There’s certainly no need to name plugin files with prefixes (although some plugin authors like to do this). I suspect the advice you read was referring to functions within your plugin files. Structuring you plugin folders as you suggest (using a class folder) is fine. See this link for more information on writing plugins: http://codex.wordpress.org/Writing_a_Plugin … Read more
Strictly from a MySQL Point-of-View SHORT VERSION MyISAM Storage Engine Table locks Writes are first come, first serve Reads slow down writes from initiating InnoDB Storage Engine Row locks Transactions (non blocking) Deadlock may occur when updating indexes LONG VERSION If the underlying tables use the MyISAM Storage Engine, row locks are not possible. Each … Read more
Basically, you filter ‘the_content’ and add a button. Okay, it might be slightly more complicated: You need to send a mail per wp_mail(). You need some spam protection: a hidden text field which should stay blank and a nonce field. You may want to restrict the pages where the button form will be displayed: On … Read more
Register an activation hook and then redirect the user’s browser when you’re done installing your plugin. function myplugin_activate() { // TODO: Install your plugin here. // I don’t know of any other redirect function, so this’ll have to do. wp_redirect(admin_url(‘options-general.php?page=myplugin_settings’)); // You could use a header(sprintf(‘Location: %s’, admin_url(…)); here instead too. } register_activation_hook(__FILE__, ‘myplugin_activate’);
On a parallel thread over on the WordPress hacks forum, someone suggested using in_the_loop() and that works some of the time, with some plugins that use either the_content and/or the_excerpt, but not all of the time with all the plugins I’ve been testing against. Likewise, I’ve now done further testing using is_main_query() and that works … Read more
There is no built-in autoloader in WordPress. But other plugins or a theme might have registered an autoloader, and depending on the order of execution these are called earlier or later than yours. Update 21. 08. 2014 This answer is no longer what I would recommend. Do use an autoloader if you need one. The … Read more
I think you could get around this by pre-running the shortcodes on the page by applying the content filters before the header is output. This should allow any internal shortcodes run inside the included post to add any action hooks properly and thus any needed stylesheets/resources. add_action(‘wp_loaded’,’maybe_prerun_shortcodes’); function maybe_prerun_shortcodes() { if (is_page()) { global $post; … Read more
You personally might not need or rely on the WP REST API, but clearly Contact Form 7 does. And so does WordPress core. Especially future versions (think Gutenberg) will heavily rely on the REST API and won‘t work without it. There might be plugins that disable the API, but that‘s at your own risk and … Read more
Hi @Grant Palin: The register_post_type() function is really agnostic to theme or plugin; you can use it in an ‘init’ hook in either place, it really depends on what you are trying to accomplish. For example, if I’m setting up a custom site for a specific client I’ll probably just register the post types in … Read more
The instance of this class is made global by WPML, so this should work: if ( ! empty ( $GLOBALS[‘sitepress’] ) ) { add_action( ‘wp_head’, function() { remove_action( current_filter(), array ( $GLOBALS[‘sitepress’], ‘meta_generator_tag’ ) ); }, 0 ); }