Plugin activation hooks

Attention all pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party authors:

If you were using register_activation_hook() to also handle updates from older versions of your plugins, you will not be able to do so any more in WP 3.1: [16012]

The activation hook is now fired only when the user activates the plugin and not when an automatic plugin update occurs. This is consistent with how the deactivation hook works.

There is a proposal for a register_update_hook() instead: #14912

Also, the callbacks for de/activation can now accept a networknetwork (versus site, blog) activation flag:

https://core.trac.wordpress.org/ticket/14170#comment:30

There was some ancient code in WP::parse…

There was some ancient code in WP::parse_request() that looked in $GLOBALS when setting up query vars.

This is no longer the case: [15796]

#3-1, #dev-notes

Trac Component Cleanup

As discussed in yesterday’s meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area., here’s a list of proposed changes to the Components in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:

1. Merge Optimization into Performance: they’re basically the same

2. Remove JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.: tickets should be moved to specific features, like Menus, Widgets etc.

3. Create Libraries component: tickets dealing with upgrading third party libraries, like jQuery or SimplePie, should go there.

4. Merge TinyMCE into Editor: there should be a single component that deals with the editor as a whole.

Thoughts?

After this is done, I plan to document each component in the Codex, so that we have a clear description of what goes where.

Menu Management UI

Here’s a quick preview of the new menu management adminadmin (and super admin) page (still alpha stage).

It highlights the dropdown section, which is the only unfamiliar element. All the rest are borrowed from the widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. management screen.

Feedback on the UIUI User interface is very welcome, either here, or on the dedicated ticketticket Created for both bug reports and feature development on the bug tracker.: #11817.

#video