#2365 (Plugin Directory: Restore links to previous versions of plugin) – Making WordPress.org

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.

visit WordPress

Clarification of Guideline 8 – Executable Code and Installs

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.

visit WordPress

#37646 (Make wp-settings.php a series of do_actions()) – WordPress Trac

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.

visit WordPress

WordPress APIs ” WordPress Codex

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.

visit WordPress

Revised Guidelines Are Live – Make WordPress Plugins

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.

visit WordPress

Changeset 38833 – WordPress Trac

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.

visit WordPress

Forums Status Update (Sept 12) – Make WordPress Plugins

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.

visit WordPress

WordPress Plugin Directory – Make WordPress Plugins

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.

visit WordPress

Security Alert: Httpoxy – Make WordPress Plugins

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.

visit WordPress

Known issues with “pre-commit” to the plugins SVN – Make WordPress Plugins

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.

visit WordPress

Create a free website or blog at WordPress.com.

Up ↑

%d bloggers like this: