|
Kevin G.
|
December 9, 2015 at 6:12 am
1. Datepicker does not work anymore
2. if i set ticket selector to “don’t show” in general settings, it still shows.
3. date sets the time +1 hour in frontend ?
4. layout of page events is messed up (see screenshot)
|
|
Kevin G.
|
December 9, 2015 at 6:14 am
|
|
Kevin G.
|
December 9, 2015 at 6:29 am
an other problem : after i clicked to go further to the payment selection i get a 404 : http://www.dancecool.be/thank-you/?e_reg_url_link=1-ff24ce69556edf92781d60573ec56512
|
|
Kevin G.
|
December 9, 2015 at 6:45 am
After i updated the permalinks of the thank you page, the last problem was resolved
|
|
Tony
|
December 9, 2015 at 6:48 am
If you enable WP_DEBUG are any errors shown?
Have you modified Event Espresso at all or have custom functionality hooking into EE?
How did you update Event Espresso? Via FTP or the plugin manage?
If you update via FTP you previously had an issue with the update when you did this, can you de-activate and delete the current version of EE your have installed and upload the latest version through the plugin manager please.
|
|
Kevin G.
|
December 9, 2015 at 6:59 am
No modifications added, the datepicker works on the registrationform, but it doesn’t work in backend.
I updated via plugin manage.
—————————————————————————————-
[2015-12-09 14:57:49] EE_Checkin.class.php
—————————————————————————————-
[2015-12-09 14:57:49] EE_Cron_Tasks -> log_scheduled_ee_crons()
[scheduled EE cron] AHEE__EE_Cron_Tasks__clean_up_junk_transactions
—————————————————————————————-
[2015-12-09 14:57:49] EE_PUE -> __construct()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Session -> __construct()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Session.core.php -> _espresso_session()
—————————————————————————————-
[2015-12-09 14:57:50] Messages_Admin_Page_Init.core.php -> __construct()
—————————————————————————————-
[2015-12-09 14:57:50] Registrations_Admin_Page_Init.core.php -> __construct()
—————————————————————————————-
[2015-12-09 14:57:50] Transactions_Admin_Page_Init.core.php -> __construct()
—————————————————————————————-
[2015-12-09 14:57:50] Pricing_Admin_Page_Init.core.php -> __construct()
—————————————————————————————-
[2015-12-09 14:57:50] Mailchimp_Admin_Page_Init.core.php -> __construct()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> _verify_routes()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> check_user_access()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> _add_registered_meta_boxes()
—————————————————————————————-
[2015-12-09 14:57:50] EE_System.core.php -> espresso_toolbar_items()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Error.core.php -> get_notices()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> _set_nav_tabs()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> check_user_access()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> check_user_access()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> check_user_access()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> check_user_access()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> _display_admin_page()
—————————————————————————————-
[2015-12-09 14:57:50] EE_Admin_Page.core.php -> admin_page_wrapper()
—————————————————————————————-
[2015-12-09 14:57:52] EE_Checkin.class.php
—————————————————————————————-
[2015-12-09 14:57:52] EE_Cron_Tasks -> log_scheduled_ee_crons()
[scheduled EE cron] AHEE__EE_Cron_Tasks__clean_up_junk_transactions
—————————————————————————————-
[2015-12-09 14:57:52] EE_PUE -> __construct()
—————————————————————————————-
[2015-12-09 14:57:53] EE_Session -> __construct()
—————————————————————————————-
[2015-12-09 14:57:53] EE_Session.core.php -> _espresso_session()
—————————————————————————————-
[2015-12-09 14:57:52] EE_Checkin.class.php
—————————————————————————————-
[2015-12-09 14:57:52] EE_Cron_Tasks -> log_scheduled_ee_crons()
[scheduled EE cron] AHEE__EE_Cron_Tasks__clean_up_junk_transactions
—————————————————————————————-
[2015-12-09 14:57:52] EE_PUE -> __construct()
—————————————————————————————-
[2015-12-09 14:57:53] EE_Session -> __construct()
—————————————————————————————-
[2015-12-09 14:57:53] EE_Session.core.php -> _espresso_session()
—————————————————————————————-
[2015-12-09 14:58:12] EE_Checkin.class.php
—————————————————————————————-
[2015-12-09 14:58:12] EE_Cron_Tasks -> log_scheduled_ee_crons()
[scheduled EE cron] AHEE__EE_Cron_Tasks__clean_up_junk_transactions
—————————————————————————————-
[2015-12-09 14:58:12] EE_Session -> __construct()
—————————————————————————————-
[2015-12-09 14:58:12] EE_Session.core.php -> _espresso_session()
—————————————————————————————-
[2015-12-09 14:58:12] EE_Session -> _create_espresso_session()
—————————————————————————————-
[2015-12-09 14:58:13] EE_Checkin.class.php
—————————————————————————————-
[2015-12-09 14:58:13] EE_Cron_Tasks -> log_scheduled_ee_crons()
[scheduled EE cron] AHEE__EE_Cron_Tasks__clean_up_junk_transactions
—————————————————————————————-
[2015-12-09 14:58:13] EE_PUE -> __construct()
—————————————————————————————-
[2015-12-09 14:58:14] EE_Session -> __construct()
—————————————————————————————-
[2015-12-09 14:58:14] EE_Session.core.php -> _espresso_session()
—————————————————————————————-
[2015-12-09 14:58:14] EE_Session -> _create_espresso_session()
—————————————————————————————-
[2015-12-09 14:58:16] EE_Checkin.class.php
—————————————————————————————-
[2015-12-09 14:58:16] EE_Cron_Tasks -> log_scheduled_ee_crons()
[scheduled EE cron] AHEE__EE_Cron_Tasks__clean_up_junk_transactions
—————————————————————————————-
[2015-12-09 14:58:16] EE_Session -> __construct()
—————————————————————————————-
[2015-12-09 14:58:16] EE_Session.core.php -> _espresso_session()
—————————————————————————————-
[2015-12-09 14:58:17] EE_Error.core.php -> get_notices()
|
|
Tony
|
December 9, 2015 at 7:24 am
Hmm, ok.
1. Datepicker does not work anymore
If you open Chrme Dev tools on that page are there any javascript errors shown?
2. if i set ticket selector to “don’t show” in general settings, it still shows.
There’s a couple of settings for this and they apply in different sections.
Both of these settings are within Event Espresso -> Events -> Templates.
Can you let me know which setting your changing and where the ticket selector still displays?
3. date sets the time +1 hour in frontend ?
Usually this is cuase by another plugin calling date_default_timezone_set() which causes problems within WordPress itself, take a look here:
https://weston.ruter.net/2013/04/02/do-not-change-the-default-timezone-from-utc-in-wordpress/
Do you have any other plugins that deal with dates/times?
4. layout of page events is messed up (see screenshot)
I’ve not seen this before, which WordPress version are you using?
If you de-activate all non-EE plugins and switch to a default theme such as twentyfourteen does it all work as expected then?
|
|
Kevin G.
|
December 9, 2015 at 7:56 am
1. no javascript errors
2. “Display Ticket Selector” : no & “ticket sale info” : no
Display ticket selector in a new event is by default : yes (and should be no)
3. No other plugin’s deal with dates (not that i know off)
4. wp 4.4 (latest version), i can’t just deactivate all the plugin’s on a live website, have to do this later on..
|
|
Josh
|
December 9, 2015 at 8:04 am
Hi Kevin,
Another thing you can do is duplicate the site onto a staging server (or even a separate folder on the same server if you only have one server to work with). Then you’ll have a site you can troubleshoot.
One thing to check for the one hour difference is the WordPress Date settings. You’ll want to set the Timezone to be a city in your timezone and not a UTC timezone.
|
|
Kevin G.
|
December 9, 2015 at 8:12 am
Hi Josh, that solved the time problem !
3 problems to go..
1. Datepicker does not work anymore
2. if i set ticket selector to “don’t show” in general settings, it still shows.
3. layout of page events is messed up (see screenshot)
|
|
Lorenzo Orlando Caum
|
December 9, 2015 at 9:16 am
Hi Kevin,
I looked at a few of our testing settings that are running the latest version of WordPress along with the latest version of Event Espresso 4 and I did not see the issues that you described.
I also checked your page source to get your theme and I had a copy of the theme on a testing site so I activated it and the events overview screen still appeared normal.
I think another plugin on your site is contributing to the issue that you are seeing or the update did not complete correctly.
Here is what I see on my end on a site that was upgraded last night to the latest WP:
http://cl.ly/1b221X3T0u13
Do you have a staging area available that you can pull in the live site for additional testing?
If not, could you schedule a brief window of a few minutes later today to try a manual re-install along with temporarily deactivating other plugins?
—
Lorenzo
|
|
Kevin G.
|
December 10, 2015 at 2:10 am
Yoast SEO was the problem.. after i disabled it the layout was corrected and the datepicker worked again..
Now only one problem left : 2. if i set ticket selector to “don’t show” in general settings, it still shows.
|
|
Tony
|
December 10, 2015 at 2:39 am
Are you using the latest version of Yoast?
Regarding the ticket selector, the option that you are changing is for the event list, not the single event. If you set that option to no we do not default the single event to no as that disables all of you new events registrations completely.
So is that option working as expected on the event lists but the ticket selector still shows on the single event?
|
|
Kevin G.
|
December 10, 2015 at 2:52 am
Yes i updated to Yoast 3.0.6
Yes i need to have the ticket selector disabled as default for every new single event.
|
|
Tony
|
December 10, 2015 at 4:52 am
Currently there’s no option within Event Espresso to do that.
I’ve created a ticket to discuss adding a filter hook to allow you to change the default value, currently you would need to manually change that setting when creating events.
|
|
Kevin G.
|
December 10, 2015 at 5:25 am
That’s weird, because it has always been “no” as default before the update.
An other question, if i download the .pdf invoice on the thank you page it uses the following adres: 123 Onna Road
PO Box 123
Inna City,Arizona
United States
12345
Where can i change that ? In general settings i already put our address..
|
|
Tony
|
December 10, 2015 at 5:42 am
That’s weird, because it has always been “no” as default before the update.
Hmm, I’ll double check with the developers but fairly certain this has always been Yes.
Did you make any customizations to force this perhaps?
here can i change that ? In general settings i already put our address..
Go to Event Espresso -> Payment Methods -> Invoice.
Check within the Payee fields, you should find address fields there. If that address is set there you can remove the values, save the settings and the Invoice will use the settings from General Settings.
|
|
Josh
|
June 16, 2016 at 1:34 pm
In Event Espresso 4.9.1, there is a new filter that allows for changing the default for the Show ticket selector option. You add the following code to your site to change the option to default to No:
add_filter( 'FHEE__EE_Model_Field_Base___construct_finalize___default_value', 'ee_change_ticket_selector_default', 10, 2 );
/**
* Changes the event's default value for displaying the ticket selector.
* @param mixed $default_value
* @param EE_Model_Field_Base $field_obj
*/
function ee_change_ticket_selector_default( $default_value, $field_obj ) {
if( $field_obj instanceof EE_Model_Field_Base
&& $field_obj->get_model_name() == 'Event'
&& $field_obj->get_name() == 'EVT_display_ticket_selector' ) {
return false;
}
return $default_value;
}
You can add the above to a functions plugin or into your WordPress theme’s functions.php file.
|
