Digital experiences for all disciplines
Forum Replies Created
-
Posted in: We hit Power Elite.
-
Silly me, forgot to restart Apache. Sorry!
Hi David,
I had to set WP_DEBUG to false because I’m moving forward to launch the site in spite of the issue, and I have needed to test functionality without this notice displaying (it shows twice). If at some point I discover where the problem lies, I will report it here. FYI, I didn’t notice the problem until upgrading to 1.67.
To replicate the problem, all I need to do is set WP_DEBUG to true and submit a contact form. Then the notice is displayed only with the JSON response, not in the main body of the page.
Sincerely,
Chris
Hi Rui,
I understand; I’m a developer, too. I’m sure you get lots of requests to fix issues that aren’t your responsibility, but since this happened to me the first time on a clean install of your theme and required/recommended plugins, and later again after updating the Swift framework, I don’t think that it’s prudent to assume that the problem lies with a third-party plugin.
Before this issue re-occurred, I installed the Custom Permalinks and WordPress Importer plugins. Looking through their code, I don’t see anything that jumps out at me that would conflict with the page builder. Here is my full list of active plugins:
Advanced Custom Fields
Akismet
Atelier Demo Content
Breadcrumb NavXT
Contact Form 7
Custom Permalinks
Go – Responsive Pricing & Compare Tables
oAuth Twitter Feed for Developers
Swift Framework
WooCommerce
WooCommerce Quickview
WordPress Importer
WordPress SEO
YITH WooCommerce WishlistAt the moment, everything’s working just fine since my last fix this morning.
FYI, this has happened to me twice since this topic was resolved. I was able to get it working again by deactivating and reactivating all plugins, but I shouldn’t have to do so. It would be nice if you all could see about fixing this in a future update. It is very disconcerting to be faced with a potentially unusable site after weeks of work.
That did it. Thank you.
-Chris
Hi Ed,
Thanks for the quick response. At the moment all I’ve got on the site are the plugins required/recommended by Atelier; this is a clean install, haven’t even run the demo importer yet.
I’ve increased the memory limit from 40MB to 128MB (via php.ini in the wp-admin directory) and turned on allow_url_fopen (via Apache’s root php.ini file because local php.ini edits wouldn’t override for some reason, not even after restarting Apache).
Problem solved.
-Chris
-
Posted in: We hit Power Elite.