Support

September 21, 2022 at 8:51 am

Hi Andreo,

Issue 1:
Some events have different dates compared to EE3 data.

That event’s dates are yesterday which is when I assume you ran the migration, which would leave me thinking the request timed out when generating the datetimes for that event and they defaulted to ‘now’.

Do we need to re-do data migration to solve issue?

Other than manually fixing the events with this issue yes you would need to re-run the migration and see if it happened again.

We have an option to change the migration step size if the current batches are causing timeouts.

The default step size is 50 but you can add:

define('EE_MIGRATION_STEP_SIZE', 30);

To your site’s wp-config.php file to reduce that down to 30 in my example but you can reduce it further if needed, the migrations will take a little longer but that should prevent timeouts if it is taking too long to process 50 currently.

Issue 2:
EE4 seems to have a compatibility issue with Avada theme.

That’s a new one on me. Especially as its only happening with the ticket selector.

You’ve asked why EE3 worked and EE4 doesn’t here and its all connected.

With EE3 we basically a complete template system within EE3 itself, which sounds great but it meant that all of your event output was totally separate from your standard theme output. The theme did its own thing and EE3 did its own thing outside of that to output events, reg forms etc. The look would be completely different becuase of the fact they they are indeed totally separate.

With EE4 we took a more integrated approach, EE4 events are a custom post type (infact they are a hybrid, but do things more of ‘the WP way’ than EE3 does) and we hook into the theme’s output for posts (because that’s exactly what they are) in inject the event content on the fly. That means you get more integration with themes, event posts look more like the rest of the site out of the box and so on.

Both have their pros and cons but integrating with the WP way and theme’s was a big plus for EE4 and one of the design choices we made very early on when designing the system.

Now, the reason that only the ticket selector is missing is interesting is because of how the content injection works. We sometimes see themes doing crazy things in the background and running the_content multiple times for a single post. EE not wanting to inject multiple sets of data will only inject the event details once on the_content and then skip if it runs again… however, that doesn’t seem to be the case here because all of the other even content is being injected and only the ticket selector is missing. I’ve not seen the ticket selector (and only the ticket selector) being missing from a request, what’s more is the ‘Register now’ button…. IS part of the ticket selector, so its injected but not all of it?

It will make sense as to why when the issue is found, but right now, its an odd one!

Can you send me a copy of the version of Avada you are using so I can test this locally and see if I can reproduce?

October 4, 2022 at 2:08 pm

You’re most welcome, I’m more than happy to answer any additional questions.

October 5, 2022 at 1:19 pm

Package up the current version you are suing and send it over, please.