|
Erica Lange
|
September 25, 2014 at 3:57 am
Hi Guys,
I have been battling this painful issue for weeks now. Based on the last suggestion, I have removed any previously installed cache files in proper manner. Event still don’t proceed past the initial ticket selection page. I have also installed wordpress from scratch and imported the database. I need a solution.
Here is my previous support thread: https://eventespresso.com/topic/event-not-proceeding-to-registration-page/
I can provide you further details over email, but we really need a concrete solution, otherwise we will need to move from EE. EE is great, but this is highly frustrating as we have severely upset client and office members at this point.
|
|
Dean
|
September 25, 2014 at 5:32 am
Hi Dana,
I took a look at the site and I see that this is still occurring on some events. You’ve advised that you have cleared the cache and removed caching plugins and I assume removed the lingering parts of those as well (.htaccess)?
If so, have you spoken to your host (GoDaddy?) to see if there is any server level caching occurring?
I know GoDaddy does use server caching but I believe it depends on the type of hosting you have, though it might be worth giving this a try https://support.godaddy.com/help/article/8057/clearing-the-server-cache-using-website-accelerator?countrysite=uk
|
|
Erica Lange
|
September 25, 2014 at 7:04 am
Hi,
Website accelerator is not on our account. Is there no other solution? What else can we do clean up the database?
|
|
Tony
|
September 25, 2014 at 7:47 am
Hi Dana,
If you re-create one of the effected events with the exact same details (the event slug will be slightly different) does the same happen to that event?
|
|
Erica Lange
|
September 25, 2014 at 8:24 am
Yes, issue still happens.
|
|
Josh
|
September 25, 2014 at 10:13 am
Hi there,
Can you ask Godaddy to move you to a different server? I realize this may sound strange, but I have a friend that was having all kinds of strange issues with their WordPress website, and Godaddy moved them to a different server and it turned out that after moving all their issues resolved.
Along with that, there’s another instance where this has been reported, and we migrated the site’s database to a different server (for testing) and on the other server, the issue went away. That’s the same data, only on a different server.
|
