|
Midsouth Fly Fishers
|
December 21, 2015 at 7:30 am
Hello,
I am experiencing issues with my Add New Event page. When I go in to add a new event, the Text for description is white on a white background, there are no editing buttons, the calendar selectors for date and time do not work. A screenshot of how the page renders is here.
https://www.dropbox.com/s/5zjucmptidk4is6/2015-12-20%2016_33_05-EE-Wordpress.png?dl=0
If I enter the data in the description and set the date/time manually, the event posts just fine.
I have tested compatibility with my theme and the page renders fine on my test server with my theme and all the plugins I am using, so I dont think this is a compatibility issue with my Theme or anything like that, rather more of an issue with my server. I first noticed the issue after having my site moved to a new server by my ISP, to update my PHP Version to a version recommended by EE. The big difference in the servers, is the new server uses a NGINX and apache while the old one just used Apache. I am not sure if this issue may be related to cacheing done by NGINX or something like that. Here are my stats
WordPress Version:
4.4
PHP Version:
5.4.45
MySQL Version:
5.5.44
Event Espresso Version:
4.8.27.p
WordPress Address (URL):
http://www.msff.org
Site address (URL):
http://www.msff.org
Thanks for any help you can give.
|
|
Josh
|
December 21, 2015 at 9:30 am
Hi there,
The issue you report here is generally caused by a JavaScript error on the page that loads up the event editor. Can you check for a JavaScript error using the Web Inspector (Chrome) or Firebug (Firefox)?
Since your troubleshooting so far has indicated a server issue, it may help to disable WordPress’s script concatenation feature. You can disable this by adding the following to your wp-config.php file:
define( 'CONCATENATE_SCRIPTS', false );
|
|
Midsouth Fly Fishers
|
December 22, 2015 at 10:20 am
Thanks. I looked at the page with Firebug and did not see any out and out JavaScript failures. I looked at what was being loaded and saw mostly 200 response codes, 301 and 304 responses. The console in firebug did not show any errors on page load. I am not a developer/programmer so there may be things I am missing here. Is there anything else that I can try to get to the bottom of this?
|
|
Josh
|
December 22, 2015 at 10:31 am
Did you try disabling the script concatenation?
|
|
Midsouth Fly Fishers
|
December 22, 2015 at 10:36 pm
Sorry, forgot to mention that. I did make the edits to the wp-config.php file. Results reported in previous post inclusive of concatenate scripts changes in file… no visable errors in JScript and 200/301/304 returns on all calls in firebug as best as I can tell.
|
|
Midsouth Fly Fishers
|
December 23, 2015 at 8:35 am
One potential note that I have found, I deactivated and activated the plugin, when activating it, I noticed in the dev tools that I get a 500 internal server error on activation of Event Espresso. As a test, I deactivated and reactivated a few other plugins and they did not produce the 500 internal server error, just the Event Espresso plugin. I deactivated and deleted the plugin, then redownloaded the plugin from the site, and added it back to wordpress with the same 500 internal server error on activation in the Dev tools
GET http://www.msff.org/wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s= 500 (Internal Server Error)
I do not see an error in the browser, and when I refresh the browser, it shows event espresso as activated. I am thinking the plugin is not getting fully installed for some reason or another.
|
|
Lorenzo Orlando Caum
|
December 23, 2015 at 8:54 am
Hi, are you manually uploading Event Espresso via SFTP / FTP or are you installing through the WP dashboard?
—
Lorenzo
|
|
Midsouth Fly Fishers
|
December 23, 2015 at 9:30 am
Downloading the Zip File from the website and installing via WP Dashboard.
Have more information. Problem seems to be caused by a conflict with the following plugin.
Booster for WooCommerce aka wooCommerce Jetpack.
Followed the following steps
EE giving 500 error on activation, turned on wp debugging to troubleshoot
Debugging gave the following error on EE activation
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 97 bytes) in <sniped path>/wp-includes/class-wp-user.php on line 491
added php_value memory_limit 128M to htaccess file and increased memory limit in wp-config.php files… no change
disabled all other plugins and activated EE first, EE activeated, NOTE: EE gave this notice which I am not sure if it is relevant.
An error has occurred:
WordPress database error: [Duplicate key name ‘first_model’]
ALTER TABLE wp_esp_extra_join ADD KEY first_model (EXJ_first_model_name, EXJ_first_model_id)
WordPress database error: [Duplicate key name ‘second_model’]
ALTER TABLE wp_esp_extra_join ADD KEY second_model (EXJ_second_model_name, EXJ_second_model_id)
New event page worked as expected.
Activated plugins one by one
problem returned when activated woocommerece booster plugin.
Experimented with a combination of plugins on and off to eliminate memory issues.
It seemed consistent that the woocommerce booster plugin immediately caused the issue, and deactivating it resolved the issue.
Is there any analysis that can be done to see why these two plugins are not compatble? I actually moved to woocommerce because of compatibility issues with WP-Ecommerce, and i use this booster pack for email alerts and notifications.
|
|
Josh
|
December 23, 2015 at 10:09 am
The out of memory error you’re seeing is a good indication that this is not a compatibility issue. It’s a server running low on memory issue. The different results you’re seeing on the two different servers also indicates this.
The next to troubleshoot this is ensure that you get the memory limt bumped up on the server where you’re having trouble.
added php_value memory_limit 128M to htaccess file
If this is an nginx server, you’re setting the php memory limit in the wrong file. Can you check php.ini?
and increased memory limit in wp-config.php files… no change
Where you place the memory limit constant within the file is important, please see:
http://serverfault.com/questions/543989/having-trouble-increasing-wordpress-memory-limit-on-nginx-server
|
|
Midsouth Fly Fishers
|
December 23, 2015 at 8:42 pm
I do not have direct access to the php.ini file for my host provider, so I am working with them to get that bumped. Hopefully that will abate the activation issues that I am seeing.
I still would like to pursue the interaction with the additional plugin, as then that one is disabled, EE returns to normal function. All other plugins can be disabled with no change in behavior, so I am wondering if the memory issue and the new event behavior are unrelated.
Regardless, will pursue the memory expansion if for no other reason than to have the memory room to function. Will post more when able. Will be out of pocket for a bit for the holidays.
Thanks for all the help so far.
|
|
Josh
|
December 24, 2015 at 8:39 am
The other thing you can keep in mind was this was all working before your site was moved to a new server, right?
|
|
Midsouth Fly Fishers
|
December 24, 2015 at 9:07 am
As far as I tested it was all working just fine on the old server. And that data vs the woo plugin behavior seem to be at odds. I am trying to determine if the woocommerce plugins got updated or if there was a version change on old server vs new server, which I may not be accounting for or did not notice. Anyway, just trying to follow the data at this point and I have a memory issue for sure, which I will pursue with my host provider, then I will continue to evaluate if the problems persist. It will take a few days to get that resolved however.
Hope you guys have a great holiday.
|
|
Josh
|
December 24, 2015 at 11:45 am
The data doesn’t necessarily mean it’s at odds. When two plugins both require more than the average amount of memory, it can look like there’s a plugin conflict, but when the first error you see on a plugin activation is a ‘Fatal error: Allowed memory size of xx bytes exhausted’, that’s a good indication that it’s a memory issue.
|
|
Midsouth Fly Fishers
|
December 24, 2015 at 12:03 pm
You nailed it Josh. That’s exactly what it was. I heard back from my host provider and they bumped the memory up to 256M in the PHP.INI file. Once done I was able to activate and deactivate the EE plugin without any issues or 500 errors, and the new event page rendered and functioned properly, with all other plugins active. Thanks again for all of your help and feedback. Hope you guys have a great holiday season.
|
