markusjj

Sorry. I meant to say the plugin has bad folder structure. ??

I found the solution.

For anybody else who might face the same problem, I followed the suggestions by webvitalyin this post

In a nutshell, this folder has bad folder structure.

Oh, I can see now on Getting started with WordPress and AVChat

1. Installing the AVChat Video Chat Plugin PRO for WordPress

First you have to download 2 archives from the client/trial area on https://nusofthq.com to your computer. These 2 archives are:
AVChat 3.0.zip (contains media server files for Red5/FMIS/Wowza and AVChat Standalone)
avchat3_wordpress_plugins_pro.zip (contains 1 plugin for WordPress 3.x)

Which means that I must be a client to install this plugin? Which means that I need to pay $130 for the 10-day trial?

Otherwise, I’m SOL.

I certainly do not have a problem with spending money on solid software which took a lot of hard work to develop. However, shouldn’t this be very clearly disclosed by the plugin’s author in the WP community plugins area?

A clarification would be much appreciated.

Well! All is good. Apparently I’ve got no conflicts at all. Just my slow wits!

I simply didn’t know where to look. I previously removed my menus, and I did not think to add a menu and look for the functionality of your plugin under each pages’ properties.

Sometimes the problem is digging through all the UI options, knobs and buttons of WP. Anyway, your reply forced me to dig deeper and play with it some more. Thanks!

Same problem for me. The plugin options are not displayed in Appearance > Menus.

If you could find a hack around the issue you explained in FAQ, this would be an awesome plugin that would save misery for many a WP user… (It’s simple, yet flexible!). …

I’ve got: WP 3.9.1, BuddyPress 2.0.1, Buddyboss 3.2.0. Cheers!

Thank you, Zourbuth. Works well. Very nice, and awesome work!

Thanks for your prompt reply! So, here’s my issue in more detail:

I could edit h3 content class=”widget-title”.

However, I could not edit (or remove) the span content in class=”screen-reader-text”. That’s not so ideal.

I think I would prefer either edit or remove/delete the content in the span class=”screen-reader-text”. And then collapse it vertically, so that there is no empty gap between the “widget-title” and the input class=”form-control search-field”.

Of course I still would have the ability to keep the h3 element, “widget-title”. (Editable of course. Just as it is right now.)

https://brainsonwings.com

You are very welcome! The thing about WP theme “business” is that fast and friendly customer support is just as important and time-consuming as software development. It’s tough. But you’re doing great.

Also, you can try this snippet:
https://www.themesandco.com/snippet/altering-adding-footer-credits/

On a side note, @apestaartje, while we do understand that it’s been frustrating and time-consuming to you, please try to emphasize here with Nikeo and volunteers who are also slaving under high stress trying to satisfy everybody (which of course is not possible). I do not know if these guys get any sleep at night. I know that hundreds of hours went into the software development of this theme. And they get no financial compensation for their work. They provide tremendously valuable services to the WP community. They are not a “company”; they just give away their work product freely to the community. I think we should all be grateful and thankful.

Also, please understand that the complexities of browser cross-compatibility issues are overwhelming. I used to manage software development teams in the past; and these issues are some of the hardest to resolve. (It’s like hacking around and fixing other peoples’ bugs.) So the fallback implemented by Nikeo is probably the only possible solution for IE9.

Disclaimer: I am not on this team; but I respect what has been done here. Customizr is one of the greatest free or paid themes — based on outstanding Bootsrap responsive framework. I am really grateful for what Nikeo are doing here!

Well, if this is the problem in question, then Nikeo might have to decide (as in prioritize) what to do about it. But perhaps since the theme is advertised to be IE9 compatible, some IE-specific hack might be in order for future release(s)….

Is is above my head. I do not personally find the issue of squares vs. circles grossly objectionable. However, I do understand and accept that some users might.

And for the record, I do abhor IE. I wish it just died away and vanished. It has always been a developers’ nightmare with all non-compliances. But I do understand that users will continue using it. And we’ll have to live with this monstrosity. These screenshots I took from were from an ancient Windows Vista laptop I had drag out of the attic.

Don’t know what else to say. I’m a mac user. ??

Anything for you my friend…. Here are the links to 2 screenshots from front page of the demo on IE9. I hope you can access them on my Dropbox account.

Is that what you expected?

Apestaartje, it’s not you against the world. We are trying to help. It’s just that sometimes even the best teams of excellent, dedicated volunteer supporters (I’m not counting myself) can run out of ideas…. Troubleshooting remotely has never been easy.

Sorry, I’m officially out if my ideas. I guess I go and smoke some grass instead.

I still think it would be a good idea to isolate the problem completely and perform a completely independent test to prove your point. You know, MS could be shipping different versions of IE9 to Netherlands just to disturb the wold browser hegemony… They have a secret agenda to piss people off in general (as you can tell I’m not a fan). Well, I am in US. No problems here. I don’t know where the other members are.

Anyway, either browsershots.org or netrenderer.com would do… Could you link to screenshots with results?

But Customizr works great with IE9. No problems you’re describing. So it’s something with your system… Can you reinstall your browser?

If not, I have another suggestion. You can do cross-browser testing remotely. You can do independent verification of your site on older browsers. Check out these:

• browsershots.org free service
• netrenderer.com free service
• crossbrowsertesting.com not free
• browserstack.com not free

If you can confirm the problem exists after any of these tests, then there is an issue with code someplace….