Digital experiences for all disciplines
New Landing › How can we help? › Atelier › Problem with Framework
New Landing › How can we help? › Atelier › Problem with Framework
- This topic has 13 replies, 3 voices, and was last updated 6 years by David Martin – Support.
-
Posted in: Atelier
-
June 28, 2017 at 12:35 pm #330341
Hi guys,
I updated my clients website to the latest version of WordPress, the theme and the Swift Framework. Now some of the elements in the page builder doesn’t show. I updated a lot of other website running Swift and didn’t had any problems after the updates.
Can you help me out?
Kind Regards,
– Erik
June 28, 2017 at 2:41 pm #330373Hi,
Any specific page? The homepage loaded fine to me.
Try to purge the cache from Total cache and also from your browser.-Rui
June 28, 2017 at 3:43 pm #330393allmost all pages has some elements that are missing. The homepage only show the first banner. Below the banner is a lot of white space but in the page builder at the backend i can see all my content
June 28, 2017 at 4:19 pm #330401This reply has been marked as private.June 28, 2017 at 8:43 pm #330438i disabled the plugin that caused those errors.
See the image i included for the errors i now see.
Attachments:
You must be logged in to view attached files.June 29, 2017 at 3:57 pm #330556This reply has been marked as private.June 29, 2017 at 4:12 pm #330557Hi Rui,
I removed the custom javascript but the same errors appeare, so i don’t think that has anything to do with it.
Kinds regards,
– Erik
June 29, 2017 at 4:30 pm #330559Just realised that the SwiftFramework plugin it’s not the latest version.
Try to update to the latest version and clear the cache. If doesn’t work, disable all plugins except SwiftFramework and Woocommerce.
-Rui
June 29, 2017 at 4:41 pm #330562I know, i just downgraded the WordPress version and Framework to see i that solved it for now. Yesterday i had runned the latest versions of WordPress, Swift Framework and the theme.
I updated everything again, turned off all plugin except swift framework. It happened after the theme update so i think that caused it.
June 29, 2017 at 5:02 pm #330563I made a few tests and there is something else caching files besides the W3TC. I created a draft page to replicate the error and started deleting elements. At the moment there is no page content and it still shows content in the frontend.
I deactivate for a few seconds W3TC to confirm this.If I deactivate the pre-minified scripts it works fine. Check the site again.
My guess is that something is caching the old minified files.
-Rui
June 29, 2017 at 5:30 pm #330567The site works again, thanks. And thanks for your clear explanation
June 29, 2017 at 5:38 pm #330568Hi Erik,
Did you find the other caching mechanism causing this? If so, I will mark this as resolved if you agree also.
Thanks,
David.June 29, 2017 at 5:44 pm #330570Hi David,
No, i’m not aware of something that’s caching the website.
But the website is fixes so i’m happy
June 29, 2017 at 5:45 pm #330572Ok, glad it’s sorted for you.
Thanks,
David. -
Posted in: Atelier
You must be logged in and have valid license to reply to this topic.