I found some info on changes in 3.2 that might be relevant: Aparrently, wp_tiny_mce_preload_dialogs() no longer exists from WP3.2 on. It got replaced by wp_preload_dialogs() which is now being called from wp_quicktags(). wp_quicktags, on his turn, is being called from the_editor() function. So, if you’re using the_editor() you no longer need to manually call the … Read more
Since the text is processed by _() function, then, of course, you can modify it using gettext filter. function change_update_notification_msg( $translated_text, $untranslated_text, $domain ) { if ( is_admin() ) { $texts = array( ‘There is a new version of %1$s available. <a href=”https://wordpress.stackexchange.com/questions/323927/%2$s” %3$s>View version %4$s details</a>.’ => ‘My custom notification. There is a new … Read more
There are actually 3 users that IIS access files with on .NET sites: IIS_IUSRS, IUSR, and NETWORK SERVICE Grant all 3 IIS users Read & Execute, List Folder Contents, Read permissions on the entire WP folder For file management (e.g. plugin/theme installation & updates), grant all 3 of the IIS users Full Control on the … Read more
You shouldn’t have any trouble … but before doing the upgrade I recommend you do the following: Backup everything Back up your theme Back up all of your plug-ins Back up your existing database This will allow you to “undo” the upgrade if needed. Check theme compatibility If you’re using a commonly available theme, check … Read more
Even more easy: open up the specific plugin directory; find the php file in which the version of the plugin is mentioned; change the version number to a high number (i.e. Version 1.1 to Version 100.1)
Yes, key (prefixed with string identifying it as transient) is used as option name when value is inserted in database.
Looking on Trac I found a ticket that discusses exactly this issue: Administrator should be able to change usernames This is what it all boils down to: Changing usernames could break permalinks To prevent this a lot more than just changing the username in the DB would need to be done. E.g. redirection from old … Read more
I know this is kind of a backwards way of doing it, but I suppose if you disable the possibility to upgrade the plugin, then you don’t need to worry about the plugin being overwritten. Change the plugin version number (in the plugins main file comment header) to something ridiculously high so it won’t recommend … Read more
Set the constant DISALLOW_FILE_MODS to TRUE in your wp-config.php: const DISALLOW_FILE_MODS = TRUE; See the Codex for background information: Setting this constant also disables the Plugin and Theme editor (i.e. you don’t need to set DISALLOW_FILE_MODS and DISALLOW_FILE_EDIT, as on its own DISALLOW_FILE_MODS will have the same effect). It will also prevent installing or uninstalling … Read more
You can Disable HTTP Calls by adding this in your wp-config.php define( ‘WP_HTTP_BLOCK_EXTERNAL’, TRUE ); This will disable/block all external HTTP requests and will make website alot faster. And then you can whitelist domains that you don’t want to block. define( ‘WP_ACCESSIBLE_HOSTS’, ‘example.com, domain.com’ );