-
AuthorPosts
-
September 14, 2014 at 9:50 pm #318917
Please respond in reference to major issues with pages not being editable via Avia Layout Builder. Running latest version of theme 2.9.2 and WP 4.0. nothing but spinning loader when I try to edit pages.
Is not plugin a incompatibility issue and I’m sorry but NO I’m not manually overwriting via FTP with updated theme files. The whole purpose of an auto update is also broken if you guys can’t address this. If you have isolated the code or issue please let me know so I can go in and make the necessary changes in the core files that are determined to be the culprit.
Any updates on this? I see numerous references to the same issue in the forum among other WP 4.0 issues. Thanks!
September 14, 2014 at 10:11 pm #318919I have the same issue- after updating to WP 4.0…and I’m on the deadline.
September 14, 2014 at 10:34 pm #318921Houston. We have a problem. OK I did do what I said I would not do and even went in and FTP’d a brand new download of 2.9.2 directly to the server. Issue still persists. Infinite spinning loader when attempting to edit a page. Also as mentioned elsewhere something funky is going on with the ENFOLD theme settings display. Can no longer access from left dashboard ENFOLD Link and see all the theme settings. I now have to access theme settings from top WP admin bar to even get all settings for ENFOLD to display.
Awesome theme but I would have hoped something like this would have been resolved much sooner as 4.0 has been out for some time now. I’m still cheering for you guys though as it’s an awesome theme. Hope your team can address the issue and get it resolved. Thanks!
- This reply was modified 10 years, 1 month ago by GaWebDev.
September 14, 2014 at 10:46 pm #318926I’m having the same issue. The circle just keeps on spinning. Hope the team can resolve the issue asap. Thanks!
September 15, 2014 at 2:52 am #318952I downgraded WP to the earlier version- and the evil thing stopped spinning.
September 16, 2014 at 3:54 am #319554Hey!
Can we see the site live and log in to take a look? So far out of the hundreds of posts we’ve gotten for “issues” we have yet to actually have a bug report recorded that has needed a theme update to address.
We *always* update immediately when we find bugs after an update so if we find one we’ll fix it.
Best regards,
DevinSeptember 16, 2014 at 4:12 am #319557same issue, if you still need a login to look at the issue let me know and i can ping you the details.
September 16, 2014 at 4:35 am #319563Same issue but with Enfold. Clicking Default Editor does nothing.
September 16, 2014 at 5:47 am #319573Sure, you can login and take look- where do I send the info?
ThanksSeptember 16, 2014 at 8:26 am #319650I see two offers for wp admin access. Hopefully that is enough. The client’s site I updated and am having the issue with is a very high volume eCommerce site and for security purposes I would not be able to offer wp admin. If it were my own site, absolutely. No problem.
I have yet to roll the update to my own Enfold site as 5+ years of web development and WP experience have taught me otherwise. I’ll wait until you guys own the issue and resolve it if it’s yours. It could be a WP 4 thing as well but have not seen the reference to this over in wp forums. Thanks for looking into it.
September 16, 2014 at 8:28 am #319651Hey!
@jmaresca23: Please create a new thread with the issue description and your login details. Post the url of the thread here. If you have the time, after updating the theme to 2.9.2, please disable the cache and minify plugins if you have them installed. See if the issue persists.Regards,
IsmaelSeptember 17, 2014 at 2:34 am #320247Nope, I though it worked. It didn’t.
- This reply was modified 10 years, 1 month ago by petarda.
September 17, 2014 at 2:48 am #320251Hey!
You and any other user can always post details as a private reply or as private data on a new post and we will be able to log in and take a look.
Still looking to log in and find an issue so if you have one, we would love to see it and roll out a fix if needed.
Regards,
DevinSeptember 18, 2014 at 10:22 pm #321525Updates? I see this issue all over the support forums yet no direct response to it. Can we please consolidate the threads or at least get some direct response? All I’m seeing are standard responses from moderators that “seem” more interested in pushing the issue back on the user.
In my case it is your theme and an incompatibility with WP 4.0. How long will this apparent “bug” be side-stepped before Kriesi owns it?
Great theme but it is very disappointing how it “appears” you guys are sidestepping this issue that dozens of us are experiencing.
September 18, 2014 at 10:27 pm #321526Hi @GaWebDev!
Enfold 2.9.2 should work fine with WP 4.0 alone, perhaps you have a plugin that is not yet compatible with WP 4.0, have you tried disabling all third-party plugins to see if it gets fixed?
Regards,
JosueSeptember 18, 2014 at 11:26 pm #321565Yes sir. Even on a Development server w/clean WP 4.0, theme version 2.9.2, & no plugins activated. I’m close to debugging it (something I feel the developer should do) but I’ll post the fix when I get it as there are multiple references to this same issue all over the forums. Too many with the exact same issue for the problem to be external from the theme its self. Thanks.
September 18, 2014 at 11:30 pm #321567Hope you find a fix :)
As my colleagues mentioned, if you want us to take a look we would need Dashboard access.
Cheers!
JosueSeptember 19, 2014 at 3:42 am #321635Hey @GaWebDev – If you have a site for us to see a bug please create a new topic with login credentials in as private data. Its the same steps I’m asking everyone to do now since these topics keep ending up with the user having 2.9.1 installed or a plugin conflict but the overlapping replies make it easy to miss that as the base issue.
In every other theme update we have ever gone through (which is a lot since Kriesi is one of the highest selling authors on themeforest) we have patched for bugs in the same way we are doing now.
Cheers!
Devin -
AuthorPosts
- You must be logged in to reply to this topic.