|
cmventures2
|
August 3, 2018 at 2:45 am
Hi
After recently updating event espresso, when a user goes into their account to check tickets, the footer disappears and they can no longer click on the cog to view transactions.
|
|
cmventures2
|
August 3, 2018 at 3:18 am
It looks like a conflict with the [ESPRESSO_MY_EVENTS] shortcode. When I remove it, the rest of the page loads fine
|
|
cmventures2
|
August 3, 2018 at 3:26 am
After checking recent updates, it seems that there were updates to [ESPRESSO_MY_EVENTS] in the WP user integration in March. Could this have caused the conflict.
I have determined it is not the theme causing the issue as I have reverted back to twenty seventeen theme and it occurs there too
|
|
Josh
|
August 3, 2018 at 7:26 am
Hi,
The first thing to do is turn on WP_DEBUG mode so you can see the error that’s being thrown.
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
If you have any customizations made to the templates that output the ESPRESSO_MY_EVENTS shortcode the customizations may need to be updated.
|
|
cmventures2
|
August 6, 2018 at 3:55 am
There have been no customisation made to the plugin. The problem occurred after the latest updates were made.
Am i able to find previous versions of event espresso so I can downgrade?
|
|
Tony
|
August 6, 2018 at 4:01 am
Whilst we can send you a copy of the previous version of the EE4 user integration add-on (thats what outputs the ESPRESSO_MY_EVENTS shortcode), that’s not really a solution as without the error you’ll be stuck on that same version indefinitely.
Can you add the code Josh mentioned to the site:
The first thing to do is turn on WP_DEBUG mode so you can see the error that’s being thrown.
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
View the page to throw the error and then look in /wp-content/debug.log
Do you see any errors in that file?
|
|
cmventures2
|
August 6, 2018 at 4:48 am
I have checked the file and can not see any errors.
Please see the error log below
**Removed**
-
This reply was modified 6 years, 3 months ago by
 Tony. Reason: Removes espresso_log content
|
|
Tony
|
August 6, 2018 at 5:01 am
That looks like the espresso_log.txt file rather than the debug.log from /wp-content/, can you double check that’s the correct file?
I’ve removed it from the above reply as it doesn’t help with the problem but bloats the page.
|
|
cmventures2
|
August 6, 2018 at 5:31 am
I enabled full logging and it gave me this file address /wp-content/uploads/espresso/logs/espresso_log_40e71d158b070b9885da6ff75ec9917d.txt
|
|
Tony
|
August 6, 2018 at 5:36 am
That’s a different type of file, it stores the functions called during EE’s operation and is of no use for the problem you are running into, you can disable that setting.
You need to enable WP_DEBUG on the site so that it stores any PHP errors that are being thrown on the page. You may have them already if you hosts provides an error_log or you can add the code Josh linked to:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
To your wp-config.php file using FTP to enable error logging to /wp-content/debug.log so we can view it.
|
