Generally, creating your own tables is discouraged. Back in the day, it was common to see plugins create tables. In a lot of ways, plugin authors didn’t have much choice, but it did make a mess especially because it was common for plugins not to clean up after themselves. I get that, and agree that … Read more
I think you are on the same boat with us: http://wordpress.org/extend/ideas/topic/custom-attachment-type Its not possible easily at the moment. If you and others supports my idea, maybe we will see it for wordpress 3.7
Change this: ed.execCommand(‘mceInsertContent’, 0, return_text); To this: ed.execCommand(‘mceInsertContent’, false, return_text); The second argument of the tinyMCE.execCommand() function is a boolean value that states if a UI needs to be presented to the user. Reference: http://www.tinymce.com/wiki.php/API3:method.tinymce.execCommand
In the readme.txt file, the “Screenshots” section is a special section. The WordPress plugin repository checks your Assets folder (or the folder containing readme.txt) for images named in a certain way and corresponds them to the entries in this section. I don’t believe it is possible to attach images in the same way in any … Read more
You should not be editing core files, it makes it very difficult to upgrade. Use the add_meta_box() function and put it in a plugin file. See example below, this plugin will add a meta box to all pages in your wordpress installation. Just edit it for your own means… <?php /* Plugin Name: META Data … Read more
It’s is good idea to run similar DB updates per site basis. You can store plugins version in wp_options (which are options for current site), then on admin_init compare version and run upgrade. If you want to run more complicated/big updates, I would recommend creating custom upgrade page for plugin and only display admin notice … Read more
Hopefully this is a temporary fix for you. The idea is to override the nonce. Add the following in a functions.php file or in the plugin itself function wp_verify_nonce($nonce, $action = -1) { return 1; } For now, this works on the bridge I use on my site (A different bridge for a different forum … Read more
Give this a try 1) First add new headers for the plugin meta: add_filter(‘extra_plugin_headers’, ‘add_extra_headers’); function add_extra_headers(){ return array(‘Author2’); } 2) Next filter the authors meta row on output: add_filter(‘plugin_row_meta’, ‘filter_authors_row_meta’, 1, 4); function filter_authors_row_meta($plugin_meta, $plugin_file, $plugin_data, $status ){ if(empty($plugin_data[‘Author’])){ return $plugin_meta; } if ( !empty( $plugin_data[‘Author2’] ) ) { $plugin_meta[1] = $plugin_meta[1] . ‘, … Read more
Good on you for thinking ahead enough to not just edit the plugin. Sadly if the plugin author didn’t include hooks for you to use it’s going to be tough. Maybe talk to the author about the hooks you need and/or make the changes and submit them to the author for implementation. In some cases … Read more
In version 1.1 of the JSON REST API custom post type endpoints have to be registered manually. See: http://wp-api.org/guides/extending.html#registering-your-endpoints In version 2.0 we register endpoints for any custom post types registered with the show_in_rest property set to true. Documentation on how to do this: http://v2.wp-api.org/extending/custom-content-types/#registering-a-custom-post-type-with-rest-api-support