Tagged: x
-
AuthorPosts
-
October 6, 2016 at 2:36 pm #1205606
IrishTomParticipanthttp://qg.mc2gd.com
Wordpress 4.6.1
X version 4.6.3
Cornerstone 1.3.3
VC version 4.12.1I’ve just updated to the latest version of X (and plugins) and now my site is broken.
I’m using VC to build my pages, and every row that had a background image or background colour defined isn’t showing the background. In the backend editor of VC, I can still see the image / colour that’s be defined, it just doesn’t show up on the front-end of the site.
Also, every row is now spanning the full width of the screen. I’m using the ‘Blank – No Container | Header, Footer’ page template, and then the rows in VC are set with ‘inner container’ ticked, but it’s not obeying the inner container and all content is running to the edge of the screen.
Just to confirm, I’ve deactivated all plugins except VC and Cornerstone. I’ve uninstalled and reinstalled all of the plugins as well.
Any help would be greatly appreciated.
October 6, 2016 at 2:38 pm #1205610
IrishTomParticipantThis reply has been marked as private.October 6, 2016 at 2:45 pm #1205619
Zack FParticipantSame problem here…
October 6, 2016 at 2:51 pm #1205632
IrishTomParticipantGlad it’s not just me (not that it helps either of us very much)…
October 6, 2016 at 2:55 pm #1205643
farhaddcParticipant+1
October 6, 2016 at 3:26 pm #1205692
IrishTomParticipantOk, I’ve reverted back to X version 4.3.1 and magically everything is working again.
Let me know when you solve the issue and I’ll consider the risk of updating.
October 6, 2016 at 4:21 pm #1205766
Steve SParticipantHad the same problem and restored a backup. Just curious if you know what happened. Guess I’ll hold off on updating the theme for a while.
October 6, 2016 at 7:45 pm #1206036
Rue NelModeratorHello There,
Thanks for updating in! Are you using CloudFlare or may have installed a caching plugin like WordFence, W3 Total Cache or WP Super Cache? Please keep in mind that after doing every updates, always remember to clear all caches when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.
I would recommend that you create a staging site. This is very useful because you can test drive any X updates in the staging area, do the customizations and troubleshooting without disrupting your live site. Once everything is perfect, you can easily and flawlessly proceed the update in the live site. To know how to create a staging area, please check out these articles:
http://www.wpbeginner.com/wp-tutorials/how-to-create-staging-environment-for-a-wordpress-site/
https://maintainn.com/2015/02/how-to-create-a-staging-site-for-wordpress/Hope this helps.
October 7, 2016 at 11:29 am #1206959
IrishTomParticipantI wasn’t using any caching apps or CDN.
Funnily enough, the site I’m working on is the staging site for a new design. I was about to push it live and thought “I’ll just update my theme and plugins so it’s all up to date” — big mistake.
Or do I need a staging site for my staging site?
October 7, 2016 at 8:59 pm #1207605
Rue NelModeratorHello There,
Sorry for the inconvenience. I can confirm that this is an issue with the latest release of X. As soon as our developers confirms that this was indeed a bug, they issued an update to address this. X 4.6.4 is now available in automatic updates! This release contains fixes for the mentioned issues so be sure to check out the changelog. Please do update to the latest version. After doing the updates, always remember to clear all caches when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.
Thank you for your understanding.
-
AuthorPosts
- <script> jQuery(function($){ $("#no-reply-1205606 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>
