I’m not entirely sure this is the right place for this question, but I can’t say I know of a better place. 🙂 Your rough proposal is a valid way of building said system, but I would argue that you’re losing all of the advantages of using WordPress with the stated method. By creating a … Read more
Yup, you certainly can. At bare minimum, just require the plugin’s main file inside your plugin file. You’ll just need to activate YOUR plugin, but you’ll still have function from the included plugin. require_once ‘/otherplugin/main-file.php’; If you want to make it more sophisticated, you could set up a composer.json file in your plugin, which could … Read more
While I can’t easily spot right now what is the cause of the bug, it is obvious that your approach is just wrong on two fronts The uploads from media library have no context, or at least it is not trivial to find out a context. An upload of font file by itself do not … Read more
I’ve used several popular plugins on my multisite without problems. The only issue I had was when I found that a plugin wasn’t working on a sub-site like I thought it should. Turns out that was my fault – the plugin wasn’t activated/enabled on that sub-site. Doh! But it all depends on how the plugin … Read more
Here’s an alternative way to only make the product post type searchable, from a plugin code: <?php /** Plugin Name: Product Search Only **/ add_filter( ‘register_post_type_args’, function( $args, $post_type ) { $args[‘exclude_from_search’] = true; if( ‘product’ === $post_type && (bool) $args[‘public’] ) $args[‘exclude_from_search’] = false; return $args; }, 999, 2 ); Here we modify the … Read more
You can wrap the code which you want to limit using the current_user_can() function. if( current_user_can(‘editor’) ) { // true if user is an editor } Depending on what you are trying to limit, you can put this conditional around the hook or action that you are adding, or use it to wrap specific functionality … Read more
How to develop a wordpress plugin for front-end user?
Saving post meta
More research at the WordPress Codex and related sites for current (2016/2017) solutions … the following tested and works fine … ` defined(‘ABSPATH’) or die(‘No direct file access allowed!’); // Modify post content function myplugin_filter_content($content) { return $content . ‘ Almost an error message but not quite. ‘; } add_filter(‘the_content’, ‘myplugin_filter_content’); function schema_TinyMCE_init($in) { $props=”@[id|class|style|title|itemscope|itemtype|itemprop|datetime|rel],div,dl,ul,dt,dd,li,span,a|rev|charset|href|lang|tabindex|accesskey|type|name|href|target|title|class|onfocus|onblur]”; … Read more
admin-ajax.php returns “No Script Kiddies!” sometimes