Support

November 19, 2015 at 3:50 pm

Hi there,

The community forums aren’t monitored by support staff as actively as the premium forums, as you have a support license you can post there for fast responses.
(I will move this post to that forum)

Are you using the latest version of Event Espresso 4? We recently found a plugin conflict that caused this that was fixed in 4.8.24. If you are not using that version can you please update and retest this.

November 20, 2015 at 3:54 am

Ok, edit your registration checkout page, this one:

http://www.stimulus.com.pe/registration-checkout/

Make no changes but simply click to update.

Then go to Event Espresso -> General Settings -> Critical Pages.

Check that ‘Registration Checkout’ is selected within ‘Registration Checkout Page’ dropdown – http://take.ms/6kmFs

Then click save.

Does the shortcode now work?

November 20, 2015 at 8:26 am

Create a new page, it can be called anything, for example ‘Checkout’ and place [ESPRESSO_CHECKOUT] within that page. Use text mode on the editor to make sure there are not unexpected characters within the shortcode.

Publish that page.

Then go to Event Espresso -> General Setting -> Critical pages

Within the ‘Registration Checkout Page’ mentioned above, select the new page you have just created and save the settings. Then run a test registration and see if that works.

If not it may be a theme or plugin conflict, but lets confirm the above first.

November 20, 2015 at 7:51 pm

Hi Jose,

We have various members that are using Visual Composer along with Templatera and we fixed this issue in an earlier release this week. We verified this fix on our own testing sites as well as several member sites.

Using an up to date version of Visual Composer, Templatera, and Event Espresso should also fix it for you.

Thanks

—
Lorenzo

November 24, 2015 at 1:28 am

It’s supposed that newer versions of aplications works ok with previous version of other “side-aplications”.

That is not always possible.

With plugin conflicts we can only help when using the latest versions of both plugins, it is impossible for us to provide compatibility for each version of every plugin.

We were not supose to make more payments for an error that isn’t ours.

It is expected that you would be using the latest versions of your plugins and WordPress for not only the reasons above, but using older versions will always run the risk of running into security vulnerabilities and/or plugin conflicts with other plugins.

Please let know what we’re going to do if the Visual Composer upgrade doesn’t work.

We have tested Event Espresso with the latest version of VC and Templatera and it works as expected. If you would like to send me a full copy of your theme I will install it locally with the latest versions of both plugins and see if the shortcode parses.

If you would like to send me a copy of the theme you will need to host the zip file somewhere (for example Dropbox or even the site itself) and provide a link we can dowm the,e from.

(Note this is not a theme review, nor a full compatibility test but simply to check your current issue)

November 24, 2015 at 11:03 am

The theme + EE4 work just fine with the latest version of Visual Composer installed. Since that plugin is required by your theme, I wonder if you can make a backup of the Visual Composer plugin, then delete it from your site, then go to the /wp-admin/themes.php?page=install-required-plugins page on your site, and re-install the Visual Composer plugin? I think it might grab the latest version for you.

November 24, 2015 at 11:54 am

This means your server is running low on memory, which is expected since Visual Composer requires a lot of memory. You can either contact your host to see if they’ll increase the memory limit or try increasing the WP_MEMORY_LIMIT by editing the wp_config.php file. Something like

define( 'WP_MEMORY_LIMIT', '96M' );

or

define( 'WP_MEMORY_LIMIT', '128M' );

should work.

November 24, 2015 at 12:12 pm

If you deactivate Templatera again, does it fix the issue?

November 24, 2015 at 2:38 pm

The templatera version number is irrelevant because you’re seeing the same breakage occur with templatera deactivated.

What I can suggest is find which plugin is causing the breakage. You start with Event Espresso activated and activate VC next. If it’s broken with VC + EE4 only, then that’s a start and will help us know where to look next. If it’s not broken with VC + EE4 only, then you continue to reactivate plugins one by one until you find the plugin that’s causing the breakage.