[KoryKeymaster]

UPDATE: This thread has been closed down as the latest releases from Visual Composer seem to have resolved the issues brought on by the WordPress v3.9 update. Please refer to our final response at the end of this thread for more information on what you can do going forward should you require further assistance with Visual Composer.

NOTICE: Please take the time to read through the entirety of this post for a thorough explanation of some of the issues that certain users are facing with the most recent version of Visual Composer, as well as a download link to the latest “patch” provided by the Visual Composer team in response to these problems.

Hey everybody,

We wanted to take some time to get a centralized thread going that could help to inform you all of some of the potential issues that are going on currently with the most recent iteration of the Visual Composer plugin. Our hope is that this thread will serve as a place for us to effectively share and troubleshoot any potential issues with the plugin that we have control over, and also as a means for us to gather information to share with the Visual Composer team in order for them to more thoroughly address some of the issues that seem to have arisen from their most recent versions of their plugin.

Backstory

A couple days ago WordPress released their most recent version of the software, v3.9 (aka “Smith”). With this update to WordPress, the TinyMCE functionality of the WordPress editor was also updated to v4.X from the previous v3.X version. With this update, nearly every theme and plugin author that implements some type of functionality into this part of WordPress experienced issues due to the complete overhaul of the system (ourselves included). The only problem that arose for us personally was our shortcode generator button that is input by our X – Shortcodes plugin, which we worked diligently to implement a fix for as soon as the initial reports started coming in of a potential issue. Within 24 hours time we had out a fix for this particular issue and everything regarding X and the X – Shortcodes plugin was in order.

As stated above, nearly every theme provider and plugin developer who works with WordPress has experienced some problems because of this, and Visual Composer was no different. Visual Composer experienced numerous issues with their plugin not only with the WordPress v3.9 update, but for the fact that they had also implemented some new features into their plugin with the most recent update, which appeared to also be causing some problems. We also thoroughly tested this new version of Visual Composer with X and did all we could to eliminate plugin errors on our side even though this is handled by the plugin vendor. Within the past couple days, Visual Composer has released numerous “patches” to their plugin (currently v4.1.1.1 at the time of this writing) in an effort to work around these issues.

While we normally package updates to all of our integrated third party plugins with the theme whenever we release a new version, these “patches” are simply being output too fast in response to the issues brought up, and there is no way we can package and release these as part of the main theme output due to this very fact. Because of this, we are making these “patches” available for download here as soon as they are available from Visual Composer in an effort to hopefully remedy this issue as quickly as possible. You can find a link to the download at the end of this article, but please read on so that we can acquire your help in working through this issue together.

What’s Going on Currently

We have had numerous customers write in to inform us that everything is working for them as expected upon updating WordPress, the theme, their plugins, et cetera. If you’re not sure that you have the most recent version of everything installed, below is a list of what everything should be at currently (all of which we’ve tested and cannot produce any errors locally or on our demo installations):

• WordPress (v3.9)
• X (v1.8.3)
• X – Shortcodes (v2.1.0)
• Visual Composer (v4.1.1 or v4.1.1.1)

That being said, we’re aware that some have notified us that things are still not working quite like they should. If that is the case, we first recommend that you double check the Knowledge Base and review the Updating Your Theme and Plugins article as it provides detailed instructions on how to ensure that all of your software (i.e. theme and plugins) is up to date. Additionally, make sure that you clear out your cache in and all other browser data as this could keep you from seeing updates even if they have been administered properly.

If you have done that and are still experiencing some issues, we recommend that you check out the responses on the following threads as it is likely that one of them could provide an answer for you on why things might not be working:

• Thread #1
• Thread #2
• Thread #3

If you have already done all of the items listed above and are still experiencing an issue, please review the Reporting Issues section below to learn how you can submit information for us to effectively troubleshoot your issue.

Reporting Issues

If you have gone through all of the information listed above and are still having a problem utilizing Visual Composer, we invite you to submit a reply to this thread so that we can investigate this problem more thoroughly. If you are submitting a reply to this thread, we require that all of the following information be included:

1. Current version of WordPress
2. Current version of X
3. Current version of X – Shortcodes
4. Current version of Visual Composer
5. A list of any third party plugins installed on your WordPress installation
6. A list of any third party scripts implemented on your WordPress installation
7. A list of any customizations made to your WordPress installation

In addition to the information listed above, we require that the following inforamtion also be included:

1. A detailed description of the issue you are experiencing
2. A detailed explanation of how to recreate the issue you are experiencing

