[Russel DParticipant]

Good Day
I Have VC 4.1.1.1
I am running latest version of WP on local server with MAMP.
I am using Renew Template.
I am testing page with header/ Footer no content template.
My editor show no text. If I highlight area is in white? When I switch to text and type my Text does not come out.
I am also getting ///////////////// errors.

[Russel DParticipant]

Hi
I am using all updates. Installed WP locally.
Text is not visible in text editor at all.
Also getting /////////////// error.
I have downloaded all the patches.

I am using Renew theme with header/ Footer no container template.

[KoryKeymaster]

Anna, we’re thrilled to learn all is in working order for you now. Thanks for letting us know! 🙂

---

Michael, similarly to Anna above, we’ve very happy to learn that everything seems to be working for you again after taking the time to go through your installation and correct the problems at hand. We understand that WordPress can at times have a lot of moving parts to keep track of (especially if you’re under a time crunch), but it seems as though the information provided has helped to clarify some of the matters you were experiencing. We are grateful for your kind words about the theme and we look forward to continuing to serve you here in the member area. 😀

---

Russel, as explained in the Reporting issues section from the original post on this thread, we will need you to provide us with detailed steps on how to try and replicate the issue you are experiencing. A simply description of the problem is not enough information for us to go on at this time and we need further data so that we can try to recreate the problem and troubleshoot. We’ll also need further clarity on what you mean by “getting /////////////// error” as well. Additionally, providing us with screenshots could prove to be most helpful as well. You can use a service like Imgur, Dropbox, or CloudApp to host your images and link out to them here if necessary. Thanks!

[Sebastien MParticipant]

I have all the same errors everybody has… duplicate content

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

So I decided to go back to wordpress 3.8.1

[KoryKeymaster]

Sebastien, we are happy to assist you but kindly ask that you refer to the Reporting Issues section in the original post and provide us with the requested information that is required before we can look into anything. Thanks.

[Sebastien MParticipant]

I decided to go back to 3.8.1 while you guys fix these issues and release a conform update…

Thanks

[Hayden GParticipant]

Hi,

I have read through all the threads. It appears that the tutorial in the knowledge base for “Updating your Theme and Plugins” is now out of date as the format is different. However I have gone back to Themeforest, downloaded the latest theme, but now I can’t upload it (I get stuck on the drag and drop bit). Can you help please?

Thank you

[Victoria DParticipant]

Hi guys

Just letting you know the link is broken to the latest release notes sticky post you have in the forum.

Also, WPbakery have version 1.4.2 out of Visual Composer, have you got access to that yet?

Thanks!

[KoryKeymaster]

Sebastien, as stated numerous times throughout this thread and confirmed by countless users, these issues are not theme related and are related to problems with Visual Composer. Visual Composer’s latest release is even slated as a WP 3.9 Compatibility Update, elaborating on the numerous issues the plugin has seen recently. We are happy to assist you in troubleshooting these plugin issues but want to reiterate that these problems are not theme related. We have had countless users inform us that following our instructions listed here have helped them. If you do decide to share with us the information we have requested, we will be more than happy to assist you.

---

Hayden, can you please elaborate on what you mean by “the format is different” as I’m not quite sure what you’re referring to. If you’ll please go through the Reporting Issues section at the beginning of this thread, there are some required pieces of information we request from our users when submitting these issues. If you’ll go though that and provide us with what we’ve asked for we’ll be happy to assist you further.

---

Victoria, Visual Composer just released v4.1.2 today. It will be included with the coming release of the theme. We normally don’t release every iterative output of the integrated plugins with the theme, we only did that with the recent versions of Visual Composer since they were so problematic. v4.1.1.1 appears to be stable as a vast majority of our users have notified us that things are fine with it and v4.1.2 will be included in the next release as stated previously. Moving forward, newer versions of Visual Composer will be bundled with the latest releases of the theme as they have always been.

[Victoria DParticipant]

Ok cool, I didn’t realize it was so new. Thanks for the quick response!

[Victoria DParticipant]

I still can’t reach this post: Release Notes: X v1.8.4 | X – Shortcodes v2.2.0 (IMPORTANT: READ BEFORE UPDATING FROM PREVIOUS VERSIONS)

It gives me a 404 message.

[KoryKeymaster]

Victoria, this post is not public yet as we have not released the theme at this time. It will become available as soon as the theme is approved by ThemeForest.

[Dusten HParticipant]

This reply has been marked as private.

[KoryKeymaster]

Dusten, we are sorry to hear that you seem to be experiencing some issues with your server issues as it relates to Visual Composer. While the following thread references GoDaddy hosting, we have found that this issue is not necessarily localized to just GoDaddy users with shared hosting accounts. As you can see in that thread, not only are these errors not specific to our theme (i.e. we have videos of Visual Composer crashing multiple sites using the themes provided by the core WordPress team) but the Visual Composer team has confirmed that this is an issue on their end (not the theme) and that it is something they might look into in the future (the following quote is taken from that thread and is a direct quote from the Visual Composer development team confirming the source of the error to be a plugin issue, not a theme issue):

“I just heard back from our development team. Unfortunately, they are not able to trace the exact cause of the issue, but it should be related to the resource usage as it is related to the shared hosting and resources used on shared hosts are minimum…The issue is on our bug list and the development team might take a look at it in future.”

Regretfully, as troublesome as this issue is and as much as we would like to be able to assist in this matter, there is nothing we can really do at this time as this error is related specifically to Visual Composer and not the theme. The theme truly has no control over this issue and simply takes advantage of the provided API with the plugin to map our own shortcodes to the Visual Composer interface, that is all. In the videos that we’ve linked out to in the thread mentioned above, you’ll see that we were able to crash multiple sites using the native Visual Composer plugin with their native shortcodes, nothing is X-specific in those videos.

At this time we are happy to pass along any information you can provide us with to the Visual Composer support team in an effort to bring further attention to this situation in hopes that they will address this issue sooner rather than later, but as you can see from their provided quote it does not appear to be a huge priority on their list right now. The only real advice I can provide right now is to go through the most recent release notes for v1.8.4 of X, which includes the most recent version of Visual Composer (v4.1.2) and you can try following our instructions to update the plugin and see if that helps anything regarding this issue. Beyond that, if this is something you need looked into immediately you may need to purchase a license of the plugin directly from CodeCanyon so that you can sign up for support with their team and have them look into this matter personally as they are the ones who will be able to address this memory resource usage problem since this issue is plugin related.

[KoryKeymaster]

Hey everybody,

I just wanted to take a brief moment to explain that we are now closing down this thread as a vast majority of you have written in to confirm with us that following the instructions listed out at the beginning of this thread fixed the issues you were encountering. As stated in that opening response, Visual Composer experienced a litany of issues with the recent WordPress v3.9 update and we did our best to work quickly to inform users of this problem and help troubleshoot issues as much as possible even though they were plugin related and not theme related and there was not much we could do beyond guide and direct through this process. It appears that with their last release (v4.1.1.1) that things had finally gotten resolved for the most part, and as mentioned in the latest release notes, v4.1.2 of Visual Composer (which is included with the new release of the theme) is labeled as a “WP 3.9 Compatibility Update,” so we are hoping that any residual issues on their side of things have been ironed out for everyone.

At this time if you have any further questions regarding Visual Composer, feel free to open a new thread in the forum and one of our support staff will be more than happy to assist you. Thank you again for your patience and understanding while we worked through these issues presented by the plugin together and we look forward to continuing to serve you here in the member area. 🙂

[Author]

Posts