Support

Home Forums Event Espresso Premium Moving installation

Moving installation

Posted: July 27, 2020 at 8:59 pm


JohnB

July 27, 2020 at 8:59 pm

Hi Guys,

My developer is moving EE from the top domain to the subdomain (training.tatsa.com.au) so we can make better use of a number of your add-ons etc.

Just need some tips on best way to do this.

Does he download the basic EE4 plug-in and go from there (have full license) one by one as needed?

Thanks


Tony

  • Support Staff

July 28, 2020 at 6:05 am

Hi John,

Just to confirm, there are no add-opn that require EE be install on a subdomain so may I ask why you need to move the site for the add-ons?

Just need some tips on best way to do this.

Within Event Espresso a lot of the entities it uses are custom post types and we don’t have a method to pull ONLY the EE specific entities from one site into another, so if you are looking to copy all of the current EE data over you’ll need to copy the original site into a subdomain and then remove the data you don’t need from that site.

Or are you looking to start fresh on the subdomain?

Does he download the basic EE4 plug-in and go from there (have full license) one by one as needed?

I’m not really sure I understand your question but yes, he downloads EE4 from your account page and installs it on the subdomain site.


JohnB

July 30, 2020 at 6:33 pm

Thank you Tony,
The main reason for moving EE to the subdomain is to simplify integration with LearnDash. I was advised to use the add-on so EE & LD can integrate, they both need to be on same domain.
We are having a few minor issues getting everything set up on the subdomain. This might be due to only being able to register EE on one domain. As it is still active on the top domain, we can’t use the same key on sub-domain. Is there any way to bypass this during this development and testing stage?
Thanks again.
JB


JohnB

July 30, 2020 at 7:16 pm

I have requested reset of license key to move to subdomain – no active events on topdomain at present.


Tony

  • Support Staff

July 31, 2020 at 3:14 am

The main reason for moving EE to the subdomain is to simplify integration with LearnDash. I was advised to use the add-on so EE & LD can integrate, they both need to be on same domain.

Ah ok, I understand now.

We are having a few minor issues getting everything set up on the subdomain. This might be due to only being able to register EE on one domain. As it is still active on the top domain, we can’t use the same key on sub-domain. Is there any way to bypass this during this development and testing stage?

The license key has no effect on Event Espresso’s functionality, it is only used for support and one-click updates.

May I ask what issues are you running into?

I have requested reset of license key to move to subdomain – no active events on topdomain at present.

I’ve processes your license key although again, the key doesn’t stop Event Espresso from working at all.


JohnB

July 31, 2020 at 3:42 am

Thanks Tony,
The support key has now activated and things seem to be going fine now.

The only issue we are having now is when editing an event, the option to use the “builder” function isn’t showing. We use AVADA theme and this is part of of. It’s working in WP Posts but not for EE Events. Not sure if this is within your scope to respolve.

Thanks again.

JB


JohnB

July 31, 2020 at 3:46 am

Wahoo… was just informed they have that builder active again.

Thanks for your help

Good night from Australia


Tony

  • Support Staff

July 31, 2020 at 3:49 am

Event Espresso doesn’t support any page builders currently, some can load and be used within the event content but not to the same level of customizations that you would get with say a standard page.

However, I don’t think the Avada builder (Fusion iirc?) can be used within EE’s editor.

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  Tony 2 months, 3 weeks ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
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/moving-installation/'> <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' >Name</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>
[i]
[i]