In order for us to effectively troubleshoot these issues, we require all of the information listed out above. If we do not have this information, we will need to ask you to submit it before we can review your reply. This is because there are simply too many variables for us to account for with a simple generic description of what errors you’re experiencing. Thorough details will help us to have a better picture of the nature of your WordPress installation and discern the potential source of the problem. Additionally, as stated above we have done all we can and know at this point with the theme to work around these issues brought up by the plugin, so while we might not be able to do anything directly, we can at least utilize this information to take to the Visual Composer team in an effort to help them solve potential problems. Finally, we’ve also had some users report that additional third party plugins were causing conflicts with Visual Composer (likely because they had something to do with the TinyMCE implementation as well), so it is recommended that you try disabling these to see if this helps to remedy any issues.

Latest Visual Composer Patch

Below is a download for the latest patch released by Visual Composer. We have tested this release as thoroughly as we can on our local and demo installations and everything appears to be in working order. If you are happening to still be experiencing some issues after downloading and installing this patch properly, please read through the Reporting Issues section above to learn how you can submit information for us to effectively troubleshoot your issue.

Download Latest Visual Composer Patch

[Evan LParticipant]

This reply has been marked as private.

[KoryKeymaster]

Evan,

Thanks for writing in and we’re sorry that you still seem to be experiencing some issues. We have put this thread in place in order to pull together all of our resources and information that we have on this matter so far as some of our users have been asking questions about this and we’re trying to make things as easy as possible.

The biggest thing we’re trying to stress out of all of this is that to the extent of our knowledge, we have addressed everything we know to address on the theme side of things regarding the updates with WordPress v3.9 and Visual Composer v4.1+. If you are still experiencing an issue, as mentioned above we simply ask that you share the requested information as this is necessary for us to further troubleshoot these issues even though they are plugin related and not theme related. The theme itself is functioning as it should. We understand that some issues still appear to be occurring, and we are happy to look into these matters but require the information requested above in order to do so.

Thanks!

[Evan LParticipant]

This reply has been marked as private.

[KoryKeymaster]

No problem, Evan. We are here and happy to serve you should you decide to share the information requested above. Thanks.

[shpati hParticipant]

I recommend the patch, it solved my issue with visual composer.

[Celeste CParticipant]

I have gone through all of the information listed above and still having a problem utilizing Visual Composer.
I installed the WP 3.9 theme X 1.8.3

The following Plugins

• Contact Form 7 (v3.8)
• Easy Pie Maintenance Mode (v0.6.4)
• Force Regenerate Thumbnails (v2.0.3)
• Revolution Slider (v4.3.3)
• WordPress Importer (v0.6.1)
• Visual Composer (v4.1)
• X – Shortcodes (v2.0.10)

I get this message all the time:

The page layout is created with a previous version of Visual Composer. Read this page before you update the layout to the most recent version. Upgrading to new version.

I can’t work with VC anymore 🙁

When i save my page it is copy all the content and my layout is completely changed.

Also the (‘s) changed in //////////////’s

[Florian GParticipant]

Why is the latest version of vc in this thread only 4.1.1 and not 4.1.1.1?

[Timothy HParticipant]

Reporting Issues
If you have gone through all of the information listed above and are still having a problem utilizing Visual Composer, we invite you to submit a reply to this thread so that we can investigate this problem more thoroughly. If you are submitting a reply to this thread, we require that all of the following information be included:

Current version of WordPress: 3.9
Current version of X: 1.8.3 with X – Child Theme: Integrity version 1.0.0on 1.0.0
Current version of X – Shortcodes: see list below
Current version of Visual Composer: see list below
A list of any third party plugins installed on your WordPress installation:

Contact Form 7
Version 3.8 | By Takayuki Miyoshi

Force Regenerate Thumbnails
Version 2.0.3 | By Pedro Elsner

WPBakery Visual Composer
Version 4.1.1.1 | By Michael M – WPBakery.com

X – Shortcodes
Version 2.0.10 | By Themeco

A list of any third party scripts implemented on your WordPress installation:

Must Use:
/wp-content/mu-plugins directory are executed automatically.
s2-hacks.php

Drop-ins are advanced plugins in the wp-content directory that replace WordPress functionality when present.
advanced-cache.php

A list of any customizations made to your WordPress installation: NONE.
In addition to the information listed above, we require that the following information also be included:

A detailed description of the issue you are experiencing:

