This thread is resolved. Here is a description of the problem and solution.
Problem:
Get Error:
An error of type E_PARSE was caused in line 66 of the file /home/lloydcen/public_html/wp-content/plugins/wp-views/application/controllers/cache/meta/manager.php. Error message: syntax error, unexpected '::' (T_PAAMAYIM_NEKUDOTAYIM)
Solution:
This issue is fixed with Views release version 2.8.1.1.
Relevant Documentation:
This support ticket is created 5 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Plugin update to version 2.8.1 It crashed the site during the update. WordPress sent me an email (recovery mode) and the email said this:
Error Details
=============
An error of type E_PARSE was caused in line 66 of the file /home/lloydcen/public_html/wp-content/plugins/wp-views/application/controllers/cache/meta/manager.php. Error message: syntax error, unexpected '::' (T_PAAMAYIM_NEKUDOTAYIM)
=================
Hello. Thank you for contacting the Toolset support.
Well - I just updated the Toolset views plugin on my test install and it successfully updated without any issues.
I need to check on your site why its not working. Can you please share access details.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
Sorry, I was premature in closing the ticket. I thought I had successfully updated to the new 2.8.1, but I was wrong. The site crashed again.
I can't at this time provide you access to the live site. It's not something I'm comfortable doing. I'll wait to see if others are reporting this problem to you.
Well - just to notify you that we confirm the issue and this is set to be fixed with next Views release version 2.8.1.1 that is scheduled to release by tomorrow.
