|
Greg Millican
|
August 30, 2015 at 9:23 pm
I’m creating my first event, and after following as closely as I could the guide for EE4, I have my event set up (I think). When I go to see it, the page is blank. I’ve tried to follow some of the other solutions posted, but I am a bit of a wordpress rookie. Any suggestions would be appreciated.
The event page is: http://www.telg.com.au/register/lismore-engineering-link-project/
|
|
Dean
|
August 31, 2015 at 6:13 am
Hi Greg,
Can you start by going to the WordPress admin, the the Settings menu, then select Permalinks, then scroll down and press the Save Changes button (you don’t need to actually do anything apart form click the button).
What this does is “flush” the permalinks, which basically clears out any old URL structure (e.g. website.com/2015/August/post) and makes sure any new one is visible (e.g. website.com/post).
If that does not help, let us know.
|
|
Greg Millican
|
August 31, 2015 at 4:29 pm
I did try that previously (from another thread from earlier in the year). I did it again, and I also just updated to the latest version (now at 4.8.7.p).
The event is still blank.
I have created a guest access to our site, if you want that (I can PM it to you if you need).
|
|
Josh
|
August 31, 2015 at 4:36 pm
Hi Greg,
It looks like there’s already a WordPress page that’s using the “register” slug. Can you go to Event Espresso > Events > Template Settings and change the event slug there so that it uses something other than “register”? Alternatively you can rename the existing register page and be sure to change its slug.
|
|
Greg Millican
|
August 31, 2015 at 4:44 pm
The “Event Slug” in our site is “events”. Sorry, I changed it back after I posted the original request, as it took away our existing registration page (we still need it until I get this working). I’ve tried again and it still doesn’t work.
When I tried the “register” slug, the event preview worked (needed some serious formatting, but I can keep working on that), but even then, when I clicked on the event to go to the individual event page, it was blank.
|
|
Josh
|
August 31, 2015 at 5:29 pm
Hi Greg,
Can you check your server’s PHP error log to see if it’s throwing a fatal error when the event page loads up?
|
|
Greg Millican
|
August 31, 2015 at 8:45 pm
How do I do that?
|
|
Greg Millican
|
August 31, 2015 at 8:47 pm
[01-Sep-2015 02:39:03 UTC] PHP Fatal error: Call to a member function is_espresso_page() on a non-object in /event-espresso-core-reg/core/CPTs/EE_CPT_Strategy.core.php on line 357
-
This reply was modified 9 years, 3 months ago by
 Tony. Reason: Removed multiple duplicate errors and server details
|
|
Greg Millican
|
August 31, 2015 at 8:48 pm
Sorry, did a cut and paste and didn’t realise until too late that it was the same error each time. I have no idea what it means, however.
|
|
Tony
|
September 1, 2015 at 5:55 am
Hi Grey,
I’ve removed the duplicates from your post and also the server path details (you don’t really want those in the wild).
We’ve seen this error previous and found it to be an issue with the sites theme hooking into all page requests and altering the query. (A plugin can also do the same thing)
Can you try temporarily switching to one of the default themes and see if the event pages is displayed correctly?
If you don’t have a development copy of the site I would recommend creating one to run through troubleshooting away from view of your visitors.
|
|
Greg Millican
|
September 1, 2015 at 4:43 pm
I currently don’t have a test site. I’ve contacted my host to see if I can get something like that organised, and then I’ll do as you’ve suggested and see what we get.
|
|
Tony
|
September 2, 2015 at 1:55 am
Hi Greg,
Did you manage to get a development site up and running?
Just to note you can set up a development site either locally or on the same server.
A development site is not a requirement in order to work through this it just prevents your visitors viewing the changes your making to the site to work through it (such as changing themes or disabling plugins) it also allows you to run updates on a ‘working copy’ of the site to check for any issues before doing so on the live site.
We can provide steps to troubleshoot this on the live site, although it involves switching to a default theme and de-activating all non-EE plugins, which is why I recommended a dev site.
|
