Core update to 4.9.2 might break VCS

  • Hi there.
    Our team uses GIT. Already twice we encountered the same problem after WordPress core update to 4.9.2 version via GIT: it appeared that WordPress changed some files in wp-admin folder (e.g. /wp-admin/widgets.php) and it breaks our GIT.
    We have not encountered such problems before, so could you please confirm if WordPress really can change files in its core. If so, apparently, to have core under git would be not a good idea or, probably you would give a piece of advice what to specify in gitignore.
    Also I didn’t understand from https://codex.www.ads-software.com/Changing_File_Permissions if WordPress can change file permissions.
    Thanks in advance.
    Alex

Viewing 3 replies - 1 through 3 (of 3 total)

  • We have not encountered such problems before, so could you please confirm if WordPress really can change files in its core.

    I’m not sure I understand. Of course it can. What do you think an update does? Are you saying that files changes _after_ the update, or as part of the update?

    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 www.ads-software.com 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.

    Thread Starter avtop

    (@avtop)

    Sorry for my request, I understand now it was not clear. Forget about GIT, the point is:
    Imagine you are going to update WP core. You uploaded (via FTP for example) new core release (without wp-content folder) to the server. From that point and until the next core update can WP by itself or some plugin in any circumstances change files in wp-admin or wp-includes folders? Or they (wp-admin and wp-includes folders and their content) stay the same until next core update?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Core update to 4.9.2 might break VCS’ is closed to new replies.