Home Forums Event Espresso Premium Update on test-Page

Update on test-Page

Posted: May 8, 2020 at 7:17 am


May 8, 2020 at 7:17 am


unfortunately my new theme does not work with EventEspresso (Thrive Theme Builder). The support from ThriveThemes wanted to take care of this, but it requires the current version of EventEspresso on my test page. How can I update EventEspresso on my test-page?

Best regards

Seth Shoultes

  • Support Staff

May 8, 2020 at 8:01 am

Hi there,

If you go to your profile page on our site, then scroll down a little and look at the right column, you should see a “Downloads” section. From there you can download the latest available version of EE4, then install it onto your test site. You can also share the files with them if that helps.


  • Support Staff

May 8, 2020 at 9:17 am

Just to clarify the above incase it isn’t clear.

If you update Event Espresso it will update the version used on the entire site, you can update a specific page. The best way will be to share the dow load with them so they can install it on a test site.

May I ask what the issue is with the theme?


May 11, 2020 at 4:56 am

Many thanks! When I open an event with ThriveArchitect, I get a WordPress error message. This bug only occurs with ThriveThemes’ ThemeBuilder.


May 11, 2020 at 5:06 am

I have downloaded and installed EE from my profile page. But it doesn’t seem to be the latest version, because I get the message “An automatic update for Event Espresso is available”. What now?


  • Support Staff

May 11, 2020 at 6:10 am

Hi there,

Looking at the site linked to your license you have the latest version installed, is the above on a dev site or the main site?

Can you add a screenshot that shows the above please?


May 11, 2020 at 6:29 am

many thanks for your answer. When I open an event there is a general error message from WordPress. I will then receive an email with the following content:

Ein Fehler vom Typ E_ERROR wurde in der Zeile 1518 der Datei /var/www/vhosts/ verursacht. Fehlermeldung: Uncaught Error: Class ‘Thrive\Theme\AMP\Settings’ not found in /var/www/vhosts/
Stack trace:
#0 /var/www/vhosts/ Thrive_Architect::tcb_post_element_extend_config(Array)
#1 /var/www/vhosts/ WP_Hook->apply_filters(Array, Array)
#2 /var/www/vhosts/ apply_filters(‘tcb_post_elemen…’, Array)
#3 /var/www/vhosts/ TCB_Post_Element->own_components()
#4 /var/www/vhosts/


  • Support Staff

May 11, 2020 at 8:10 am

Ok, I don’t know how your server is set up, or the sites you are logging into but your main site is linked to your license and that has the latest version of Event Espresso installed:

The above errors are from a directory so I assume that a test site. You’ll need to install the update on that version of the site as well, you can do that manually, you can do that following this:

Something to note that whilst the above builder may well end up working within EE’s editor, Event Espresso is not compatible with page builders in that you will not be able to control the individually sections of EE events like you can other pages.


May 12, 2020 at 6:06 am

That doesn’t sound good. The support from ThriveThemes answered the following. Does that help?

“Upon checking the video and the error, it seems there are missing parameters for the files that cause the site not to function properly. I logged into your site and noticed your Thrive plugins are outdated. I updated the plugins as we need to eliminate the version of the plugin as a potential cause of the issue.

However, updating the plugins doesn’t fix the issue. I force install Thrive Architect to see if this will fix the issue. Upon further checking, it seems Event Espresso is changing the parameters to call Thrive Architect.

I tested one of the pages using the normal page option and I was able to open it using Thrive Architect.

Please see:

Then I checked the page using Event Espresso. The needed parameter for Thrive Architect is not available.

Please see:

I’m afraid without the right URL parameter, Thrive Architect will not work. I believe Event Espresso controls the URL. I would suggest reaching this out to the plugin developer as they might be able to assist you with this issue since they have a better understanding of how the plugin is working.”


  • Support Staff

May 12, 2020 at 9:50 am

The issue is not “EE changing the parameters to call Thrive Architect”.

The first screenshot shows Thrive loading on the default WordPress post edito route using &action=architect&tve=true

The second screenshot shows Thrive is trying to load on EE event editor using:

&action=architect&tve=true (with some additional parameters, such as page, post ID and a nonce )

So I’m not sure how they think EE is changing anything there.

The problem appears to be that Thrive is loading on the editor and expecting it to be loaded on the default WP routes. So when you click on that button it’s trying to load code that Thrive (not EE) has not loaded and throws a fatal error.

The error itself shows this:

Uncaught Error: Class ‘Thrive\Theme\AMP\Settings’ not found in /wp-content/themes/thrive-theme/integrations/architect/class-thrive-architect.php:1518

Thrive can’t find the class Thrive\Theme\AMP\Settings from within class-thrive-architect.php:1518.

This likely means the editor is not compatible with EE’s event editor and can not be used. There may be a way to force Thrive to load there assets on additional routes but again, it isn’t going to give you full control over each of EE’s event elements due to how it works.


May 13, 2020 at 1:37 am

Many, many thanks. I will forward this to ThriveThemes. Maybe this will help there.
Best regards

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3 Documentation for Event Espresso 4

Status: publish

Updated by  hepar 5 months, 2 weeks ago ago

Topic Tags


This topic is:
Do NOT follow this link or you will be banned from the site!
[gravityform id=80 title=false description=false ajax=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_80' ><form method='post' enctype='multipart/form-data' id='gform_80' action='/topic/update-on-test-page/'> <div class='gform_body'><ul id='gform_fields_80' class='gform_fields top_label form_sublabel_below description_below'><li id='field_80_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_1' >First name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_80_1' type='text' value='' class='medium' aria-required="true" aria-invalid="false" /></div></li><li id='field_80_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_2' >Email address<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_email'> <input name='input_2' id='input_80_2' type='email' value='' class='medium' aria-required="true" aria-invalid="false" /> </div></li><li id='field_80_3' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_80_3'><li class='gchoice_80_3_1'> <input name='input_3.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_80_3_1' /> <label for='choice_80_3_1' id='label_80_3_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_80_4' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_4' >Phone</label><div class='ginput_container'><input name='input_4' id='input_80_4' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description_80_4'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_80' class='gform_button button' value='Download Now' onclick='if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} jQuery("#gform_80").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_80' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='80' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_80' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_80' id='gform_target_page_number_80' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_80' id='gform_source_page_number_80' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 80) {} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [80, 1]) } ); </script>