mkornegay2

I saved the options and submitted a contact on your website. That is strange how just resaving the colors options addressed the issue.

Same. Apparently any workaround is not longer valid and Twitter has shut off access to their API for good. Got to love it. Well.. bye bye Twitter.

2.0.16 was a buggy and bad release. I wasted a lot of time with Cloudways support to then have to reverted back all my websites to 2.0.15. Cloudways should do more testing before released such a bad version.

It did the same to mine @woltersadvertising. I had to revert back to using 2.0.15 through SSH on all 20 of my sites. I never had issue with having to test Breeze before. But 2.0.16 totally messed up my sites like you said. It made them very erratic and CSS all messed up. I got on CW with support and they noted the issue and told be to revert. Huge wasted of my time having to do this and purge/test all my sites. I’m hesitant to update 2.0.17 @adeelkhan unless the issue has been fixed. Do you know?

• This reply was modified 1 year, 8 months ago by mkornegay2.

I had an issue with this too. For some reason it wouldn’t appear on the page I needed to and then appeared on every page. I was hoping I was not going to have to select every page for it not to be on. After an update it seems like it puts a global lock on the whole site. You may have to go to the pages and turn off individually. I’m locked out of my backend and even disabling AG through FTP it still is an issue. Based on the lack of reply from the dev it looks like you may be waiting awhile.

Thanks! I appreciate it. Breeze seems to be applying updates right regularly and I did install your latest update. I actually got it working a bit sooner, but Trap Focus isn’t enabled yet. As far as optimisation beside Breeze, I just have Varnish Cache on the server and what Divi has natively. Of course I purged everything, but I know some Divi performance options have caused issues in the past.

Thanks for digging in to this.

Any update on this? I responded to the previous email and apparently it did not post my responses. I have turned off Focus Trap, no change. I have also excluded these pages from caching on my servers and purged all cache/cookies. I have also duplicated the page and left one gallery on the page and the page loads the Agegate popup, but will not load on the two pages it’s suppose to. I have tested removed and test every update from 2.21 and no change. So I’ve installed the latest version again. I’m really not sure what could be causing the error or the plugin not load. All CSS has also been removed.

I understand as long as the errors are not affecting my site in anyway. However, on max execution time, my page builder software requires at least 120 for importing and loading so that’s why its high; to prevent timeouts. I took it down to 120 server wide to see how it may affect the backend.

That’s it. Thank you sir!

Hi Peter,

I will test the install/uninstall method and export my setup. As for performance settings here are my settings.

PHP: memory_limit = 256M
max_execution_time = 300

I just added define( ‘WP_MEMORY_LIMIT’, ‘256M’ ); to my wp-config.php file as it was not set.

Now when I say that is slows my page load, this is not in relation to site scans which should be done in off hours. It during normal hours just navigating the site. I also see this in my PHP Errors List

Warning (Suppressed)	chmod(): Operation not permitted	1	
wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:443
chmod()
wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:443
wfWAFStorageFile->_open()
wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:431
wfWAFStorageFile->open()
wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:610
wfWAFStorageFile->fetchConfigData()
wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:564
wfWAFStorageFile->getConfig()
wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/utils.php:1063
wfWAFUtils::rawPOSTBody()
wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/request.php:384
wfWAFRequest::createFromGlobals()
wp-content/plugins/wordfence/waf/bootstrap.php:46
wfWAFWordPressRequest::createFromGlobals()
wp-content/plugins/wordfence/waf/bootstrap.php:928

Hi John,

Where do you see that the custom logo was hidden? I don’t remember doing that. It was only after the plugin was installed that the logo disappeared. Maybe the WP logo was hidden from my white label plugin?

But your CSS did work. Just trying to find out the root of the issue without have to use CSS. But if you think this is the only way around it, I will oblige.

Thanks, but it’s my server CPU get bogged down, not the memory. Plus I have beyond what Divi recommends and had them even higher beforehand.

Here is the link https://we.tl/t-ta6e5bwMhB

I’m having same issues. I had to disable plugin through FTP to access my backend. I have cleared my site cache via plugin and made sure the login url is not cached. I’m still get the issue.

Seems like it’s back to working.