|
Mansi Hans
|
February 3, 2015 at 7:29 pm
The basis to upgrade was brought upon from another issue, but as a result of the upgrade to 4.6.0.p the entire function of WordPress becomes unresponsive. So I logged into the database for the site and removed all of the active plugins un the wp_options table to allow access back into the website.
|
|
Mansi Hans
|
February 3, 2015 at 7:32 pm
I’ve deleted 4.6.0.p and I’m putting version 4.4.10.p back onto the site to at least get the site functioning again. I will post the related post regarding the original issue in a later.
|
|
Mansi Hans
|
February 3, 2015 at 7:40 pm
Also a note to this upgrade…
With the upgrade the theme settings for font types and css become inaccessible. This prevents the page layout and designs from appearing correctly.
|
|
Tony
|
February 4, 2015 at 3:41 am
Hi Mansi Hans,
When you tried to log into the Dashboard did you just see a whitescreen?
If so that means a fatal error was being thrown, we’ll need this error to investigate further. Can you check your server error logs and see if the error is there?
|
|
Mansi Hans
|
February 4, 2015 at 2:31 pm
Yes, there was only a white screen and nothing appeared anywhere to try and access any portion of the website. By removing the active plugins (which was only the 4.6.0.p version on one attempt), I was able to gain access back into the Administrative portion of the site.
I checked with the hosting company today and there were no error logs to be viewed.
|
|
Sidney Harrell
|
February 4, 2015 at 2:54 pm
If you set WP_DEBUG to true in the wp-config.php file, it should dump the error message straight to the screen. There’s a little bit fancier method that will dump it to a wp error log file in wp-content, but putting it to the screen should work fine for your purposes.
|
|
Lorenzo Orlando Caum
|
February 4, 2015 at 3:25 pm
Hi there Mansi, another member reported a similar issue and we are trying to get more information on what happened.
Could you temporarily turn on WP debugging and give the upgrade another try?
https://gist.github.com/lorenzocaum/848801a1173be464fbe7
As Sidney shared, you should see some kind of messaging on the screen. Please copy and paste that information here.
Thanks again.
—
Lorenzo
|
|
Mansi Hans
|
February 4, 2015 at 9:58 pm
Unfortunately, because our busiest time of the week is Thursday thru Sunday, I won’t be able to attempt the upgrade or even the debug setting until Monday.
|
|
Tony
|
February 5, 2015 at 7:04 am
Hi Mansi,
That’s fine, we are still investigating the cause currently.
Can you also let us know which version of WordPress is the site running please?
|
|
Mansi Hans
|
February 5, 2015 at 11:56 am
Wordpress 4.1
|
|
Lorenzo Orlando Caum
|
February 5, 2015 at 5:59 pm
Hi Mansi, we have released updates that fix a handful of issues for Event Espresso 4.6.x.
https://eventespresso.com/topic/read-this-support-post-event-espresso-4-6-x/#post-138772
Please try the update next week after your busy period.
Thanks
—
Lorenzo
|
|
Mansi Hans
|
February 9, 2015 at 7:21 am
I just applied the 4.6.4.p update to the site and the entire site went blank on what was being displayed. According to my Tier 2 support, there is a PHP warning that is causing a Fatal Error is trying to open file core/libraries/payment_methods/eei_payments_method_interfaces.php.
The permissions on this file (and others in this folder) are not set correctly. I changed them all to 755 and the site launches again without the error.
Here is a screen shot showing the result that Event Espresso is in Maintenance Mode.
|
|
Mansi Hans
|
February 9, 2015 at 7:24 am
Well the screen shot could not be attached. So here is a link to see the screen.
http://colorfulaffair.com/wp-content/uploads/2015/02/Event-Espresso-Error-2-9-15.png
|
|
Mansi Hans
|
February 9, 2015 at 7:31 am
Now that I have access to the WP Admin side of the site, I have backed up the DB and performed the upgrade to the DB per the maintenance mode instructions. Now I have, Congratulations! Your database is “up-to-date” and you are ready to begin using EE4.6.4.p.
Now however, when I go to access the Calendar on the actual site there is this error.
http://colorfulaffair.com/wp-content/uploads/2015/02/Event-Espresso-Error-2-9-15-Calendar.png
|
|
Mansi Hans
|
February 9, 2015 at 7:34 am
When I go to verify the Payment methods, there are four (4) of them that are currently active when there should only be one. I attempt to set the PayPal Standard Settings and I get this…
An error has occurred:
Payment method of type Paypal Standard was not saved because there were validation errors. They have been marked in the form
Payments_Admin_Page – _update_payment_method – 767
|
|
Mansi Hans
|
February 9, 2015 at 7:37 am
The other three methods of payment that were active were Bank Draft, Check, and Invoice. None of which should have been active for our payment options.
I deactivated these three and try to confirm the settings for PayPal Standard and I still get this error message.
An error has occurred:
Payment method of type Paypal Standard was not saved because there were validation errors. They have been marked in the form
Payments_Admin_Page – _update_payment_method – 767
|
|
Mansi Hans
|
February 9, 2015 at 7:50 am
I determined that with the upgrade to 4.6.4.p, for some reason the Calendar Addon was deactivated. So I activated it and now I received the following message from the activation process.
Payment Method ‘Bank Draft’ had a broken button url, so it was reset
Payment Method ‘Check’ had a broken button url, so it was reset
Payment Method ‘Invoice’ had a broken button url, so it was reset
Payment Method ‘Authorize.net AIM’ had a broken button url, so it was reset
Payment Method ‘Mijireh’ had a broken button url, so it was reset
Payment Method ‘PayPal Pro’ had a broken button url, so it was reset
Payment Method ‘PayPal Standard’ had a broken button url, so it was reset
|
|
Mansi Hans
|
February 9, 2015 at 7:57 am
Now that the Calendar function is working on the site, I accessed one of the events and was able to get all the way to the PayPal payment screen.
Things of note…
- Calendar Events took a while to appear on screen.
- There was a delay in actually reaching the Payment Screens.
- Connection to the PayPal Gateway took about 5 seconds to appear.
- Cancelled Registration page has no content available to be shown (Is it possible to edit this to show either the Calendar or have a custom message that the site visitor can order again from?)
|
|
Sidney Harrell
|
February 9, 2015 at 8:07 am
Are you continuing to receive those error messages, or was it just the one time on activation?
The files in core/libraries/payment_methods should be 664, and all folders should be 775. That’s pretty standard for WP http://codex.wordpress.org/Changing_File_Permissions#Permission_Scheme_for_WordPress What were they before you changed them to 755?
|
|
Mansi Hans
|
February 9, 2015 at 10:43 am
The file permissions were set to 644 not 664.
|
|
Sidney Harrell
|
February 13, 2015 at 9:57 am
That is really odd. They should be 664 in the zip that gets downloaded behind the scenes when you update. Normally, if the web server is running as the file owner, it wouldn’t matter, but some administrators run the web server as www-data and use the group.
We did just launch a hosting platform for EE, EventSmart, where we take care of the environment for you. That may be a better long term solution in your case.
Are things working smoothly now?
|
