Divi WordPress Theme
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WordPress fix Reply To: Core update to 4.9.2 might break VCS

Discussion in 'Misc WordPress Requests' started by RossMitchell, Jan 29, 2018.

  1. RossMitchell


    Reply To: Core update to 4.9.2 might break VCS, by RossMitchell

    It is the usual thing for a WordPress website to exist as a set of files on the web server with both file/directory owner and permissions to permit the website code to update its own files, this is how the automated updates get rolled out, on occasions when the website code gets run, it checks at wordpress.org to see if an update has been issued, if it has then it downloads and installs the files. It is similar when an author uploads pictures and media, the website code saves the images into directories on the webserver.

    I also understand that you use GIT, what is not clear is if you use GIT procedures to track and archive the website files, OR if you expect to use GIT to update the website files from a GIT managed WordPress archive. Which is it ? Clearly it is a bad idea to have two competing file update mechanisms, it is bound to end in inconsistencies, also an essential phase of an update is to update the database structure, the GIT mechanism would have to activate this code.

    You could deactivate the WordPress update mechanism and delegate website file updates to GIT, and also activate the database structure updates.

    You could also use GIT to periodically snapshot your website files as an archive, to make this a proper website backup you also must backup the database tables.

    Hope this clarifies the situation.

    Reply To: Core update to 4.9.2 might break VCS

Share This Page

Monarch Social Sharing Plugin