WordPress uses the ‘plug-in slug’ to identify a plug-in (and uses this as an ‘id’ for plug-in updates, though its not clear how, as the code isn’t published). The plug-in slug is determined by the location of the .php file header containing the comment header necessary for plug-ins. (see source) So if your main plug-in … Read more
As the Codex tells us you can add another parameter to the function that holds the version number. wp_register_script( $handle, $src, $deps, $ver, $in_footer ); $ver String specifying the script version number, if it has one, which is concatenated to the end of the path as a query string. If no version is specified or … Read more
If you are comfortable with Composer — by all means that’s precisely what you should use to manage your WordPress site! I have made a mini site Composer in WordPress on topic in general and your cornerstones will be: johnpbloch/wordpress package for WP core WPackagist for proxying official plugin repo
This question has been answered before and therefore should likely be marked and closed as duplicate. In short, it is viable, of course, for example we use Git to version control development of our sites. We control the versioning of the database somewhat differently in the form of incremental backups outside of the git workflow. … Read more
I have tested this at home (~ 3 hosts) for some time now, trying different scms (RCS, Subversion, git). The setup that works perfectly for me right now is git with the setgitperms hook. Things you need to consider: Handling of file permissions and ownership RCS: does this natively Subversion: last I tried, you needed … Read more
Do not rename or modify the sample files unless such modifications are intended for contribution – they are there for reference. The files wp-config.php and wp-tests-config.php are explicitly ignored by .gitignore. Simply create them as new files yourself (or, if you’d like to use the sample files verbatim create symlinks to the sample files) to … Read more
As expected, there is a JSON API. Just had to dig a lot in the codex! https://codex.wordpress.org/WordPress.org_API#Plugins
I answered this question on Stackoverflow, and reposting the answer here. We would never edit it there though, it’d be impossible, quite, the CF7 plugin was never conceived for anything more complex than a contact form unfortunately. You may want to play around with the Smart Grid-layout extension which was specifically designed for creating and … Read more
On the register_activation_hook() function of the new plugin use the function deactivate_plugins() (or deactivate_plugin_before_upgrade()) and deactivate the older plugin and also delete the data with delete_option. If you will also delete the files, then use the function uninstall_plugin($plugin); maybe delete_plugins( $plugins, $redirect=”” )
well that depends on what you want to do, but if it is easier for you to edit that template it will be better that you can control all the output of it.. fx like this function add_require_scripts_files() { wp_enqueue_style(‘layout’, get_template_directory_uri().’/style.css’, array(), ‘1.0.0’, “all”); } add_action( ‘wp_enqueue_scripts’, ‘add_require_scripts_files’ ); and this what the function expects … Read more