VVV: 5.2.1 update breaks WordPress installations

Expected Behavior

Minor update shouldn’t break anything

Current Behavior

When I update the WP from 5.2 to 5.2.1 (I tried downgrading but that didn’t help) I am getting

Parse error: syntax error, unexpected ‘}’, expecting end of file in /srv/www/personal/wordpress-test/public_html/wp-includes/general-template.php on line 4569

I started digging and the issue happens in feed.php on line where $feed->init() is (770).

So my guess is something with new vvv version and SimplePie() is clashing maybe?

I deleted my db in order to run a clean install, but no go.

Steps to Reproduce (for bugs)

  1. Have VVV3
  2. Try to update WP to 5.2.1 version
  3. Panic because you need to test the code for production
  4. Set up temporary docker to see if it will work until this issue is solved ¯_(ツ)_/¯

Your Environment

  • VVV version: 3
  • VVV Git Branch: develop
  • Vagrant version: Vagrant 2.2.4
  • VM Provider name: VirtualBox
  • VM Provider version: Version 6.0.4 r128413 (Qt5.6.3)
  • Operating System and version: MacOS 10.14.4

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 3
  • Comments: 26 (12 by maintainers)

Most upvoted comments

If I vagrant ssh into the guest VM, and flush the page cache, all syntax issues disappear:

vagrant@vvv:~$ sudo su
root@vvv:/home/vagrant# echo 1 > /proc/sys/vm/drop_caches

This issue is due to a kernel bug in a box we used to use. The latest version uses a newer box that doesn’t have this issue.

Back up your database, update VVV, destroy and recreate the VM.

On Wed, 7 Aug 2019 at 16:54, Victor Lava notifications@github.com wrote:

I doubt that’s the case, my personal site runs on Digital Ocean and has near identical specs to VVV yet doesn’t encounter this issue. I did see this issue myself during testing but reprovisioning a fresh install fixed the problem. Looking at the files themselves didn’t reveal the issue as the missing characters were present when checked, resaving resolved the problem for that file

Do you encounter this error upgrading from any other WP install? Is there an associated WP Trac ticket? ( if not can you raise one? My suspicion is character encoding issues but I haven’t much to go off of )

Also have you tried WP CLI based updating?

I had a similar issue after updating to 5.2.2. However re-saving file helped to fix that. Very odd!

— You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1819?email_source=notifications&email_token=AAAOLZ54DUAIEADJYZDSZQTQDLVZ3A5CNFSM4HOVLDWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3Y3XOA#issuecomment-519158712, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAOLZ5ASTXB2RQDKQENLNLQDLVZ3ANCNFSM4HOVLDWA .