• Resolved HKP

    (@hiskingdomprophecy)


    Hi Folks,
    Just received this error message:`

    [Tue Jun 01 20:45:46.496928 2021] [proxy_fcgi:error] [pid 26868:tid 140583221630720] [client 164.132.177.1:51378] AH01071: Got error ‘PHP message: PHP Warning: Use of undefined constant DB_USER – assumed ‘DB_USER’ (this will throw an Error in a future version of PHP) in /home/hiskingd/domains/hiskingdomprophecy.com/private_html/wp-content/plugins/query-monitor/wp-content/db.php on line 140PHP message: PHP Warning: Use of undefined constant DB_PASSWORD – assumed ‘DB_PASSWORD’ (this will throw an Error in a future version of PHP) in /home/hiskingd/domains/hiskingdomprophecy.com/private_html/wp-content/plugins/query-monitor/wp-content/db.php on line 140PHP message: PHP Warning: Use of undefined constant DB_NAME – assumed ‘DB_NAME’ (this will throw an Error in a future version of PHP) in /home/hiskingd/domains/hiskingdomprophecy.com/private_html/wp-content/plugins/query-monitor/wp-content/db.php on line 140PHP message: PHP Warning: Use of undefined constant DB_HOST – assumed ‘DB_HOST’ (this will throw an Error in a future version of PHP) in /home/hiskingd/domains/hiskingdomprophecy.com/private_html/wp-content/plugins/query-monitor/wp-content/db.php on line 140′

    Will leave it with you.

    Regards and thanks,
    Angus

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks, this has been reported a few times but so far I’ve been unable to reproduce the problem. I don’t know under what situation the wp-content/db.php file could be loaded without WordPress itself also having been loaded.

    Previous thread: https://www.ads-software.com/support/topic/php-error-435/

    * Do you have any idea when this error appears? eg. does it appear when viewing a certain page or performing a certain action?
    * Can you provide a list of active plugins on your site?

    Thread Starter HKP

    (@hiskingdomprophecy)

    @johnbillion

    Hi John,

    As far as I recall this is the first time I have seen this error.

    I forwarded it as it was a) lengthy (not the normal 1-line notice) and b) it related to a future version php warning.

    As I recall, I had just deactivated your plugin which had been running for a few days, as I was not finding any useful information as to which script was causing our high cpu load and excessively high load-averages on the server.

    We use Cache Enabler (CE) which was set to empty the cache when any plugin was activated or deactivated. This has been an issue for us, for if the Cache is full at say, >250Mb, then it often caused a critical error when a plugin was deactivated.

    This is most likely what happened here. I deactivated Query Monitor with a full cache and it threw out that warning message.

    FYI, I have now changed the CE settings so it does not empty the cache on a plugin activation or deactivation – as the plugins I turn on and off often are only for testing etc. and not post content related.

    Actually, things work much better now that the CE cache remains active, and I am able to turn your plugin off and on without throwing an error message. I know because I just tested it here and now.

    I hope this helps.

    A list of our plugins is below.

    Since you are aware of this, I will make this issue as resolved….. or at least known ??

    If you need more information, please do just ask. Pleased to help if I can.

    Regards and thanks,
    Angus

    -- WordPress Active Plugins --
    
    AddToAny Share Buttons: 1.7.44
    Advanced Editor Tools (previously TinyMCE Advanced): 5.6.0
    All in One SEO: 4.1.1.1
    Better Search Replace: 1.3.4
    Broken Link Checker: 1.11.15
    Cache Enabler: 1.7.2
    Classic Editor: 1.6
    Cloudinary: 2.7.3
    Extra Sentence Space: 1.3.9
    Fast Velocity Minify: 3.2.2
    GTranslate: 2.8.63
    iThemes Security: 7.9.1
    List category posts: 0.84.2
    P3 (Plugin Performance Profiler): 1.5.4
    Pre* Party Resource Hints: 1.7.6.3
    Query Monitor: 3.7.1
    RefTagger: 2.4.1
    UpdraftPlus - Backup/Restore: 1.16.56
    Weaver Xtreme Theme Support: 4.4.5
    WPBruiser: 3.1.43
    XML Sitemap & Google News: 5.2.7
    
            -- WordPress Inactive Plugins --
    
    Database Collation Fix: 1.2.7
    Fast Secure Contact Form: 4.0.56
    GTmetrix for WordPress: 0.4.4
    Optimize Database after Deleting Revisions: 5.0.4
    Redis Object Cache: 2.0.18
    WordPress Importer: 0.7
    WP Crontrol: 1.10.0
    WP Memory: 2.10
    WP Rollback: 1.7.1
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Line 140 Issue’ is closed to new replies.