Title: Jan Fabry's Replies | WordPress.org --- # Jan Fabry [ ](https://wordpress.org/support/users/janfabry/) * [Profile](https://wordpress.org/support/users/janfabry/) * [Topics Started](https://wordpress.org/support/users/janfabry/topics/) * [Replies Created](https://wordpress.org/support/users/janfabry/replies/) * [Reviews Written](https://wordpress.org/support/users/janfabry/reviews/) * [Topics Replied To](https://wordpress.org/support/users/janfabry/replied-to/) * [Engagements](https://wordpress.org/support/users/janfabry/engagements/) * [Favorites](https://wordpress.org/support/users/janfabry/favorites/) Search replies: ## Forum Replies Created Viewing 8 replies - 1 through 8 (of 8 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Monkeyman Rewrite Analyzer] Abandoned?](https://wordpress.org/support/topic/abandoned-56/) * Plugin Author [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [8 years, 10 months ago](https://wordpress.org/support/topic/abandoned-56/#post-9736410) * Hello [@enchiridion](https://wordpress.org/support/users/enchiridion/), * You can certainly take over the plugin. It only exists in the WordPress plugin Subversion repository, it’s not in a git repository yet. * Over the past years from time to time I have considered to update the plugin, but I haven’t done any serious WP (or even PHP) development in that period, so I never found the need or the time for it. I have considered integrating it into another existing developer plugin with more traction – first [Developer](https://wordpress.org/plugins/developer/), but that seems abandoned as well, so maybe [Debug Bar](https://wordpress.org/plugins/debug-bar/) would be a better choice now. * So depending on whether you want to continue it as an independent plugin or as an extension to something existing (or maybe even a hybrid – independent, but if it detects the Debug Bar extend it), we can decide how to go forward with the code. I think you still need access to the WP plugin Subversion repository if you want to publish it in the plugin directory, but you could do the main development via git and then via a git->svn bridge put it there. * Let me know what you want to do, and we will figure it out. I’ll send you a mail via your site so you have my contact details. * Regards, * Jan * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Drag-To-Share eXtended] [Plugin: Drag-To-Share eXtended] Share URL writing outdated](https://wordpress.org/support/topic/share-url-writing-outdated/) * [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [15 years, 4 months ago](https://wordpress.org/support/topic/share-url-writing-outdated/#post-2101795) * The share URLs are created in the `wp-dragtoshare-extended.js` file. See [my answer on the WordPress Stack Exchange](http://wordpress.stackexchange.com/questions/18416/plugin-drag-to-share-extended-share-url-writing-outdated/18537#18537) for (a bit) more details. * Forum: [Requests and Feedback](https://wordpress.org/support/forum/requests-and-feedback/) In reply to: [My plugin doesn't have a Trac Component](https://wordpress.org/support/topic/my-plugin-doesnt-have-a-trac-component/) * [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [15 years, 4 months ago](https://wordpress.org/support/topic/my-plugin-doesnt-have-a-trac-component/#post-1586681) * This has been discussed in a core Trac ticket: [No documentation (not possible?) to add plugins to Trac](http://core.trac.wordpress.org/ticket/16524). * > Problem is, the plugins trac doesn’t scale to 13,000 plugins. Otto and I have > been discussing some ways to start over and make it more viable, but we’re > not sure yet how we’d do it. * > Getting the plugins trac working properly is indeed on my todo list. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [Plugin directory “Last Updated” not changed after initial commit?](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/) * Thread Starter [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [15 years, 4 months ago](https://wordpress.org/support/topic/plugin-directory-last-updated-not-changed-after-initial-commit/#post-2099858) * I have sent a mail to the plugins team. I think this has been reported in the Trac as [Plugins display incorrect update date](http://core.trac.wordpress.org/ticket/16266). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Custom Metadata Manager] [Plugin: Custom Metadata Manager] Custom meta fields not appearing](https://wordpress.org/support/topic/plugin-custom-metadata-manager-custom-meta-fields-not-appearing/) * [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [15 years, 7 months ago](https://wordpress.org/support/topic/plugin-custom-metadata-manager-custom-meta-fields-not-appearing/#post-1973590) * I think there is [a small omission in the plugin](http://wordpress.org/support/topic/plugin-custom-metadata-manager-plugin-not-activate-on-new-post-page) that causes it not to load when you create a _new_ post, only when you edit an existing one. * If that is the case for you, you can fix it by adding the `post-new.php` value to the `$_pages_whitelist` array, as explained in my other forum post. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Taxonomy Terms List] [Plugin: Taxonomy Terms List] Move Content to Widget or Sidebar](https://wordpress.org/support/topic/plugin-taxonomy-terms-list-move-content-to-widget-or-sidebar/) * [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [15 years, 9 months ago](https://wordpress.org/support/topic/plugin-taxonomy-terms-list-move-content-to-widget-or-sidebar/#post-1816441) * I created a version of this plugin as a widget, and [posted it as an answer on your original question on the WordPress Stack Exchange](http://wordpress.stackexchange.com/questions/5394/list-a-current-posts-taxonomy-terms-in-a-widget-in-wordpress/6073#6073). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Plugin: Subscribe to Comments] Is this plugin dead? Are there alternatives?](https://wordpress.org/support/topic/plugin-subscribe-to-comments-is-this-plugin-dead-are-there-alternatives/) * [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [16 years, 3 months ago](https://wordpress.org/support/topic/plugin-subscribe-to-comments-is-this-plugin-dead-are-there-alternatives/#post-1538354) * Since it hasn’t been updated in such a long time, it uses some functions that are now deprecated. You can see all kinds of notices when you turn on `WP_DEBUG`. So yes, an update or a maintained alternative would be nice. * Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/) In reply to: [‘colors’ meta-css src (boolean) generates parse_url errors in _css_href](https://wordpress.org/support/topic/colors-meta-css-src-boolean-generates-parse_url-errors-in-_css_href/) * Thread Starter [Jan Fabry](https://wordpress.org/support/users/janfabry/) * (@janfabry) * [16 years, 9 months ago](https://wordpress.org/support/topic/colors-meta-css-src-boolean-generates-parse_url-errors-in-_css_href/#post-1335136) * I [reported](http://core.trac.wordpress.org/ticket/11820) this in the Trac, we’ll see what happens with it. Viewing 8 replies - 1 through 8 (of 8 total)