Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Upgrading from Free to Paid, Shortcodes no longer work | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Upgrading from Free to Paid, Shortcodes no longer work

Upgrading from Free to Paid, Shortcodes no longer work

Posted: February 25, 2014 at 6:09 am

Viewing 4 reply threads


mamamojo

February 25, 2014 at 6:09 am

Hi, I set up our website with the free version of EE. I used two shortcodes on the site. One displayed a SINGLEEVENT in a widget (with assistance from the Use Shortcodes in Sidebar Widgets plugin) and the other did ESPRESSO_CHECKOUT on a page. All was going well so we bought in. I downloaded EE 4.1.5.reg and installed it, but now neither of the shortcodes work. I’m up to date on all my other plugins and I’m running WP 3.8.1. Any advice? Thank you! Looking forward to getting this working!

:)


Dean

  • Support Staff

    •

February 25, 2014 at 6:54 am

Hi,

OK so you have updated from the Lite to the super new version 4. This version is radically different to version 3 (which the Lite version is based off) so some of the ways in which it works has changed.

It would be a good idea to check out this post http://staging.eventespresso.com/2014/02/event-espresso-4-beta-officially-released/

The events are now custom post types, so they will appear when you type /events/ after your domain name.

You can also make a list of them show on a specific post or page by using [ESPRESSO_EVENTS]

You no longer need the single event shortcode as each event is it’s own post so will be found at /events/event-name/

I hope that makes some sense, feel free to ask for clarification or if you have further queries.

Documentation can be found here – http://staging.eventespresso.com/support/documentation/versioned-docs/?doc_ver=ee4


mamamojo

February 25, 2014 at 3:57 pm

thanks dean. sounds straightforward enough. i’ll read the links you cited and let you know if i have any issues. the googles didn’t find either of those pages.


mamamojo

February 25, 2014 at 7:53 pm

hmm… it seems i actually want to jump back to 3 before jumping in to 4. there are many things that are still add-ons that we were counting on being in the paid version.


Dean

  • Support Staff

    •

February 26, 2014 at 5:25 am

Hi,

No problem, we know that EE4 isn’t the right fit for everyone just yet, mainly due to the add ons not being ready.

To go back, obviously remove EE4 and reactivate EE#. You will need to remove the pages created by EE4 and set the old EE3 pages back. You will also need to check those pages to make sure they have the right shortcodes (these can be found in the General Settings page).

This does leave the tables in the database, so for a cleaner revert, use a backup from before the move to EE4.
Viewing 4 reply threads

The support post ‘Upgrading from Free to Paid, Shortcodes no longer work’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Dean 10 years, 10 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server