automattic / developer Goto Github PK
View Code? Open in Web Editor NEWIn your WordPress, developing locally
Home Page: http://vip.wordpress.com
License: GNU General Public License v2.0
In your WordPress, developing locally
Home Page: http://vip.wordpress.com
License: GNU General Public License v2.0
=== Developer === Contributors: automattic, batmoo, Viper007Bond, nbachiyski, tott, danielbachhuber, betzster, nprasath002, nickdaugherty Tags: developer, development, local Requires at least: 3.4 Tested up to: 4.3 Stable tag: 1.2.6 License: GPLv2 or later License URI: http://www.gnu.org/licenses/gpl-2.0.html A plugin, which helps WordPress developers develop. == Description == A plugin, which helps WordPress developers develop. This plugin will help you optimize your development environment by making sure that you have all the essential tools and plugins installed. If you'd like to check out the code and contribute, [join us on GitHub](https://github.com/Automattic/developer). Pull requests, issues, and plugin recommendations are more than welcome! We would like to thank Ejner Galaz for letting us use the `developer` slug in the WordPress.org plugin repository. == Installation == 1. Upload the `developer` folder to your plugins directory (e.g. `/wp-content/plugins/`) 2. Activate the plugin through the 'Plugins' menu in WordPress 3. Follow the instructions == Frequently Asked Questions == = Why are there no FAQs besides this one? = Because you haven't asked one yet. == Screenshots == 1. On activation, the plugin prompts you to specify what type of developer you are. This is used to configure the plugins checks. 2. On activation, the plugin does a quick check to see if you have essential developer plugins installed. 3. With one click you can install and activate the plugin. 4. The plugin's settings page (Tools > Developer) will check to make sure your environment is correctly configured, including plugins, constants, and other settings. == Changelog == = 1.2.6 (2015-11-14) = * Remove MP6 * Fix strict standards notice * Fix PHP Notice in `is_dev_version()` = 1.2.5 (2013-10-18) = * Don't recommend Pig Latin for VIP * Fix cache key length by hashing relevant data = 1.2.4 (2013-10-08) = * Don't recommend Beta Tester if we have a dev version of WordPress * Fix cache key length = 1.2.3 (2013-09-17) = * Add WP-CLI 0.11.2 compatibility * WP-CLI: Mark selected type as active * Fix strict errors in upgrader = 1.2.2 (2013-08-09) = * Added WP-CLI command * Removed Grunion Contact Form because it's part of Jetpack = 1.2.1 (2013-06-18) = * Added MP6 to recommended plugins * Added Koop's Debug Bar Console to recommended plugins = 1.1.6 (2013-04-08) = * Made purpose of activate/install links on Settings page more obvious * Added link to full plugin details on Settings page (opens in Thickbox) = 1.1.5 (2013-04-05) = * Added ability to define multiple project types for plugins * Added ability to define project types for constants * Added Jetpack to recommended plugins and constants = 1.1.4 (2013-04-03) = * Added plugin descriptions to installation and settings pages = 1.1.3 (2013-04-02) = * Added improved error reporting * Added [Log Viewer](http://wordpress.org/extend/plugins/log-viewer/) to recommended plugins. Props to @rockaut for the suggestion = 1.1.2 (2013-01-29) = * French localization. Props [fxbenard](https://github.com/fxbenard) * Replaced Reveal IDs with Simply Show IDs. The former never installed. * Bug fix: Show a few plugins as active when they're actually active. = 1.1.1 (2012-08-30) = * Fix piglatin slug, props bobbingwide = 1.1 (2012-08-30) = * New "WP.org Theme" project type for developers building themes for self-hosted installs with a number of sweet plugins recommended by the WordPress.com Theme Team. * Simplify some of the wording across the plugin. * Added John Blackbourn's [User Switching](http://wordpress.org/extend/plugins/user-switching/) is now a recommended plugin for all projects. * Added [Pig Latin](http://wordpress.org/extend/plugins/pig-latin) plugin to help developer i18n their code. * Added resources for all projects. * Bug fix: don't show installation prompt in network admin. = 1.0 = * Initial Release
Not sure if this is something that should be fixed in the handbook, or in this plugin.
This page - https://make.wordpress.org/themes/handbook/get-involved/become-a-reviewer/ - lists the plugins you need to install when doing theme reviews, and says that you can install all of them through the Developer plugin. However, Query Monitor is not in the list of suggested plugins to install after activating the Developer plugin.
I receive the following error when installing recommended plugins:
Declaration of Automattic_Developer_Empty_Upgrader_Skin::request_filesystem_credentials() should be compatible with WP_Upgrader_Skin::request_filesystem_credentials($error = false, $context = false, $allow_relaxed_file_ownership = false) in /vagrant/content/plugins/developer/includes/class-empty-upgrader-skin.php on line 5
Recommended by Markus Fischbacher: http://wordpress.org/extend/plugins/log-viewer/
Recommended set of plugins and functionality for building an WP.com Enterprise site.
We're looking to do automated installs of the developer plugins for our clients, is there a possibility of adding an option called "test site for hosting provider" automatically during the install?
We use wp-cli to add and activate the plugin. It'd be nice to not have the customer answer the question the second they log in.
Using developer plugin I cannot seem to be able to activate Theme Check.
It seems to work but when I refresh it is still inactive.
And have it look for the JETPACK_DEV_DEBUG
constant.
The transient name a8c_developer_plugin_details_{plugin}
causes the option_name
in the options table to exceed the maximum length when the transient timeout is stored.
Related ticket on core Trac: http://core.trac.wordpress.org/ticket/13310
get_plugin_details
stores the entire API return value in transient. For some plugins (like Jetpack, with big changelogs), that's a lot of data. We should only store the data we need.
Going through the install/activate step for each plugin is annoying. Let's make it as one-click as possible.
Props to Siobhan McKeown for reporting this one.
It's a tool, not a setting. Let's be semantically correct.
Would it be possible to include Debug Meta Data plugin in Developer plugin?
https://wordpress.org/plugins/debug-meta-data/
Currently I person who's not acquainted with what all plugins do will be lost, not knowing which plugins to install and which not. And this is the exact target audience of the developer plugin.
We need to either add short descriptions, or links to the cool popup plugin pages, which are seen when searching or updating plugins.
Props to Siobhan McKeown for reporting this one.
When I have a 'recommended plugin' active network-wide on my site, it is listed as inactive on the Tools -> Developer screen.
Not sure if this project is really active anymore, but I figured I'd mention the issue here anyway.
If you install the plugin, then go to: /wp-admin/tools.php?page=a8c_developer
-- find something that says NOT INSTALLED
-- then click on the title for that plugin.
The modal will pop up and it will say:
You do not have sufficient permissions to access this page.
Here is some output that might be useful:
$pagenow
string(18) "plugin-install.php"
$_wp_submenu_nopriv
array(5) {
["index.php"]=>
array(1) {
["update-core.php"]=>
bool(true)
}
["link-manager.php"]=>
array(2) {
["link-manager.php"]=>
bool(true)
["link-add.php"]=>
bool(true)
}
["plugins.php"]=>
array(2) {
["plugin-install.php"]=>
bool(true)
["plugin-editor.php"]=>
bool(true)
}
["edit-tags.php?taxonomy=link_category"]=>
array(2) {
["link-manager.php"]=>
bool(true)
["link-add.php"]=>
bool(true)
}
["themes.php"]=>
array(1) {
["theme-editor.php"]=>
bool(true)
}
}
and for good measure:
$_wp_menu_nopriv
array(1) {
["edit-tags.php?taxonomy=link_category"]=>
bool(true)
}
The impact of course is installing any of those plugins OR reading about them in the modal isn't possible.
It makes it really easy to switch between different users and see what they're seeing
There's issue with VIP Scanner WordPress.com Rules update notice, you'll get it all the time. I posted about it on WP.org support forum, but maybe moving my suggested solution here would move things big faster.
I think "VIP Scanner WordPress.com Rules" is causing this. WP.com VIP Scanner extension PHP file also has plugin header, >but it misses version tag. It won't be a problem if this plugin where into separate folder, I guess it's related to how WP checks >plugin updates.
Proposed fix would be passing same version for "VIP Scanner WordPress.com Rules" as VIP Scanner has.
Originally posted on WP.org forums.
Notice: Trying to get property of non-object in /srv/www/wp-content/plugins/developer/developer.php on line 847
Throws an error when get_preferred_from_update_core
returns false. Needs isset( $cur->response )
check before using it.
Suggested by Jon Brown
If a plugin install fails, it usually returns an instance of WP_Error
, but not always. On developer.php
, line 397, we need to check that $install_result
is a WP_Error
before calling get_error_message()
, because it can be a boolean
. Otherwise, you can get:
Fatal error: Call to a member function get_error_message() on a non-object in /{Web Server}/trunk/wp-content/plugins/developer/developer.php on line 397
If the WordPress install is using an SVN checkout of trunk, the developer plugin should detect that, reflect it in the UI, and not prompt to install the beta tester plugin
In Quickstart we don't show the plugins menu, so it's hard to find a way to deactivate recommended plugins once they're activated. I don't think this issue is specific to Quickstart, just more obvious. We should be able to deactivate plugins from the same place they're activated.
Hi!
Since this plugin promotes other plugins.. I would like to humbly submit my plugin.
https://wordpress.org/plugins/view-admin-as/
It has some crossover functionalities with User Switching since this one also handles switching users.
Info: (copied from wordpress.org):
Overview / Features
Module: Role defaults
Features planned for future releases:
It would be awesome if this plugin could be featured. Take a look and let me know!
Regards, Jory
When plugin installation or activation fails, we present a cryptic "Error!" message. We should report what the error actually is so the user can correct it.
Now that we have Jetpack as a suggested plugin, which includes an improved version of Grunion (though not branded as that), we should remove Grunion from the list as it's redundant and no longer relevant.
我很抱歉
Is there a way to turn off the "... accepted your friendship request" emails for the friendships created automatically by the plugin? It seems as if all new users receives mass notification emails from the automatic friend requests.
Lynne
RTL Tester
Regenerate Thumbnails
Theme Check
These show as inactive on the Developer admin page, even when active.
I am getting this error:
Strict Standards: Declaration of Automattic_Developer_Empty_Upgrader_Skin::request_filesystem_credentials() should be compatible with WP_Upgrader_Skin::request_filesystem_credentials($error = false, $context = false, $allow_relaxed_file_ownership = false) in /srv/www/wordpress-default/wp-content/plugins/developer/includes/class-empty-upgrader-skin.php on line 5
1
When trying to activate plugins within the developer plugin page.
I am using Mac Yosemite and vvv.
Thanks
A few improvements related to the lightbox and admin view for installing recommended plugins:
Currently, constants cannot be recommended based on the project type, which is problematic when we need to add plugin specific constants, such as JETPACK_DEV_DEBUG
.
Should allow constants to be defined in the same way plugins are.
Example: monster-widget is useful for Theme Developers and WP.com VIP.
Hello good people. This plugin https://wordpress.org/plugins/what-the-file/ is super and should be invited to the party.
From the forums, the "Developer" link should only be added to the admin bar if the user has the appropriate permissions
All ajax calls should be updated to use the Deferred handlers .done()
and .fail()
instead.
What the title says.
causes fatal error on a wordpress.org supported php version.
For the theme developer mode, we should allow installing the Theme Unit Test sample data: http://codex.wordpress.org/Theme_Unit_Test
Props @mfields
Core doesn't include the un-minified versions of external JavaScript libraries. But sometimes during development errors in those libraries occur and it would be useful if we could debug the source code directly.
For more details of where to find the latest versions, see: http://make.wordpress.org/core/2012/08/29/minified-versus-development-scripts-and-min-js/
On activation of this plugin, I'm unable to select the type of website I'm developing. I tried clicking on Theme for a self-hosted WordPress installation and my cursor won't select it. Any suggestions?
I'm setting up a VM for a client which installs and enables this plugin when running in a local development environment, and I would like to find a way to bypass having to have them select "Developing a plugin for a self-hosted install" and opting out of the other recommended add-ons. Is this possible? I can see where the code is written in admin_init
but I haven't been able to find a way to suppress or pre-fill the options.
Should include the following plugins (suggested by the WordPress.com Theme Team):
If possible, throw in a promo to _s and other cool starter themes.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.