Serious Lack of Professionalism

  • cvladan

    (@cvladan)


    3 years, 1 month ago

    It’s difficult to comprehend how such plugins make it to wp.org.

    This plugin attempts to load the error_log.txt file, which typically does not exist on WordPress, except perhaps at the plugin author’s setup.

    In fact, if not intentionally changed, the default log file when WP_DEBUG is enabled is located at /wp-content/debug.log.

    However, this plugin tries to load the error_log from the root site folder for some unknown reason.

    Not only it does not know the default log file location, but it also does not check if we have deliberately modified the WP_DEBUG_LOG path and in that way defined another log file.

    All in all, it shows a serious lack of professionalism.

    It is a total waste of time. Don’t waste yours.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    3 years, 1 month ago

    @cvladan I’ve restored this review and removed this line:

    It’s as if wp.org is a private repository? Maybe they started approving custom plugins that we write for our clients?

    The directory is open to anyone who writes safe (i.e. secure) code that meets our guidelines. But bear in mind we only review the initial submission, so people make edits that break things all the time.

    It would be kinder, but it is not required, that you ask for support first before reviewing. Simply posting a support topic “Hey, you call a non-default log file with no way to customize. Can you fix that to check what WP is calling for the debug log instead?” would have been tops 🙂

    Plugin Contributor Stefan Pejcic

    (@stefanpejcic)

    3 years, 1 month ago

    Pozdrav Vladane,

    This plugin has nothing to do with the debug.log file – as the plugin name suggests error_log File Viewer is intended to work only for the error_log file.

    And because on most shared hosting platforms the error_log file is not publically accessible (nor should it be), the plugin has a function that when the download button is pressed, it makes a copy of the error_log file to error_log.txt and allows the user to download that file on demand.

    So there is no need to check the WP_DEBUG_LOG path and the file error_log.txt is created on demand – when the button is pressed to download it, and afterward gets deleted for security.

    Sorry if the plugin is not doing exactly what you need (download debug_log file), but feel free to fork the plugin and modify it as per your needs to use the debug.log instead. Feel free to contact me if you need any help. 🙂

    Cheers!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Serious Lack of Professionalism’ is closed to new replies.