Looking through that list, most plugins and themes haven’t been updated in the last couple of years. However there are few with lots of users: nextgen-gallery wysija-newsletters codestyling-localization wp-all-import profile-builder wp-filebase flash-album-gallery
With little old MCE editor so lively and quick, Matt knew in a moment it was a St. Gutenberg trick. More rapid than eagles his programmers they came, And Matt whistled, and shouted, and called them by name: As code that before WordPress would fly, Now they met with an obstacle, Saint Gutenberg, oh why?
diff –git src/wp-includes/class-wp-option-query.php src/wp-includes/class-wp-option-query.php new file mode 100644 index 0000000..9f7f5f5
It took a little longer than expected or desired, due to a couple serious issues. Not everything is perfect yet, but submissions are open. Some things are different. Most are the same. Instead of a link, you will now upload your zip directly. In doing so, the plugin slug will be assigned for you.
I went looking for this in reviewing the new Plugin Directory and primarily to see where things had moved to and found this particular feature completely missing now. I checked Admin as well to see if maybe I missed it, but nope, the links to previous versions of the plugin are completely gone now.
Sorry about the post-facto notice, there were a lot of moving parts and we got some things out of order when communicating between the multiple teams. Current Status Pending plugins are imported Approved (but not yet committed) plugins are being imported Rejected plugins have not yet been imported (though they will be …
Since Jetpack announced it installs themes, a number of people have asked if this is a violation of the 8th guideline: The plugin may not send executable code via third-party systems. And in specific, these two items: Serving updates or otherwise installing plugins, themes, or add-ons from servers other than WordPress.org’s Installing premium versions of the same plugin The short answer is no, it’s not, and yes, you could do this too.
As more robust and sophisticated plugins, themes, APIs, and systems start to use, rely on, and bend WordPress to their will, the need to override more & more pieces becomes apparent. While WordPress comes with a very handy set of default post types, taxonomies, APIs, helpers, wrappers, and tools, it may be desirable to unhook (or never load) certain pieces so that other pieces can take their place.
Posted a reply to [Plugin: CollabPress] Cause problems, on the site WordPress Support Forums: This was a JS conflict and is fixed in CollabPress 1.1.3. Thanks!
With the advent of the new directory being on the horizon, which allows us to easily hard-limit the number of plugin tags displayed, we have taken the time to change the guidelines. While minor updates to the guidelines (with regard to spelling, grammar, etc) are common, major changes are rare and we are striving to be more transparent about them.
I’d love to see this functionality added to the support forum. Images are a great way to show how things are broken. At the very least, it would be cool to show Cloudup (Automattic owned) hosted images inline with the post content.
The WordPress API stands for the WordPress Application Programming Interface. It can be separated into multiple API sections / topics. Each covers the functions involved in and use of a given set of functionality. Together they form what might be called the WordPress API, which is the plugin/theme/add-on interface created by the entire WordPress project.
I know the 4.7 ‘please test’ email went out a bit late (WordCamp US, blame Wapuu), but we did send it and just like last time, we’ve taken action the replies. If you reply and ask for a plugin to be closed, we close it. If your email auto-replies, we warn you once.
Thanks for the quick reply, a question still stands though: can it be turned into an option to be opted in by administrators? While it is clear that wordpress is checking for updates it isn’t clear that it is also leaking how many blogs and users are on the current installation.
Generally, the idea here is to have content that showcases various WP and default theme features and gives users an idea of what sort of site X theme will help them create.
* Hides the custom post template for pages on WordPress 4.6 and older * * @param array $post_templates Array of page templates. Keys are filenames, values are translated names. * @return array Filtered array of page templates.
We soft-launched them on the 20th, just to make sure we didn’t mess anything up. Those last few spelling and grammar edits are killer. However yes, the guidelines, reviewed and revised by the community are now the official Plugin Developer Guidelines. While I can hope they’re easily understood by all, I know that’s a fond wish.
Twenty Seventeen: Replace remaining Genericons with Font Awesome icons
From a technical point of view there aren’t many changes needed in core to support templates for all post types, but there may be some things to consider regarding the best way to go about it.
As sparrows’ tears shed steadily Make widest rivers filled,
Previously we ensured that the entry points to WordPress were parsable by PHP4 in order to display a friendly not-supported-php error message. However, for the last two years the main entry points have not actually parsed, and we’ve only added extra parse errors since it last worked in 3.9, so it’s time we just remove this ‘feature’.
Props melchoyce, laurelfulford, davidakennedy, grapplerulrich, manishsongirkar36, joefusco, smyoon315, b-07, rabmalin, mrahmadawais, hardeepasrani, implenton, acmethemes, claudiosanches, valeriutihai, pressionate, sgr33n, doughamlin, zodiac1978, tsl143, nikschavan, joshcummingsdesign, enodekciw, jordesign, patilvikasj, ryelle, mahesh901122, williampatton, juanfra, imnok, littlebigthing, mor10, samikeijonen, celloexpressions, akshayvinchurkar, davidmosterd, hiddenpearls, netweb, pratikchaskar, taggon, nukaga, ranh, yoavf, karmatosed, sandesh055, adammacias, noplanman, yogasukma, binarymoon, swapnilld, swissspidy, joyously, allancole, rianrietveld, sixhours, alex27, themeshaper, mapk, leobaiano.
REST API endpoints for your WordPress content. These endpoints provide machine-readable external access to your WordPress site with a clear, standards-driven interface, allowing new and innovative apps for interacting with your site. These endpoints support all of the following:
Props westonruter, valendesigns, utkarshpatel, stubgo, lgedeon, ocean90, ryankienstra, mihai2u, dlh, aaroncampbell, jonathanbardo, jorbin. See #28721. See#31089. Fixes#30937. Fixes#31517. Fixes#30028. Fixes#23225. Fixes#34142. Fixes#36485.
WP_Term_Query already supports querying terms by ‘slug’, ‘name’, and ‘term_taxonomy_id’. Its additional arguments allow us to generate nearly the same SQL queries as before. This change has one yuge benefit: the term queries are now cached.
When emailing zips, please make sure your email client and email service provider allow this. Increasingly, we have seen people testifying that they emailed us a file with a zip, but we never receive it. In doing some research, we’ve found that mail providers are now silent-killing large emails!
We’ve got a variety of resources to help you get the most out of WordPress. Your first stop should be our documentation, where you’ll find information on everything from installing WordPress for the first time to creating your own themes and plugins.
1 Sometimes a plugin gets partly (un)installed during automatic update due to failing to delete the plugin folder (in use error) or a request timeout. To be able to reinstall a plugin you then must delete it, either trough FTP or the proposed delete without uninstalling action.
Subscriptions should be working again. Feeds have _moved_ and I’m really sorry about that. Hopefully we’ll get an nginx redirect in there sooner rather than later but basically it’s this: `https://wordpress.org/support/plugin/akismet/feed/` We’re using WordPress now, so any time you see a view you want to follow in RSS, slap `/feed/` on the end and it will _probably_ work.
Filters and actions have been the basis of WordPress’ plugin functionality since time immemorial, they’ve always been a reliable method for acting upon the current state of WordPress, and will continue to be so.
Thank you everyone for being patient about this. This summer was spent re-writing and editing and tweaking the guidelines. I ripped them down, sat and spelled out what they meant, then I rewrote them to be more clear. Then I got the plugin review team to review the changes.
The WordPress Plugin Repository is rebranding as the WordPress Plugin _Directory_. As “directory” refers to the entire plugin hosting service (the site, VCS, etc) and “repository” conventionally refers more specifically to just a VCS (such as GitHub, SVN, etc), we feel this will be less confusing and more in-line with the other aspects of WordPress.org.
Now that I think about it, I might have just made some assumptions regarding the pattern name (have been doing too much work in that area lately). What you propose can indeed be called a Registry, provided that it never instantiates an object by itself, but only stores them.
Query: collapse several of the is_* methods using __call(). Add @method annotations.
You may have heard about this already. Even so, please read this post. Normally we email all possibly impacted developers directly. In this case, trying to generate a list gave me over 6 gigs of results. I trimmed it down, but given the volume of people using Guzzle and possibly using suspect code, it was more straightforward to post an alert.
The default CDN location for loading Twemoji images has changed, moving to a versioned subdirectory. This allows updates without needing to purge the CDN.
Have you seen this recently? $ svn ci -m ‘commit first version of plugin’ Adding trunk/readme.txt Adding trunk/my-cool-plugin.php Transmitting file data …….svn: E165001: Commit failed (details follow): svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output: *********************************** PHP error in: my-cool-plugin/my-cool-plugin.php: Errors parsing my-cool-plugin/my-cool-plugin.php *********************************** A couple weeks ago, the PHP “lint” part of the SVN pre-commit check was changed from using PHP 5.4 to using PHP 7.0.
The official plugin guidelines are currently found on DevHub under Detailed Plugin Guidelines. The older version now redirects (thank you!). Like the Codex and DevHub, we’re mid transition and apologize for any confusion when that redirect wasn’t happening.
Posts about WordCamp Europe 2016 written by WordPress.tv
For PHP 5.2, SPL can be disabled. As SPL provides the support for multiple autoloaders, this needs to be shimmed if not available.
WP_Term_Query is modeled on existing query classes, such as those used for comments and users. It provides a more consistent structure for generating term queries, and should make it easier to add new functionality in the future.
Introduces unit tests to check the Emoji CDN filters.
We are sorry that you are having trouble with Easy Updates Manager. Hopefully we are able to get this sorted out so that you can continue to use Easy Updates Manager. First off, what plugin are you referring to that was auto updating?
Timestamp: 05/13/16 04:41:45 (less than one hour ago) Author: rmccue Message: HTTP API: Replace internals with Requests library. Requests is a library very similar to WP_HTTP, with a high level of unit test coverage, and has a common lineage and development team. It also supports parallel requests. Location: Files:
There are hundreds of thousands of web hosts out there, the vast majority of which meet the WordPress minimum requirements, and choosing one from the crowd can be a chore. Just like flowers need the right environment to grow, WordPress works best when it’s in a rich hosting environment.