|
durhamrec
|
February 3, 2017 at 5:13 pm
This is a site we inherited so I don’t have a lot of history. The client was able to create new events just fine until about a week ago. We debugged and found the following: Session save path does not exist – contact your host to resolve the problem.
We had the host set the session save path to what the plugin was now looking for and it still will not allow new events to be created.
It seems they also have 12 additional event espresso plugins installed.
|
|
Lorenzo Orlando Caum
|
February 5, 2017 at 12:53 pm
Hello,
Thanks for letting us know what you have tried.
What happens if you temporarily deactivate other plugins and try to create a new event?
Do you see an error? If so, could you share that error here in a reply?
—
Lorenzo
|
|
durhamrec
|
February 5, 2017 at 1:35 pm
Are you referring to the other event espresso plugins or all in general?
|
|
Josh
|
February 6, 2017 at 8:01 am
All in general. Can you check with your host to make sure they’ve verified that the session save path can be written to?
|
|
durhamrec
|
February 6, 2017 at 11:31 am
The host has confirmed that the directory is writable. We’ll start to disable plugins.
|
|
durhamrec
|
February 7, 2017 at 11:10 am
Status: Problem still not resolved.
We are suspecting the SSL may not be configured correctly but thats a guess.. Steps we took are below.
Troubleshooting steps completed:
1. Updated plugins, disabling all plugins, enabling only Event Espresso. Problem persists with only EE core active.
2. Updated Site address and WordPress Address in wp options to current URL: https://durhamrec.com
3. Used Velvet blues to update any lingering http:// or www. formatted urls to current.
4. Switched to default theme (Twenty Seventeen), problem persists.
All plugins and custom theme are now re-activated.
Detailed description of the problem:
wp-admin section works fine until visiting Event Overview or Venue Manager pages. After visiting these pages clicking on “New Event” or any other page in the admin backend results in display of Page Not found (404) front end template. Attempting to visit /wp-admin then results in a “Too Many Redirects” error until all site cookies are cleared.
|
|
Josh
|
February 7, 2017 at 11:23 am
Have you checked the .htaccess file for any extra things other than the normal WordPress rewrite rules?
|
|
durhamrec
|
February 7, 2017 at 1:42 pm
Nothing truly odd. We looked at that first when we suspected malware, and found none. There is an odd wrapper on the rewwrite rules..
# BEGIN s2Member GZIP exclusions
<IfModule rewrite_module>
RewriteEngine On
RewriteBase /
RewriteCond %{QUERY_STRING} (^|\?|&)s2member_file_download\=.+ [OR]
RewriteCond %{QUERY_STRING} (^|\?|&)no-gzip\=1
RewriteRule .* – [E=no-gzip:1]
</IfModule>
# END s2Member GZIP exclusions
|
|
durhamrec
|
February 7, 2017 at 1:44 pm
Sorry.. the above appears BEFORE the WP rewrite.. but assuming that has been there for a long time. Below is the entire file contents
# BEGIN s2Member GZIP exclusions
<IfModule rewrite_module>
RewriteEngine On
RewriteBase /
RewriteCond %{QUERY_STRING} (^|\?|&)s2member_file_download\=.+ [OR]
RewriteCond %{QUERY_STRING} (^|\?|&)no-gzip\=1
RewriteRule .* – [E=no-gzip:1]
</IfModule>
# END s2Member GZIP exclusions
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
# ea4 php_value post_max_size 30M
# ea4 php_value upload_max_filesize 30M
|
|
durhamrec
|
February 7, 2017 at 1:45 pm
Also could you add my e mail to this ticket? The client is getting the e mails but we are doing the troubleshooting.. jmberry@jmberry.com
|
|
Josh
|
February 7, 2017 at 2:31 pm
Sorry I can’t add your email because the forum notifications go to the email address for your account. If you can switch the email address in your account settings the emails you’ll get the emails.
Since you suspect something got misconfigured while switching the site to SSL, it may help to follow this guide:
http://www.wpbeginner.com/wp-tutorials/how-to-fix-error-too-many-redirects-issue-in-wordpress/
|
|
durhamrec
|
February 7, 2017 at 3:13 pm
We didn’t switch anything to SSL. We just thought that might be a suspect. Everything works except the EE product. Let me find out if the host recently installed SSL. IWe just inherited this site a couple weeks ago.
|
|
Josh
|
February 7, 2017 at 6:01 pm
I think what you’re seeing with EE is a symptom of a larger problem with the way the server is configured. If you can try following the guide I linked to in my last reply that may help.
|
|
durhamrec
|
February 7, 2017 at 11:30 pm
That would bode well if the server configuration had actually changed, but this worked fine for a year till 3 weeks ago. Let me confirm with the host that nothing has changed.
|
|
Tony
|
February 8, 2017 at 4:17 am
Hi there,
So in that case 3 weeks ago something changed, be it an update to a plugin, theme, host config or something which may seem completely unrelated but something has changed and we need to figure out what that was.
You mentioned this:
2. Updated Site address and WordPress Address in wp options to current URL: https://durhamrec.com
3. Used Velvet blues to update any lingering http:// or www. formatted urls to current.
So the domain changed or is this just a change from http to https? This question also applies for 3 weeks ago, was something with the domain changed then?
If you open up Chrome Dev tools, make sure its on the network tab and click to create a new event, wait for the 404, now visit /wp-admin/ and watch the dev tools you should see the redirect happening in the network tab, where is it directing you to?
|
|
durhamrec
|
February 8, 2017 at 12:18 pm
Hi. Thanks for your patience and support. Seems there was a server migration 4 weeks ago and a security option was deployed. See below, We couild not see the error in any cpanel logs and did not have access to the Apache logs. The change seemed to fix the issue. Waiting for the client to confirm then we can close this ticket. Thanks for the support.
The mod security option appears to be disabled for your account long back and there was a server upgrade a month back. Mod security will be enabled by default for all sites and will be disabled only when applications are being blocked by it.
|
|
Josh
|
February 8, 2017 at 12:27 pm
They may be able to find which rule was triggered and make an adjustment to the mod_security settings, then mod_security could still be enabled. Sometimes folks will jump to the conclusion that you can’t use Event Espresso on a server that has mod_security enabled, but that’s not the case.
You can use Event Espresso on a server that has mod_security enabled, but if there’s a specific rule that’s getting triggered, that one specific rule can be deactivated.
|
|
durhamrec
|
February 8, 2017 at 12:32 pm
Thanks.. I’ll let them know..
|
