• Resolved roadlink

    (@roadlink)


    IHi there,

    It worked well on one website but didn’t on other one.

    Other one: I use convesio hosting. they don’t use wp-config but their own file.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter roadlink

    (@roadlink)

    Here are logs from other plugin about this.

     
    Mar 03, 02:44:58

    Warning: chmod(): No such file or directory in /var/convesio/wordpress/wp-admin/includes/class-wp-filesystem-direct.php on line 173


    Mar 03, 02:41:59

    PMCS Caught Exception: Failed to update the config file. in /var/convesio/wordpress/wp-content/plugins/debug-log-manager/classes/class-wp-config-transformer.php on line 421


    Mar 03, 02:41:59

    Warning: file_put_contents(/var/convesio/wordpress/wp-config.php): Failed to open stream: Permission denied in /var/convesio/wordpress/wp-content/plugins/debug-log-manager/classes/class-wp-config-transformer.php on line 418
    Plugin Author Bowo

    (@qriouslad)

    @roadlink thank you for reporting this. At the moment, Debug Log Manager only supports sites where wp-config.php file’s location is either the defaul one, in WP root directory, or a predictable one… and where the debug.log file can be accessed publicly.

    What do you know about how Convesio place and manage the wp-config.php and debug.log files? Please try asking their support as well whether it’s possible to use any debug.log reader/parser plugin to access their wp-config.php and debug.log file. In managed WP hosting, occasionally these files are purposefully locked out from access by plugins, and only editable and accessible from their server/hosting panel.

    Thread Starter roadlink

    (@roadlink)

    Hi Bowo,
    Convesio keep wp-config.php file but use wp-convesio.php file for settings.
    What line should I need to add there?
    I can do it manually.
    I use another log plugin within this way.

    Plugin Author Bowo

    (@qriouslad)

    @roadlink these are the wp-config.php lines added by Debug Log Manager:

    define( 'WP_DEBUG', true );
    define( 'SCRIPT_DEBUG', true );
    define( 'WP_DEBUG_LOG', '/path/to/the-dlm-debug-log-file/wp-content/uploads/debug-log- manager/yoursiteslugid_20260115004139411208_debug.log' );
    define( 'WP_DEBUG_DISPLAY', false );

    The debug.log file on the third line (WP_DEBUG_LOG) should be automatically created by Debug Log Manager on activation. Please try to loook for it in /wp-content/uploads/debug-log-manager/ and copy the file name. Good luck.

    Thread Starter roadlink

    (@roadlink)

    that worked very well. Thank you

    Plugin Author Bowo

    (@qriouslad)

    @roadlink glad to hear that. 🙂

    If you find Debug Log Manager useful for your dev work, please kindly consider writing a quick review for it at https://wordpress.org/plugins/debug-log-manager/#reviews. Thank you.

    Thread Starter roadlink

    (@roadlink)

    I did 🙂

    Btw I have 2 websites on same hosting. It worked for one of them.
    But exactly same config file didn’t work on the other one.

    I mean file is there but no log.
    https://monosnap.ai/file/kDTS3GDGKFdW1krDJ9WoToWZstxdjk

    Plugin Author Bowo

    (@qriouslad)

    @roadlink thank you.

    As for the latest issue. Please try the following:

    • Delete both log files
    • Deactivate DLM and reactivate
    • Check that a new log file has been created.
    • Use the filename of the new log file in wp-config’s WP_DEBUG_LOG constant.
Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.