I found the problem. I didn’t realize this was a generic message for pretty much all errors. I stripped everything out of the activation routine (similar to above) and ran it… got no errors. Started adding “stuff” back. And it appears a call to flush() at the end of the activation function trying to force … Read more
You have to check if PHP mail is working in your server or debug WP’s mail, there are several ways to do this, I would first test if a basic PHP mail function works. The is as simple as running this from a PHP file or the command line: mail (‘[email protected]’, “Test”, “Test mail from … Read more
The init and plugins_loaded hooks are already run before a plugin is activated. That’s why your first code doesn’t work but the second does. Regarding your third code: there’s no need to run add_action(‘myplugin_activate’ … inside init. Not everything needs to be hooked to init. Just use add_action(‘myplugin_activate’, function(){ echo ‘myplugin is not allowed.’; die; … Read more
You can use detect_plugin_deactivation, function detect_plugin_deactivation( $plugin, $network_activation ) { if ($plugin==”parentplugin/parentplugin.php”) { deactivate_plugins(plugin_basename(__FILE__)); } } add_action( ‘deactivated_plugin’, ‘detect_plugin_deactivation’, 10, 2 ); Add this snippet in your plugin’s main file.
Take a look at after_switch_theme link But I would use hooks to insert the css for example in wp_head This link helps you get the directory of the theme, so you can create the css afterwards.
It was a caching problem with composer. I retroactively changed my composer.json, so I had to open my terminal and run composer dumpautoload to correct the cache.
You just add the content to your initial array. The most simple way is using the titles as array indices like this: $pages = [ ‘Login’ => ‘Some content’, ‘Dashboard’ => ‘Some other content’ ]; foreach ( $pages as $title => $content ) { if ( get_page_by_title( $title ) ) { continue; // skip this … Read more
WP needs all the required arguments – you skipped the one that tells it either a PHP file to use for output, or a function to run. From the Developer Site: /** * Register a custom menu page. */ function wpdocs_register_my_custom_menu_page(){ add_menu_page( __( ‘Custom Menu Title’, ‘textdomain’ ), ‘custom menu’, ‘manage_options’, ‘custompage’, ‘my_custom_menu_page’, plugins_url( ‘myplugin/images/icon.png’ … Read more
If I had to guess? The plugin activation hook is firing before the rewrite_rules_array filter is applied, resulting in the rules being flushed before you make changes to them. See here for the Codex-recommended implementation, using the wp_loaded action hook.
The register_activation_hook() is actually just a wrapper for add_action(‘activate_’ . $file, $function); and is only executed when a plugin is activated. This action/function is meant to be used by anything that should only execute once when the plugin is activated, things which would include stuff like adding custom terms to taxonomies create new database tables … Read more