I have all my client sites on their own repos for tracking changes with svn but when I update through the Wordpress admin panel (Wordpress or plugins) the directories for them are deleted and replaced, removing the .svn files.
This then breaks my svn as I keep getting the following,
Commit failed (details follow):
Directory '/website/trunk/wp-content/plugins/plugin-dir/.svn' containing working copy admin area is missing
Does anyone know a way to auto-update through the Wordpress CMS with it deleting any svn files?
This page has a procedure of setting up the process properly:
https://wordpress.stackexchange.com/questions/23052/updating-a-wordpress-plugins-breaks-svn
Related
Overview
I can't update my WordPress from the admin panel=>Update (the admin panel is locked in the middle).
WordPress itself is trying to update to "WordPress 5.9".
What I tried
Stop all plugins and update WordPress.
Set the permissions of "upgrade" and "plugins" directories under the WordPress directory and wp-content to 777 or 704, and stop all plugins.
To enable debug.log, I added the following to wp-config.php and tried to update, but no debug.log appears under wp-content.
Added statement=>define('WP_DEBUG_LOG', true);
Update with browser cache cleared
Checked PHP execution time in wp-config.php=>set_time_limit(600) and it was specified as 10 minutes, so it seems to be fine.
What I want to ask you
Even if I do all of the above things in parallel, I can't update WordPress (the process stops in the middle).
Can you tell me if there is any other reason why WordPress can't be updated? Thank you for your time.
I would just do a manual update at that point.
Download the current/or version you need and once you’ve downloaded it, extract the zip file to your computer. Then, open the folder that contains all of the WordPress files and delete the following items:
The wp-config-sample.php file.
The wp-config.php file (you might not see this file – just make sure to delete it if it’s there). The wp-content folder.
Once you’ve deleted those items, upload the remaining files/folders to your server via FTP. When prompted about duplicate files by your FTP client, tell it to overwrite all files:
Hello i am not getting the Update Now button at wordpress admin.
My current worpdress version is 4.8.3
so how can i solve upgrade my wordpress 4.8.3 to latest version 4.9
you can do one thing in wordpress folder i.e. you can do all plugins deactivated after you refresh the dashboard page from backend admin side then you can get the Update Button.
Otherwise you can upgrade the version by manually,
Follow the steps,
Upgrading WordPress Core Manually
First create a full backup of your website. This is very important
in case you make a mistake.
Download the newest WordPress ZIP file from wordpress.org.
Unzip the file into a directory on your local machine or in a separate directory on your website.
Deactivate all of the plugins on your WordPress site.
Go to your website root directory and delete your ‘wp-includes’ and ‘wp-admin’ directories. You can do this via sFTP or via SSH.
Upload (or copy over) the new wp-includes and wp-admin directories from the new version of WordPress you unzipped to your website root directory to replace the directories you just deleted.
Don’t delete your wp-content directory or any of the files in that directory. Copy over the files from the wp-content directory in the new version of WordPress to your existing wp-content directory. You will overwrite any existing files with the same name. All of your other files in wp-content will remain in place.
Copy all files from the root (‘/’) directory of the new version of WordPress that you unzipped into your website root directory (or the root directory of your WordPress installation). You will overwrite any existing files and new files will also be copied across. Your wp-config.php file will not be affected because WordPress is never distributed with a wp-config.php file.
Examine the wp-config-sample.php which is distributed with WordPress to see if any new settings have been added that you may want to use or modify.
If you are upgrading manually after a failed auto-update, remove the .maintenance file from your WordPress root directory. This will remove the ‘failed update’ message from your site.
Visit your main WordPress admin page at /wp-admin/ where you may be asked to sign-in again. You may also have to upgrade your database and will be prompted if this is needed. If you can’t sign-in, try clearing your cookies.
Re-enable your plugins which you disabled earlier.
Clear your browser cache to ensure you can see all changes. If you are using a front-end cache like ‘varnish’ you should also clear that to ensure that your customers can see the newest changes on your site.
Your upgrade is now complete and you should be running the newest version of WordPress.
Hopefully, you get the solution.
Me and my friend started developing a web site using a WordPress theme. I uploaded the source code on git hub and started doing changes on the website using the admin dashboard. But whenever git status command is entered in the bash, It says working directory is clean and no changes. Any idea why this is happening?
git tracks changes of the source code (or, generally, any files) which lie in the folder where the repository is located. But when you change something in WordPress or other CMS, these changes are typically recorded into database, not filesystem. Only files uploaded by users typically go to the file system, but not configuration settings (like titles and posts).
We're using Subversion to keep track of the changes our web team makes to our Wordpress site. We do nothing more than modify and update our custom theme, but we have difficulty updating the Wordpress core and plugins.
Right now, I have my checked out copy working on a local WordPress install. However, when I run the automatic WordPress updates on this local copy, the updates overwrite the .svn folders in the respective subfolders, resulting in a "Directory .svn containing working copy admin area is missing" error when I try to commit the update.
How can I do these updates automatically without overwriting the .svn folder? As of now I am resorting to copying the files in manually.
If you're just maintaining your theme, you should not have the whole wordpess install under svn but just the theme. I also think in your case it doesn't make sense to actually use a working copy of your repository in the actual live site. In your case I'd keep a working copy of your theme somewhere on your server and then rsync on demand to your theme folder. This way you can update wordpress and your plugins automatically and without problems.
I am currently developing a site based on WordPress (3.3) and am having an issue keeping it up to date properly in subversion (my personal svn server), wondering if I could get any help/guidance on how to handle this. I have a working copy checked out, and everything is working fine, accept for when I update a plugin and/or WordPress itself...here's an example for the Woocommerce plugin (hopefully I explain this well enough):
Woocommerce notifies me of update
I update the plugin using the WordPress dashboard
WordPress deletes all files in the wp-content/upgrade directory, and the plugins/woocommerce directory (including the .svn folders).
I then try and either do an svn add and/or svn commit and get errors about the upgrade and woocommerce directory's 'working copy admin area missing' plus a whole bunch of other problems.
I want to be able to keep this WordPress site in subversion and keep the plugins directory updated, so that I can eventually do an export when I'm ready to move the site to my server, but this is proving to be exceptionally difficult (I can re-checkout and replace the .svn directories for each of the WordPress folders that are missing them, but there are a lot of folders, and is very tedious. I can ignore the upgrade and plugin folders, but then they don't get updated and my export won't go as planned...what should I do?
One thing that will help a lot is to upgrade your client to Subversion 1.7. Instead of a .svn folder in each folder, it has a single .svn folder in the root of the working copy and will keep better track of things.
After you upgrade your client, do svn upgrade at the root of your working copy. Note that this is irreversible and incompatible with older versions of SVN.
The SVN server does not have to be upgraded for this, only the client.