|
Florida Abolitionist
|
March 31, 2016 at 6:02 am
When someone goes to a Registration Page the fields are filled with the previous registrant’s information.
Event Page
|
|
Tony
|
March 31, 2016 at 7:44 am
Hi there,
This is likely due to some form of caching.
Are you running any caching plugins on the site?
Can you check with your host if they run server side caching. If so they’ll need to disable it on the EE4 Critical pages.
We have an example of disabling page caching here: https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
However I suspect this is some form of object/database caching.
|
|
Florida Abolitionist
|
March 31, 2016 at 8:11 am
I have no caching plugins and have no conflicting 3rd party plugin from this forum post, except the noted settings for SEO Yoast and Shortcodes Ultimate.
This seemded to occur when I upgraded from decaf 4.7.13 to 4.8.37. I moved to the full 4.8.38 in hopes that this would solve the issue.
|
|
Florida Abolitionist
|
March 31, 2016 at 8:14 am
I did install W3 Total Cache many months ago, but disabled and deleted the plugin. It performed very poorly on my Google Cloud Platform install.
|
|
Josh
|
March 31, 2016 at 12:24 pm
Looks like you’ll need to configure your installation to not use the built-caching that’s included with the Google Cloud Platform.
|
|
Florida Abolitionist
|
March 31, 2016 at 12:40 pm
As far as I can tell there are no built-in caching. I am using Compute Engine not App Engine. The only caching I see in the install is in the wp-incudes folder is a cache.php. But this looks like core WP functions.
|
|
Josh
|
March 31, 2016 at 1:48 pm
If you go in and make a small edit to the /event-registration/ page, does the past user information in the registration fields go away? If so, that’s a good indication this is being served from a cache.
-
This reply was modified 8 years, 1 month ago by
 Josh. Reason: updated URL
|
|
Florida Abolitionist
|
April 2, 2016 at 6:53 am
I added some text to the Event Registration page below the [ESPRESSO_CHECKOUT] and the past user dat is still there, plus the wrong event information.
I created a new event with the same information and it also shows old information, but at least the event information is correct. So I will start using the duplicated version and just keep track of the registrants from the old one.
But I need to solve why the previous data is getting loaded.
|
|
Josh
|
April 2, 2016 at 8:41 am
Hi there,
It’s usually caching that causes this. Can you try installing Event Espresso on a different server?
|
|
Florida Abolitionist
|
April 3, 2016 at 6:27 am
I ran a Curl -I and no caching is being set. This is the page information that is being generated. Why are the default values already set?
<div id="ee_reg_qstn-139-fname-415-input-dv" class="ee-reg-qstn ee-reg-qstn-fname-input-dv">
<label id="ee_reg_qstn-139-fname-lbl-415" class="ee-required-label ee-reg-qstn" style="" for="ee_reg_qstn[139][fname][415]">First Name<span class="ee-asterisk">*</span></label>
<input type="text" name="ee_reg_qstn[139][fname][415]" id="ee_reg_qstn-139-fname-415" class="ee-required ee-reg-qstn ee-reg-qstn-fname" required value="Diana" style=""/>
</div>
<!-- close ee_reg_qstn-139-fname-415-input-dv -->
<div id="ee_reg_qstn-139-lname-416-input-dv" class="ee-reg-qstn ee-reg-qstn-lname-input-dv">
<label id="ee_reg_qstn-139-lname-lbl-416" class="ee-required-label ee-reg-qstn" style="" for="ee_reg_qstn[139][lname][416]">Last Name<span class="ee-asterisk">*</span></label>
<input type="text" name="ee_reg_qstn[139][lname][416]" id="ee_reg_qstn-139-lname-416" class="ee-required ee-reg-qstn ee-reg-qstn-lname" required value="Ludwig" style=""/>
</div>
<!-- close ee_reg_qstn-139-lname-416-input-dv -->
<div id="ee_reg_qstn-139-email-417-input-dv" class="ee-reg-qstn ee-reg-qstn-email email-input-dv">
<label id="ee_reg_qstn-139-email-lbl-417" class="ee-required-label ee-reg-qstn" style="" for="ee_reg_qstn[139][email][417]">Email Address<span class="ee-asterisk">*</span></label>
<input type="text" name="ee_reg_qstn[139][email][417]" id="ee_reg_qstn-139-email-417" class="ee-required ee-reg-qstn ee-reg-qstn-email email" required value="sparklemimi3@gmail.com" style=""/>
</div>
<!-- close ee_reg_qstn-139-email-417-input-dv -->
</div>
<!-- close ee-reg-form-qstn-grp-personal-information-1445458771 -->
|
|
Josh
|
April 4, 2016 at 9:18 am
Hi there,
Every time we’ve seen this happen before it’s because the page is being served from a cache.
|
