-
-
There is clearly a big issue with the theme as everyone is notifying you of a specular codeless plugin issue causing a critical issue that leads to the site failing.
Why are you guys requiring EVERY SINGLE PERSON to create a new separate tix and only responding to them privately, instead of providing the fix to everyone.
If there is a glitch in your theme (which there clearly is) there should be overall info we can use to fix it.
I too had to utilize a backup. Please provide a fix. Thanks.
-
Hi,
Please share your website URL, wp-admin, and FTP info (Username and password) and send me using “Set as private reply”.
Thanks -
-
I will do that, but I’m just curious – why are you guys making everyone who has this same issue do a private reply instead of just posting what the solution is so we can fix it quickly? It has to be a global issue, right? So why not just provide that to everyone so we can all move on it more quickly? thanks.
-
-
I had already got the site working before providing credentials by rolling back a backup and not touching a lot of your core theme / plugin files.
Since we’re all wondering:
1. What did YOU do after you had access?
2. Why is WP Bakery still so outdated? Why not update that as well?
3. Is it safe for us to turn auto updates on? I had to turn it off since I originally fixed this but it broke again.Mainly, I’d like to know what the issue WAS/IS and how to ensure it doesn’t happen again. Thanks!
-
-
-
Thanks, but can you explain what those were, why they were needed, why so many people had this issue and if you will be providing a global fix? Also, WP Bakery is very outdated, when will you provide that fix? I appreciate the help but more concerned that there wasn’t a global fix/patch provided when this was a widespread issue. Forcing everyone to create separate tix doesn’t seem efficient so we’re just wondering what exactly the issue was. thanks so much!!
-
-
-
-
Hi, I see someone logged into the account today, I think you guys manually updated WP Bakery on the site.
Last question: it’s asking about updating the codeless framework from 1.06 to 1.07. Do we want to do that or keep it at 1.06? Cause I believe updating that core plugin broke things last time. Please advise.
-
Please keep 1.0.6 and ignore update this for the time being.
Thanks,
-
You must be logged in to reply to this topic.