|
Chris Stambaugh
|
February 12, 2014 at 1:35 pm
Hi,
(This happened on the initial release of EE and on EE Version 4.1.1.reg)
I have this short code (and nothing else) on a page:
[ESPRESSO_TICKET_SELECTOR event_id=’4911′]
When I view the page, there is nothing there other than the page title.
URL of the page in question is: http://www.bsop.ca/landscape-photography-class/test-edmonton-portrait-photography-classes-feb-12-2014/
If I call the shortlink directly, the event seems to work, but I’d really like the shortcode embedded on a page to work too.
Any ideas?
Paul
|
|
Josh
|
February 12, 2014 at 6:33 pm
Hi Paul,
I’m having trouble reproducing this, there should be *something* on that page other than a page title. Some information about your setup may help us investigate. Can you go to the Event Espresso > Maintenance > System Information tab, copy the contents of the raw system data text area, paste into a .txt file, and send to support@eventespresso.com?
|
|
Chris Stambaugh
|
February 13, 2014 at 8:08 am
Hi,
Just emailed you the file.
To save some time, I also gave you login privileges and filled in your form.
Paul
|
|
Josh
|
February 13, 2014 at 2:13 pm
Hi Paul,
It may help to see if are any PHP errors getting thrown when that page loads. Can you try turning on WP_DEBUG for a momemnt by changing its value in the wp-config.php file?
We have released an update today, which could potentially help since there were some related shortcode fixes, so that’s one other thing you could try.
|
|
Chris Stambaugh
|
February 13, 2014 at 2:22 pm
Hi,
I upgraded to 4.1.2 today and that didn’t fix it. Turned on WP_DEBUG and here’s what came up…
Strict Standards: Declaration of aec_contributor_list::form() should be compatible with WP_Widget::form($instance) in *moderated*/wp-content/plugins/ajax-event-calendar/inc/widget-contributors.php on line 64
Warning: Cannot modify header information – headers already sent by (output started at *moderated*/wp-content/plugins/ajax-event-calendar/inc/widget-contributors.php:64) in *moderated*/wp-content/plugins/bad-behavior/bad-behavior/screener.inc.php on line 12
Strict Standards: Redefining already defined constructor for class JCP_UseGoogleLibraries in *moderated*/wp-content/plugins/use-google-libraries/use-google-libraries.php on line 123
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at *moderated*/wp-content/plugins/ajax-event-calendar/inc/widget-contributors.php:64) in *moderated*/wp-content/plugins/eventespresso.tmp/core/EE_Session.core.php on line 247
Notice: Cookie cannot be set – headers already sent in *moderated*/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 365
Notice: Cookie cannot be set – headers already sent in *moderated*/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 365
Notice: Cookie cannot be set – headers already sent in *moderated*/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 365
Notice: Undefined index: giftcertificates_signup_action in *moderated*/wp-content/plugins/gift-certificates/gift-certificates.php on line 1471
-
This reply was modified 10 years, 9 months ago by
 Josh. Reason: moderated server path info for security purposes
|
|
Josh
|
February 13, 2014 at 2:38 pm
Hi Paul,
Notices are usually fine, but warnings can be significant. This one may be indicative of a conflict between Bad Behavior and Ajax event calendar. You could try deactivating those temporarily to see if that help:
Warning: Cannot modify header information – headers already sent by (output started at /ss/wp-content/plugins/ajax-event-calendar/inc/widget-contributors.php:64) in /xx/wp-content/plugins/bad-behavior/bad-behavior/screener.inc.php on line 12
|
|
Chris Stambaugh
|
February 13, 2014 at 4:08 pm
Hi,
Turning off those plugins made no difference.
Paul
|
|
Dean
|
February 14, 2014 at 3:57 am
Hi Paul,
After you turned those plugins off did you clear your cache? If so can you try the debug again please (with the addons turned off) so that we can see how the error s have changed.
|
|
Chris Stambaugh
|
February 14, 2014 at 8:04 am
Yes, I did clear my cache. Here is what debug reports now:
Strict Standards: Redefining already defined constructor for class JCP_UseGoogleLibraries in /xx/wp-content/plugins/use-google-libraries/use-google-libraries.php on line 123
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /xx/wp-content/plugins/use-google-libraries/use-google-libraries.php:123) in /xx/wp-content/plugins/eventespresso.tmp/core/EE_Session.core.php on line 247
Notice: Cookie cannot be set – headers already sent in /xx/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 365
Notice: Cookie cannot be set – headers already sent in /xx/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 365
Notice: Cookie cannot be set – headers already sent in /xx/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 365
Notice: Undefined index: giftcertificates_signup_action in /xx/wp-content/plugins/gift-certificates/gift-certificates.php on line 1471
-
This reply was modified 10 years, 9 months ago by Josh. Reason: removed sensitive server details-- please do not post these in a public forum
|
|
Josh
|
February 14, 2014 at 8:14 am
Hi Paul,
At this point I don’t think this is a plugin conflict, but I could be wrong and to be sure, can you try deactivating each of the plugins that are throwing an error?
Another possibility that I’m thinking of is a possible database issue, can you check the MySQL error log in your host’s control panel? What we’re looking for is an error that gets logged at the exact moment the page in question loads up. So if something gets logged right after you refresh that page, that could be a clue.
|
|
Chris Stambaugh
|
February 18, 2014 at 10:45 am
Hi,
Upgraded to most recent version of EE 4.1.3.reg and I finally got access to my mysql log file. Trying to access the page where the event short code isn’t working does not throw an SQL error.
I also tried deactivating every plugin that was throwing an error and it made no difference.
I need to get this fixed ASAP. This is a _BIG_ deal as I need to launch and am losing money every day this isn’t fixed. Could someone please spend some time on this issue?
Thanks,
Paul
|
|
Josh
|
February 18, 2014 at 10:51 am
Hi Paul,
It turns out that I’ve spent quite a bit of time on this issue trying to re-create it on a test site and combing through your website trying to find a clue why this isn’t working on your site. To be clear, it’s working on our test sites. If you can send an export of your site’s database tables to our support@eventespresso.com email address we can investigate further.
|
|
Chris Stambaugh
|
February 18, 2014 at 1:12 pm
I emailed you a link to a Dropbox location as the file is too big to email.
|
|
Josh
|
February 18, 2014 at 1:25 pm
Update:
I took another crack at this and I figured out how to reproduce this. What it involves is setting the page that has the ticket selector shortcode on it to have a parent page. I’ve created a ticket for the dev team to work on a fix. In the meantime, if you set to page to not have a parent page, the shortcode should work fine.
If you need the pages that have event info to be nested within a navigation menu, this can be done by nesting the pages under a menu item in the WordPress menu manager.
|
|
Chris Stambaugh
|
February 18, 2014 at 1:58 pm
Great work Josh!
Paul
|
|
Josh
|
February 18, 2014 at 2:38 pm
Hi Paul,
We’ll have a fix for this in the next update.
|
|
Josh
|
February 18, 2014 at 5:52 pm
The update is now available and it includes the fix for the event shortcode not displaying on nested pages.
|
