Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Mike

    (@mromp2103)

    I did not intend to turn this into a support thread as I no longer need this plugin and have noticed no real difference in page load times since disabling it. I only wanted to suggest that you create proper documentation and possibly better error handling, and to warn others that anything other than a cookie-cutter setup may be difficult to troubleshoot.

    If PHP is unable to access a file, then there should be a clear error message stating as much (there is none whatsoever). Although it this case, it was able to delete the file just fine with the “Clear Logs Now” button. Before doing so, its last entry was from 2021 so it was working at some point.

    And I’m sorry, but there is no list of API permissions on the plugin settings page. See here. I vaguely remember better information in the first few pages of the wizard when I first set it up over a year ago, but once you have gone through that, it is stuck on the third page. Regardless, that doesn’t change the argument that this information belongs in the documentation, which again doesn’t really exist.

    Thread Starter Mike

    (@mromp2103)

    I’m sorry, but a cherry-picked FAQ is not a replacement for proper documentation. And despite your experience, everything I stated is happening for something that was working perfectly. Log verbosity is high and logging on, but there is no log file and no error. The “documentation” doesn’t even mention logging or where to find the log file. For what it’s worth, in this state, clicking “Download Log File” simply goes to the WP dashboard and no log file is delivered (because it doesn’t exist).

    I also imagine most of your setups involve the much less secure API key rather than a token with specific rights, which is where most of the challenges occurred when first setting it up. On that note, nowhere in the “documentation” does it even list the API token settings — you need to dig into forum posts to even find it.

    Your point on support for a free product is valid and I apologize. I was hasty and frustrated with the lack of documentation and reacting to certain responses others had received. Regardless, I have moved on from this plugin and wish you the best.

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