#48306 closed defect (bug) (invalid)
Fatal after WordPress update
| Reported by: |  | Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | 5.2.3 | 
| Component: | Upgrade/Install | Keywords: | close | 
| Focuses: | Cc: | ||
| PR Number: | 
Description
Hi there,  
I have tried to update WordPress in a local installation and I got a PHP error in admin area, the frontend works fine. 
PHP Parse error: syntax error, unexpected ')', expecting end of file in /srv/www/wordpress-one/public_html/wp-includes/class-wp.php on line 753 PHP Parse error: syntax error, unexpected ',' in /srv/www/wordpress-one/public_html/wp-includes/class-wp-query.php on line 4360 PHP Parse error: syntax error, unexpected '->editor_sc' in /srv/www/wordpress-one/public_html/wp-includes/script-loader.php on line 2755
I have the same issue in 3 files:
class-wp.php | class-wp-query.php | script-loader.php.
To solve this issue you simply open each file, remove the last line and save it, nothing else. After that the problem disappear. 
My local environment running vvv 3.1.1. I try to update WordPress via WP-CLI and via WordPress Dashboard and the problem persist. 
Windows/Unix, no difference -> same issue.
I have tested it several time, same issue. 
Thanks for your time. 
Change History (7)
    
      
    #2
  
          follow-up:
    ↓ 7
    
        
          
             @
 @
            
2 weeks ago
        
    
  
  
    
Hi there! 
Sure, works fine after vagrant_reload
Thanks for suggestion. 
Do you know the reason of that ? 
    
      
    #3
  
          follow-up:
    ↓ 5
    
        
          
             @
 @
            
2 weeks ago
        
    
  
  
  - Keywords close added; needs-testing removed
Hi @agengineering 
Glad to know it solves your problem. I do not know the reason.
:)
    
      
    #5
  
        in reply to:
    ↑ 3
    
        
          
             @
 @
            
2 weeks ago
        
    
  
  
    
Replying to dkarfa:
Hi @agengineering
Glad to know it solves your problem. I do not know the reason.
:)
Thanks to you :)
    
      
    #7
  
        in reply to:
    ↑ 2
    
        
          
             @
 @
            
2 weeks ago
        
    
  
  
    
Replying to agengineering:
Do you know the reason of that ?
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/1819 has some context. Per the latest comment:
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.


 
                       
			     
			 
                
Hey @agengineering,
Can you try to reload VVV using
vagrant reloadThanks,