Tag Info

New answers tagged

1

Edit line 149 in file.php as described in this thread: https://wordpress.org/support/topic/unable-to-update-plugins-after-upgrade-to-42 fixed it for me (on a linux host). edit: just read you are on windows: someone also posted a fix that applies to windows hosts there (apparently more complicated because backslashes are used in filepaths). so your line ...


0

Brandoo WordPress was abandoned. I've now moved to Nami WordPress which is similar. It also works with SQL Server and is more actively developed.


1

Brandoo isn't (sadly) hosted by Azure at the moment. This plugin is written to be used by version 3.6. Newer versions make use of queries which will not work on SQL Server. That's why you get those errors. So, you need to keep your version of wordpress at all costs till a newer version of brandoo is released: ...


0

I got the same problem, site wasn't loading with Chrome after the update (I guess Firefox/Safari handles this somehow differently), because of those https asset links. Are you using WooCommerce by any chance? After updating that I got my site running again, here is a part of their changelog: Fix - Fixed Google Chrome forcing to use SSL. This can cause some ...


0

I finally got it by changing the db value in wp_options table and it works like a charm


0

If you get that Database update message, looks like WordPress may have updated. Probably you want to turn automatic updates off. Simply do: 1 - Restore your db where it works ok 2 - Add this to your wp-config.php: define( 'AUTOMATIC_UPDATER_DISABLED', true ); 3 - Enjoy!


3

The short answer is yes. Wordpress does go into maintenance mode when updates are are installed. You have nothing to worry about. This is default behavior. I do know that there are sometimes issues where Wordpress gets stuck in maintenance mode after updates, but if you don't experence such issues, you are good to go :-)


1

You setup a Wordpress site in a subdirectory/subdomain or any url of your choice. So, the path structure is up to you. Add all the files and database info in this site. Activate the same plugins and themes. Disable search engine indexing for this site. Set up so that published posts and everything else on the live site are added automatically in this site ...


2

In this case i will do: create a new folder inside website root folder (ex: mynewsite) create a new db and import the old website db to it copy old website files and folders to the new directory (mynewsite) change db name, user etc in wp-config on mynewsite folder define site url by adding to wp-config.php ...


0

Figured it out. Apparently WordPress is a bit dumb, and even if your files are owned by user abc and group www-data (abc:www-data) and are all group-writable, WordPress still won't do the easy update method unless the files are actually owned by www-data:www-data. It doesn't even bother checking the group permissions.


1

Every 12+ Hours WordPress automatically goes out and checks if a plugin needs to be updated via the WordPress Repository. There's 3 cron jobs that WordPress runs to check on things: wp_version_check - Checks for Core Updates wp_update_plugins - Check for Plugin Updates wp_update_themes - Checks for Theme Updates A neat little plugin to view these is WP ...


0

You're right in that this does not have to do with permissions. You will run into it depending on a particular server configuration. To ensure that you don't have to deal with it on an ongoing basis, you will want to add the FTP credentials to wp-config.php like so: define( 'FTP_USER', 'username' ); define( 'FTP_PASS', 'password' ); define( 'FTP_HOST', ...



Top 50 recent answers are included