چۈشەندۈرۈش
This plugin has been closed as of 2025-يىلى 8-ئاپرېل and is not available for download. This closure is temporary, pending a full review.
باھالاشلار
2024-يىلى 12-ئاپرېل
1 reply
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».
تۆھپىكار ۋە ئىجادكار
«Debug Activation Errors 2.0» كودى ئوچۇق يۇمشاق دېتال. تۆۋەندىكى كىشىلەر بۇ قىستۇرمىغا تۆھپە قوشقان.
تۆھپىكار«Debug Activation Errors 2.0» نى تىلىڭىزغا تەرجىمە قىلىڭ
ئىجادىيەتكە قىزىقامسىز؟
كودقا كۆز يۈگۈرتۈپ، SVN خەزىنە تەكشۈرۈپ ياكى RSSئارقىلىق ئىجادىيەت خاتىرىسىگە مۇشتەرى بولغىلى بولىدۇ.