Sorry for the initially off-topic reply.
—-
@phpexpert21 You have been politely asked three times so far about kicking off your replies with “Thanks for contacting us.”
https://wordpress.org/support/topic/removing-thumbnails-on-homepage/
https://wordpress.org/support/topic/minamaze-v-1-4-3-free-slideshow-speed/#post-8787131
https://wordpress.org/support/topic/caannot-login/?view=all#post-8791694
This can lead to confusion that you are presenting yourself as an official support representative of the theme or plugin in question, when in fact you are not.
Please, as this is now the fourth request, please stop doing that, or we might have to consider further actions against your account. We do take impersonation very seriously around here, and while we have a feeling that impersonation is not your intent, the fact that you have so far ignored three previous polite requests is beginning to make us feel otherwise.
—-
@piter92wzg Since that is a commercial plugin, we ask that you please go to their official support channel, so you can get support from the people who know it best: http://support.wpbakery.com/
Forum volunteers are also not given access to commercial products, so they would not know why it is not working properly. Other community members who may have faced your issue might be able to help you but your best bet is your product’s developer. Keep in mind we encourage you to use the official support venues, as it allows the developers to be aware of issues with their code and gives back to the community in a more robust way.
-
This reply was modified 8 years, 9 months ago by
James Huff.
-
This reply was modified 8 years, 9 months ago by
James Huff.
@macmanx I understand your pointview. I re-buy support from plugin creators and submitted them a ticket. Initially I was sure that the conflict is produced by the theme after update. But it’s not true. I’m sorry again.
@piter92wzg
No worries at all, we’re always glad to help 🙂
As a future reference our plugin is indeed VC compatible so maybe it’s just something in their latest update that broke it
Kind Regards,
-Roch
@rochesterj It shows that the conflict was produced by two plugins: google analytics and comet cache. VC support figured it out.
Awesome!
I’m glad it’s resolved!
Please, let us know if you need anything else.
Kind Regards,
-Roch