Working good but would deserve to be improved

  • Hello, thank you for packaging this snippet in a plugin.
    Few UX issues in my opinion though:

    • a major one is the hardcoded $max_length value of 140 characters. In my case I needed to retrieve the full output of a “print_r($array)” command, much longer… The plugin’s codebase is not that big so it is fine to change the value manually, but the point of a such a plugin is not to have to go through the code… It should really have an input box somewhere to change the value from the UI (or at least a much higher value by default).
    • two minor ones:
      • Clicking “Clearing warning” did nothing. Bug? Desactivating the plugin being object of study removed the warning.
      • Remind the user from within the dashboard on how to enable WP_DEBUG if it is detected as “OFF”.
Viewing 1 replies (of 1 total)
  • Plugin Author AVATTAVA

    (@avattava)

    Hello @cpoakl

    Thank you for your technically detailed review. We feel flattered, indeed.

    We absolutely agree on the UX issues and we are working on that, we can assure you.

    $max_length value of 140 characters allows to inspect a glimpse of the unexpected output’s error, in most screen sizes (apart from mobile where usually people are not fixing WP websites’ issues or even developing plugins). The “buggy” plugin that we use for tests and development outputs a diluvium of 57000 crazy characters and we cannot “print” that abnormal verbose for a normal user.

    We also prefer to send minimalistic plugins for review by the www.ads-software.com, since there are more than 450 plugins awaiting review (numbers have exploded with the advent of AI and the na?ve illusion that plugins will “work out of the box”) and it becomes less time consuming for the Plugin Review Team to allow a new plugin on WordPress plugins’ repository.

    Kind regards.

Viewing 1 replies (of 1 total)
  • The topic ‘Working good but would deserve to be improved’ is closed to new replies.