|
girlsrockcampaignboston
|
November 1, 2012 at 6:47 am
Hello,
last week we moved our site from a development to a live server. Things were fine on dev, but now that we’re live, events that should appear active keep appearing as expired. Now and then, I can get one to display as active , but by and large, they keep being expired. Our account info is up to date, key is active, registration is open. Thanks for your help.
|
|
Dean
|
November 1, 2012 at 6:59 am
Hi,
Have you checked your time/date settings?
|
|
girlsrockcampaignboston
|
November 1, 2012 at 7:27 am
Hi Dean,
our time/date settings appear to be fine. For example, we have an event that has an “open” status in EE, registration started today at 12am, and registration ends on 2/4/13. Our attendee limit is “unlimited” yet the event still appears as expired on and off in the front end. I’m thinking this is a bug since the display is being really inconsistent. I’m not sure how to tackle it though. For instance, would re-installing the plugin help?
|
|
Josh
|
November 1, 2012 at 7:35 am
Hi there,
I think what Dean was referring to was the time / date settings in WordPress> Settings >General. In this case, they should be consistent to what was set up on the dev site, and set to a City in the same time zone (not UTC).
You could try deactivating and re-installing a fresh copy of Event Espresso, especially if you think some files were altered somewhere along the way.
|
|
girlsrockcampaignboston
|
November 1, 2012 at 7:45 am
Thanks Josh,
the general time/date settings in WP are the same (NY timezone, not UTC). Is the best bet uninstalling/re-installing at this point?
|
|
Josh
|
November 1, 2012 at 8:02 am
Hi there,
It’s a good next troubleshooting step to take. If some of the files were changed somewhere along the way, and this is what’s causing the issue, then uploading a fresh copy of the plugin will resolve it. If there’s nothing wrong with the files, the next place to look is the database. Sometimes, and it can vary with the method of database migration that was used, the data that was copied over may have been corrupted. So another approach to take would be to compare the event data from the original dev site to the event data on the live site.
|
|
girlsrockcampaignboston
|
November 1, 2012 at 1:37 pm
Thanks for your help (again). Just wanted to follow up and let you know found the problem. We were using a caching plugin to increase speed and such, but it was majorly conflicting with EE and forcing events to display as expired off and on. The only solution was to nix that plugin. Just wanted to share this in case it helps anyone going forward.
|
|
Josh
|
November 1, 2012 at 2:10 pm
Thanks for sharing. Some of the more popular caching plugins will let you exclude specific pages from being cached. In this case, you could still use the caching plugin and exclude the pages that handle the event registration and payments.
|
