|
ACAEvents
|
July 28, 2021 at 5:39 pm
Hi, we have a multisite with two events systems and two “Everything” licences.
I updated the network and now one is working
membership.corrosion.com.au
This one is reporting a licence failure and I have one event with a critical error. I am just ruling out this as a reason.
membership.corrosion.com.au/training
|
|
Tony
|
July 29, 2021 at 5:37 am
Hi there,
Currently, Event Espresso doesn’t officially support multisite. That’s not to say it won’t work with it but the licencing system can easily throw false positives with it.
The good news is that licence errors/notices/warnings/issues do not change Event Espresso’s functionality, we intentionally designed it not to. It’ll throw a notice or show you something in the admin you can’t use the one-click update whilst the licence is ‘flagged’ (although you can always manually update) but then should otherwise work as normal.
So, you mentioned a licence failure error, can you post that error here so I can check into it?
The critical error you mention on an event, which event is throwing that?
If you check the server errors logs at the same time you trigger the error, what error does it show?
|
|
ACAEvents
|
July 29, 2021 at 6:57 pm
Since the upgrade, to 4.10.13.p it is throwing a WordPress critical error 500
|
|
ACAEvents
|
July 29, 2021 at 9:57 pm
Update. I have disabled the Stripe payment plugin and registrations are now going through for EFT.
|
|
Tony
|
July 30, 2021 at 7:02 am
So the error only happened when using the Stripe payment method?
When you updated to 4.10.13.p did you also update the server to use PHP8?
If you check the server error logs (your host will usually have a section to view them in your control panel) around the time you were getting the critical error can you see an error from Event Espresso (or the Stripe payment method)?
|
|
ACAEvents
|
August 1, 2021 at 7:59 pm
This reply has been marked as private.
|
|
Tony
|
August 2, 2021 at 3:39 am
That’s strange, updating Event Espresso 4 core (the main plugin) shouldn’t change the payment method settings as those are stored within each add-on’s own config and core doesn’t change those when updating.
If you can check the error logs and post whatever error is being thrown when connected via elements I can investigate this further.
|
