There’s no official github repo.
https://plugins.trac.wordpress.org/report/10?PLUGIN=debug-bar is probably the best place to submit patches. Issues can be submitted in the forum here.
Any chance of it being added to GH ?
Creating patches for plugins in trac is a nightmare IMHO.
You can create diffs from Github easily and submit those to Trac.
I’ll create a unofficial mirror for myself on github this week sometime, but note that it’ll only get the diffs in front of me, and that I’m only one of the many maintainers of the plugin.
Appreciated & understood.
Considering there are more maintainers (though not very active over the last few years, but you) and the official author is listed as WordPress.org, would an official GH repo under the WP or the Auttomatic GH account be an option ?
The thing is, if you look at trac there are issues there which haven’t been touched for years. Even ones which include a patch…
For whatever reason, that channel clearly isn’t working.
The plugins trac is the canonical location for this plugin.
Sorry, not sure what you mean ?
There’s no official github account for it.
You can post issues in the forums, or on the plugins trac (with diffs attached, which you can generate from Github) https://plugins.trac.wordpress.org/report/10?PLUGIN=debug-bar they’re the official locations.
You can submit PR’s to my personal mirror of the code, but no promises if I’ll ever get a chance to follow up on them https://github.com/dd32/debug-bar
@dd32 Hi Dion,
Appreciated & understood.
I’ve taken some time to go through my local changes & some of the issues on the forum and such.
Felt to me like this plugin could really do with some TLC 😉
What I’ve ended up with is 17 (!) different branches with changesets. I’ve tried to keep each changeset as small as possible for easier review.
There was only one in which that really was not possible as all the changes intertwined. In that case, I’ve split the branch in a number of individual commits which show the steps taken.
I’d be happy to add them to trac, but it would be great if you would be willing to give them the once-over before I create the patch files.
I’ll send the branches in as PRs to your unofficial GH repo for review.
As altogether it’s a lot, I’ve also created a develop branch in my own fork which incorporates all the changes, solves the merge conflicts and includes the below changelog & updated minified files and such.
Might be easier to test with that:
https://github.com/jrfnl/debug-bar/tree/develop
= Trunk =
* [Bugfix] PHP Error logging was only started when the admin bar was initialized which meant it did not catch nor show any errors generated before that point.
* [Bugfix] Deprecated notice logging was only started when the admin bar was initialized which meant it did not catch nor show any errors generated before that point.
* [Bugfix] Fix some error notices for PHP 5.2.
* [Bugfix] Diminish bleed through of front-end CSS styling.
* [Bugfix] Added the missing message text for deprecated arguments.
* [Bugfix] Fixed the classification of the various deprecated notices – previously all would be seen as functions.
* [Bugfix] Prevent things looking weird when the current locale is RTL based.
* [Enhancement] Added logging of PHP strict, deprecated and silenced error notices to the PHP panel.
* [Enhancement] Added logging of deprecated constructors to the deprecated panel.
* [Enhancement] Add a new panel showing ‘doing it wrong’ notices.
* [Enhancement] Even though display of deprecated/doing it wrong and other notices is not send to the screen – as they are displayed in their respective debug bar panels instead -, *do* continue to send them to the error log if one has been set up.
* [Enhancement] Improve usability by showing error counts in the panel menu for PHP/Deprecated/JS/Doing It Wrong.
* [Enhancement] Improve usability by colourizing the button in the admin bar late. This allows for the button to show there are warning or notices even after the button was created.
* [Enhancement] Improve usability by also colourizing the button in the admin bar for Deprecated/Doing it Wrong notices.
* [Enhancement] Improve readability of the WP Query – Queried object information.
* [Enhancement] Introduce the debug_bar_enable filter which allows for selectively giving access to the debug bar for additional users, such as site-admins in a multi-site environment.
* [Enhancement] Allow for large(r) number of add-ons in the panel menu.
* [Enhancement] Throw deprecated constructor notices for Debug Bar plugins using the old constructors.
* [Enhancement] The Debug bar plugin is now fully translatable. If you’d like to translate the plugin to your own language, head on over to [GlotPress](https://translate.wordpress.org/projects/wp-plugins/debug-bar).
* Minor refactoring
I’ve also created some screenshots, highlighting some of the more visible changes:
http://snag.gy/xywCf.jpg
http://snag.gy/5oCfB.jpg
http://snag.gy/Qjm1S.jpg
http://snag.gy/OPSPS.jpg
http://snag.gy/fXKsO.jpg
Hope this helps.
If you don’t have the time, I’ll just add each changeset to trac in a week or two.
Smile,
Juliette
@dd32 Hi Dion,
Just wondering if you’ve had a chance to look through some of the changes I suggested in the PRs.
Apart from PR #1 and #17, all the other changes are pretty small and self-contained.
Not to worry if not, though I intend to start adding the issues to trac and creating the patch files over the next few days.
Smile,
Juliette
@jrf Sorry, I’ve been busy and haven’t had the chance to setup automation of it.
I want to sync the individual commits back to plugins.svn.wordpress.org, but can’t easily do that from Github right this moment. I’ll get something setup this weekend.
@dd32 That sounds awesome! Let me know if there’s anything I can do.
