elonreynolds

Yep, the PHP WARNING issue associated with the ASE PRO “Hide Admin Notices” option has been resolved with 6.7.0. Thank you for your patience and your persistence.

ASE PRO…great tool!

• This reply was modified 1 year, 1 month ago by elonreynolds.

Yep. Please note that the recent ASE PRO 6.6.0 update did not resolve the persistent PHP WARNING message displayed when using the “Hide Admin Notices” option.

Thank you. However, please note that the recent ASE PRO 6.6.0 update did not resolve the persistent PHP WARNING message displayed when using the “Hide Admin Notices” option.

• This reply was modified 1 year, 1 month ago by elonreynolds.

I am experiencing this same (or similar) PHP WARNING message when using ‘Appearance/Customize’ to switch to the Divi theme customizer screen. In my case, I have isolated ‘a’ source of this PHP WARNING message as using the “Hide Admin Notices” option listed in the “Admin Interface” ASE PRO menu. You can review the details in my Support ticket “ASE PRO 6.5.0 PHP WARNING with Divi”.

Are you using the ASE “Hide Admin Notices” option?

Thanks for the response.

I followed your suggestions and, unfortunately, there is no change from my original inquiry details sent to you (see below).

I contacted my host again and they validated that PHP 7.0.33 with the PHP values that I see in WP Server Stats are, in fact, the default values in their (host) PHP file. Those default values are successfully passed to both the public_html root and the wordpress root files.

I can then add the PHP.ini file with the updated values (see below) to the public_html root and then query with the phpinfo.php script and get the UPDATED VALUES in that root ONLY. WP Server Stats still reports the default host values.

I can then also add the PHP.ini file with the updated values (see below) to the wordpress root and then query the phpinfo.php script and now get the UPDATED VALUES in BOTH the public_html root AND the wordpress root. WP Server Stats still reports the default host values.

I have cleared the WP Server Stats cache, deactivated the plugin, deleted the plugin, reinstalled WP Server Stats and then reactivated it multiple times, but with no change from the above results.

My host has assured me that with the PHP.ini files I am using, their sever is successfully passing the UPDATED VALUES to WordPress, And I can validate the same using the phpinfo.php script.

Based also on the performance I can anecdotally see WITHOUT and then WITH the PHP.ini file, I am comfortable that the UPDATED VARIABLES are successfully being passed to WordPress, but that WP Server Stats is incorrectly reporting the host server default values.

Please advise.

Thanks for the response. My apologies for not immediately seeing the obvious.

I successfully purged the WP Server Stats cache and re-ran both WP Server Stats and the phpinfo.php query (twice).

Same results as the previous comparison.

WP Server Stats appears to reflect my host server’s default values, while the phpinfo.php query appears to directly reference the updated values I made to the php.ini file in my root folder.

Because the phpinfo.php query is processed directly from within my root folder, does that not reflect privileges that perhaps WP Server Stats does not have???

• This reply was modified 5 years, 11 months ago by elonreynolds.

Thread is marked RESOLVED, but I have an unanswered question still outstanding.

Please advise me on where to locate the “Purge Cache – WP Server Stats” BUTTON???

Thanks in advance.

I am unable to locate the “Purge Cache – WP Server Stats” button???

Thnx for the prompt response.

I was initially reluctant to report this because the “Ozh Admin Drop Down Menu” plugin is no longer supported. It would be quite a reach for me, the end user, to expect you to look into it. But you did, and I am grateful for that.

I finally decided to report this because there is/has been no similar conflict with your sister plugin, UpdraftPlus backup, regardless of the update rev cycle for that product. UpdraftPlus plays nicely with the “Ozh Admin Drop Down Menu” plugin.

https://snag.gy/hzHDkM.jpg

Again, this glitch appeared after “making improvements and adding features” in v2.2.9.

Loyal Customer and Advocate

Thnx for the prompt response.

Screenshot: https://snag.gy/uKe3DU.jpg

Thnx for the prompt response.

Updated to 2.2.9, but, unfortunately, no change???

I did not mention this in my first post, but the default screen since 2.2.7 is ‘Settings’ and not ‘Database’.