Tag Info

Hot answers tagged

11

Instead of using the code from the question in functions.php, replace it with this: /** * Prevent certain plugins from receiving automatic updates, and auto-update the rest. * * This function could easily be altered to do the opposite, by auto-updating specific * plugins and excluding the rest. * * Also, by using the 'auto_update_theme' or ...


6

I use XAMPP myself, but WAMP isn't much different. I'll bet you have not enabled the curl module. WordPress can use other methods (streams and fsockopen) as a fallback, but these may be disabled by default as well in a stock install. Curl is preferred and easy to enable. Close WAMP Go your the \bin\php\version directory in WAMP Edit the php.ini, and ...


4

The first argument is the plug-in's 'slug'. The plug-in slug is determined by the location of the .php file header containing the comment header necessary for plug-ins. (see source). If your main plug-in file might be ~/wp-content/plugins/foo/bar.php, while your plug-in slug is foo/bar.php. If the wp-content dir has a custom name, you can retrieve it using ...


4

Disable Plugin updates all together It should be as easy as that: <?php defined( 'ABSPATH' ) or exit; /* Plugin Name: (#120589) Disable Plugin Updates */ remove_action( 'load-update-core.php', 'wp_update_plugins' ); Deny (or reroute) Updates for Themes/Plugins Single core and theme updates can be deactivated by this script my Mark Jaquith: For ...


4

From my perspective there are about two issues with your plan - Git and "conventional" structure. So basically everything. :) Git (and version control in general) is poor tool for whole site stacks. Been there, done that, it hurt a lot. What you call "unconventional" structure with content separated from core has been for a while very conventional and ...


3

WP checks for updates by sending data about all plugins and themes to the repository. To prevent false update messages for your own code you need to selectively scrub it out of those requests. The example for theme by Mark Jaquith: function cws_hidden_theme_12345( $r, $url ) { if ( 0 !== strpos( $url, 'http://api.wordpress.org/themes/update-check' ) ) ...


3

There're a couple of libraries out there. One of the more well known is from Joey Kudish and hosted on GitHub itself. Basically it does the following: utilizes the GitHub API Adds a callback to the 'pre_set_site_transient_update_plugins' filter Adds another callback to the 'plugins_api' filter finally utilizes the WP HTTP API and does a wp_remote_get() ...


2

That might be a problem coming from your settings when you created your WordPress website. Are you using a cPanel and an application that automatically takes care of the WordPress installation for you? For example, I use 'Quickinstall' (you might be using the same application, or Fantastico or something in that sense). There's an option in the settings: ...


2

The setting you are looking for is found in "Settings"=>"General"=>"E-Mail Adress". All the Emails WordPress or Plugins send out are sent to the admin_mail, which is returned by get_option( 'admin_mail' ), and this Emailadress is not always connected to a user. If you first install WordPress, the first user created gets the role administrator, and the same ...


2

From development point of view the most practical way to detect and locate changes is version control - comparing against SVN/Git checkout of core or use such checkout directly. However there are also plugins around that verify files against set of hashes. I think Sucuri Security recently got such feature. The practical limitation of them is for which ...


1

If my guess is right that you think you add your site URL inside the plugin's head and it will magically update everyones plugin, then I have to tell you that wont work. You have choices: Either you host your plugin on wordpress.org and updates work pretty much without you doing anything then pushing your plugin to svn with the right stable tag in the ...


1

From quick look at the code upgrade motions are performed by wp_upgrade() function. I imagine calling it in some way would get it done, but postponing it until normal upgrade process is fixed is probably more efficient. In recent versions WP rarely does major changes to DB and it's reasonable expectation for it to not need database upgrade urgently after ...


1

There is this commercial Plugin and Theme Update API manager for WooCommerce that specifically works if the plugin or theme is not hosted on wordpress.org. It is designed to provide updates for self hosted plugins and themes. The plugin is for those who don’t want to write it yourself, and need a lot of features, plus working examples for plugins and themes ...


1

You need 2 basic things to accomplish this Hook into pre_set_site_transient_update_themes Use the HTTP API to query whatever url has your update The basic premise is your theme's version is stored in a transient that checks a remote URL every x hours and compares the $version. Notes: The URL can be anything, the HTTP API supports authentication ...


1

Saving this data persistently seems like excessive approach. Since there is no human input (only logic), there is no benefit to storing results - just keep the logic. More so if logic changes next week you won't need to re-save everything. Basically I would instead during output check is post has value and if not apply the one generated automatically. I ...


1

There is a bug in some versions of PHP itself, unzip hangs. PHP 5.2.17 hangs, PHP 5.3.24 works as expected. PHP Change Log http://www.php.net/ChangeLog-5.php#5.3.4 says PHP Version 5.3.4 released 09-Dec-2010 - "Fixed crash in zip extract method (possible CWE-170)". (Note: 5.3.24 released 11-April-2013, and is no longer the latest version.) ...


1

Well it looks like it's running ok from front end. I did get a notice saying that your Wordpress Database needed upgrading though. I'd suggest you visit: http://www.azraar.com/wp-admin and click that (after backing up your DB as previously suggested) as it might fix your problem. Good luck


1

Probably the update wasn't complete and some files are missing. If you have FTP access, follow these steps. Download you wp-config.php and save it somewhere. In the wp folder on server delete everything but the wp-content folder Have a DB backup, if you can Download from wordpress.org the zip of wordpress and extract it At this moment remove the ...


1

Best Practice #1 One of the best practices is to let the PHP process to run under a different user (in your case: jdoe, jsmith, etc) than the web server user (in your case: httpd) and let only these users have the write permission. Of course, your web server may still need read permission for all these files. For this solution to work, you may need to go ...



Only top voted, non community-wiki answers of a minimum length are eligible