|
Oska Studio
|
December 5, 2013 at 10:42 pm
Hi everyone
We just purchased the Business version with all the plugins and we’ve discovered some major issues with the date selector in the admin. It seems for any date we pick whether it’s registration open date, event start or end date etc, the value that is saved in the form is truncated somehow and we end up with strange values like “30th January 201”. We’ve also saved some new evens with today’s date and ended up with a 1900s date or with the year missing the last 2 digits. It’s not consistent either and i’ve tested in Chrome, Safari and the Firefox (all latest versions) and the behaviour is consistent.
Software:
Event Espresso – 3.1.36.1.P
Wordpress: Version 3.7.1
Website: (see footer widgets of latest events for date issues)
http://kjross.tuskagency.com/training/training-courses/
This is a major issues obviously for a plugin based around dates so I’m hoping it’s just a recent issue in the latest version and can be fixed quickly.
Cheers
Phil
|
|
Dean
|
December 6, 2013 at 3:40 am
Hi Phil,
We haven’t come across this before, could you please advise what your WordPress date settings are from the Settings > General page?
We also recommend that the timezone be set to the closest city rather than a UTC setting.
|
|
Oska Studio
|
December 8, 2013 at 3:38 pm
Hi Dean,
Thanks for the reply. This is definitely a really strange issue and very frustrating as we need to release the site live this week and the most important part of the plugin doesn’t appear to function properly. I’ve uploaded some screenshots of the WordPress date/time settings which are specifically set to Brisbane, Australia, and also the Event Espresso event form which shows how the dates are being truncated as well.
Wordpress Date/Time Setting:
http://img32.imageshack.us/img32/7241/quba.png
Event Espresso Dates Inputs:
http://img534.imageshack.us/img534/1856/6qzt.png
Cheers
Phil
|
|
Oska Studio
|
December 8, 2013 at 4:54 pm
Also another screengrab that i think shows the problem best.
http://img826.imageshack.us/img826/5761/r774.png
No matter what date I select when i save click on the Calendar and inspect the form element the value is still truncated causing an incorrect year and subsequent date save. Settings for Dates/Timezones are all correct and working, and I initially thought it was related to the JQuery UI Date picker but when i manually use web inspector to change the date input values to say “December 12, 2013” and save the event, it will still turn up truncated and corrupted after saving.
|
|
Tony
|
December 9, 2013 at 4:07 am
Hi Phil,
The expected date output would be YYYY-MM-DD (http://d.pr/i/YkKT). It looks like something is changing the output of the date picker. To test can you manually alter the dates on a problem event to match the format above and confirm if that event is then fixed?
Have you modified the date output yourself? It could be done through a plugin or even the theme. Anywhere else on the site use a date-picker if so how/where?
You could try a full troubleshoot, disable all plugins apart from EE ones, reload the edit event page, check date output. If fixed enable each plugin individually, reload the edit event page and check the date output. If still the same, temporarily switch to the 2012/2013 theme. Check the date output.
Basically we need to find what is altering the date output and then we can look into it further.
|
|
Oska Studio
|
December 9, 2013 at 11:31 pm
Hi Tony,
I had thought initially the date format was coming from the WordPress settings, but i deactivated the theme completely back to 2013 theme and the dates saved in correct format.
The Theme being used is: http://themeforest.net/item/minimum-professional-wordpress-theme/4084338
Not quite sure where this would be overriding the date in this fashion or whether this is a change that can be handled in the Event Espresso core code as it seems risky to rely on themes to behave when it comes to the Date format given date management is the core of an event plugin.
Cheers
Phil
|
|
Josh
|
December 10, 2013 at 8:56 am
Hi Phil,
While it may seem risky, it’s a rather impossible task to prevent a theme from loading its scripts on every admin page load. We’d have to know ahead of time what it uses as a handle for any potentially conflicting scripts, and programmatically remove them from Event Espresso’s pages.
It’s not that difficult for a theme to be developed so that it only loads it scripts on its admin pages, but until ThemeForest starts enforcing its new standards, this is the reality we are all left to deal with.
I’ve run into this once before with another ThemeForest theme and will look for the thread where we came up with a solution.
|
|
Josh
|
December 10, 2013 at 8:58 am
This is the one I was thinking of:
https://eventespresso.com/topic/nothing-works-as-it-should/#post-52744
Can you try the solution that was posted in that topic?
|