Testing this on a page where I cleared all content from the HTML editor and saved the (empty) page.
Using the “Blank – Container | No Header, No Footer” page template (or any other template – including the default one); the front end visual editor button is absent.

Write me at tim@swing-thing.com for an admin login; if you would like to come in and poke around for yourself.

A detailed explanation of how to recreate the issue you are experiencing: It will not go away; so recreating it is sort of a non sequitur here.

[Timothy HParticipant]

I just noticed an update to the X-Shortcodes plugin.
When I tried to deactivate it, it would not deactivate.
So I simply replaced the plugin folder (2.0.10) with the newer version folder (2.1).
According to the plugins manager, the update took okay.

However, that made no difference in terms of the missing front end visual editor issue.

[James LParticipant]

The patch has worked for me. I deactivated all plugins, re-installed visual composer patch 4.1.1, then re-activated a few plugins and avoided going back and forth between visual and classic editor when working on my pages. I have been able to use the editor all day with no problems. Thank you, Support!

[Trevis BParticipant]

Guys, I’ve done everything. All my versions are up-to-date. All my plugins. I deleted the Visual Composer and installed the patch. It is still giving me the error message and when I hit UPDATE, it duplicates all of my rows, places them in random orders, and adds rows that I did not add and it is impossible to delete them.

I know this was unexpected with WP 3.9. I’m frustrated because I was really beginning to understand how X works as a newbie (I left Weebly for this them).

I hope it gets fixed very soon. I have a few deadlines to meet.

[Trevis BParticipant]

For some reason, I let it sit for a second…come back and it’s fixed! Appreciate you guys!

[KoryKeymaster]

Shpati, thanks for writing in and letting us know that everything is working for you now. 🙂

---

Celeste, just to double-check, were you able to take some time to read through thread #1 from our initial post? It addresses this specific issue, which is nothing new and is unfortunately due to developmental nuances of the plugin itself. If you were not experiencing this issue before and are now seeing it, we’ll be happy to assist you with this but we’ll first need you to provide us with some information (don’t forget to select Set as private reply to ensure that your data remains hidden):

1. Your URL.
2. Your WordPress login credentials.
3. Your FTP credentials (in case we need to check anything out on your server).

Once we have all of this, we’ll be happy to take a deeper look into things.

---

Florian, the version of Visual Composer provided in this thread is v4.1.1.1. If you are seeing v4.1.1, it is likely that you are opening an old file or perhaps the provided version in the v1.8.3 release of X. Try downloading the plugin again from this thread as v4.1.1.1 is what has been available here since it was released on ThemeForest. Thanks!

---

Timothy, if I’m understanding you correctly it sounds like the issue you seem to be experiencing is the absence of the frontend editor from Visual Composer with X. If that is the case, the following information from our v1.8.1 release notes should help you with this situation. If you get a chance, we recommend you take a look through these notes in their entirety, but the following is an excerpt from that thread that explains this issue:

Beyond the Customizer updates with this release, we’ve also included the latest version of Revolution Slider (v4.3.3) and Visual Composer (v4.0.4). It should be noted that we have implemented all of the necessary changes to accommodate the newest offerings from the Visual Composer plugin, but much to our chagrin have had to disable the frontend editing ability at this time due to a few developmental nuances of the plugin itself. We spent a considerable amount of time investigating how other other theme providers are dealing with these same realities and they all seem to fall into one of three camps: they’re still not using v4.0+, they are using v4.0+ but have disabled the frontend editor, or they are using v4.0+ but have bugs with how the frontend editor operates with theme integration. Because we wanted to get the ball rolling on this update, we’ve gone ahead and worked on everything we can at this point and are personally working with the Visual Composer team to address the various bugs we’ve found while working with the frontend editor. As soon as these issues can be addressed by their team, we will be quick to add back in the frontend editing capabilities as soon as possible.

If there is more to this issue, then please don’t hesitate to let us know as we’re happy to help you out with anything else that might be going on.

---

James, we’re so thrilled to hear that everything is working for you now. 🙂 Thank you for reporting this for us and our other users to hear.

---

Trevis, it sounds like you might have experienced a caching issue with your update but we’re very happy to hear that things are working for you now. Thank you so much for letting us and our other members know. 🙂

[Oliver VParticipant]

Hi!

After updating everything, I just have the VC error: Please,update……

It has happen after around 30 minutes working with VC, and fortunatelly I have been able to recover the data through a WP revision.

Question here is: I have VC 4.1. Is is the same as 4.1.1.1?

Should I use the VC patch from this thread?

Thx!

Oliver.

[Author]

Posts