Home › Forums › Calendar Products › Events Calendar PRO › Warning: strtotime() expects parameter 1 to be string, object given in
- This topic has 31 replies, 4 voices, and was last updated 8 years, 2 months ago by Support Droid.
-
AuthorPosts
-
December 7, 2015 at 8:56 am #1036967GeorgeParticipant
Hey Matt,
Thanks for sitting tight over the weekend, I was hoping to check in on this thread over the weekend but ended up not being in town 🙁
I really appreciate your patience here and the system information you’ve provided thus far. I’ve unfortunately boiled things down to two options from here in terms of what next steps we can take.
The first option would be for you to hold up on any further testing and such, and sit tight while we work on numerous bug fixes after the 4.0 release and hope that our next maintenance release addresses these problems. What I mean by that is that I cannot recreate your specific issues yet exactly as they are manifesting for you, and so we don’t have a specific bug ticket for these bugs yet.
But we DO have two bug tickets related to stock issues with WooCommerce, and both bugs are being actively worked on. I am not sure if these fixes will address your specific problems because, as noted, your problems are manifesting in a way I cannot reproduce exactly. But the bugfixes we’re working on could help with your issues, too.
—
The other option here, instead of just sitting tight waiting for the next release, is for you to do a bit more research on this. I hate to ask that after all the efforts so far here; but basically, the process would be to use the “testing for conflicts” steps outlined in this article here → https://theeventscalendar.com/knowledgebase/testing-for-conflicts/
Then, after EACH step there, try to recreate the exact problems you’ve described in this thread.
The process sounds tedious, and it is a little bit – although it tends to be much faster than you might expect. But the value of these steps is that, for example, if you deactivate a plugin and then try things out and suddenly the behavior is even a little bit different, then we now have evidence that there’s a code conflict factoring into these issues and that would be very helpful!
—
It’s your call, Matt – if you want to keep doing some doing here with the steps I recommended above, it may be fruitful. But it also might not be 🙁 And so if you’d rather just hold off on further researching and such for now, then I can at least promise you that we are working on a number of other semi-related bugfixes for our Ticketing plugins (and for The Events Calendar and Events Calendar Pro themselves, too).
I hope this all makes sense – let me know if so, and what you think about going forward with this issue. Your patience means a lot and I’m genuinely sorry for all of the trouble here.
Sincerely,
GeorgeDecember 11, 2015 at 12:46 am #1039347mattconradParticipantHi George,
Thanks for getting back to me. I noticed that there were updates to the events plugins last night and I have upgraded them so I am now on the events calendar 4.0.1.
All the issues still persist unfortunately. I’m assuming as the tickets plugin didn’t have an update, that the release is still being worked on for the stick issues.
Regarding testing for conflicts, I have gone through that list and done the processes a couple of times now without any joy unfortunately.
Apart from waiting for further releases, I’m not sure what else I can do?
Kind regards,
Matt
December 11, 2015 at 10:38 am #1039730GeorgeParticipantI really appreciate your patience Matt!
Can you share your ‘system information’ one more time here, now that some things are updated and what not? I will try again to recreate this problem; once I can do that, we should at least be able to try and work backwards and figure out the problem…
I’m really sorry for all of this Matt! Thank you for the continued patience and cooperation.
Sincerely,
GeorgeDecember 12, 2015 at 2:40 am #1039993mattconradParticipantHi George,
Sure, my system information is as follows:
URL
INSTALL KEYS
events-calendar-pro = f9484552f09aacc24e979e476b7d1a0f518020db
tribe-wootickets = 69fa76a87fac8d71ed265100142eb0e89bdd9b35
WORDPRESS VERSION
4.4
PHP VERSION
5.4.45
PLUGINS
Gravity Forms version 1.9.15 by rocketgenius(http://www.rocketgenius.com)
Advanced Custom Fields Pro version 5.3.0 by elliot condon(http://www.elliotcondon.com/)
Advanced Custom Fields version 4.4.4 by Elliot Condon(http://www.elliotcondon.com/)
Akismet version 3.1.5 by Automattic(http://automattic.com/wordpress-plugins/)
All In One SEO Pack version 2.2.7.4 by Michael Torbert(http://michaeltorbert.com)
The Events Calendar PRO version 4.0.1 by Modern Tribe, Inc.(http://m.tri.be/20)
Fold Page List version 1.9 by Rob Schumann(http://www.webspaceworks.com/)
Gravity Forms MailChimp Add-On version 3.7.1 by rocketgenius(http://www.rocketgenius.com)
myFancybox version 1.0 beta by m.r.d.a
Page-list version 5.1 by webvitaly(http://web-profile.com.ua/wordpress/plugins/)
Quick Page/Post Redirect Plugin version 5.1.5 by Don Fischer(http://www.fischercreativemedia.com/)
Srizon Facebook Album Pro version 3.1.1 by Afzal(http://www.srizon.com/contact)
The Events Calendar version 4.0.1 by Modern Tribe, Inc.(http://m.tri.be/1x)
WooCommerce Checkout Field Editor version 1.4.10 by WooThemes(http://woothemes.com)
WooCommerce SagePay Form and SagePay Direct Gateway version 3.1.7 by Add On Enterprises (Andrew Benbow)(http://www.addonenterprises.com)
WooCommerce MailChimp version 1.3.6 by Adam Anderly(http://anderly.com)
WooCommerce version 2.4.12 by WooThemes(http://woothemes.com)
WooThemes Helper version 1.5.9 by WooThemes(http://woothemes.com/)
The Events Calendar: WooCommerce Tickets version 3.12.1 by Modern Tribe, Inc.(http://m.tri.be/28)
Wordfence Security version 6.0.22 by Wordfence(http://www.wordfence.com/)
WordPress Importer version 0.6.1 by wordpressdotorg(http://wordpress.org/)
Acunetix WP Security version 4.0.5 by Acunetix(http://www.acunetix.com/)
NETWORK PLUGINS
–
MU PLUGINS
–
THEME
Orange Rooms
MULTISITE
–
SETTINGS
tribeEnableViews = Array
(
[0] => list
)
schema-version = 4.0.1
recurring_events_are_hidden = exposed
previous_ecp_versions = Array
(
[0] => 0
[1] => 3.11.2
[2] => 3.12
[3] => 3.12.1
[4] => 3.12.2
[5] => 3.12.3
[6] => 3.12.6
[7] => 4.0
)
latest_ecp_version = 4.0.1
last-update-message = 3.11.2
donate-link =
postsPerPage = 999
liveFiltersUpdate =
showComments =
showEventsInMainLoop =
eventsSlug = events
singleEventSlug = event
multiDayCutoff = 02:00
defaultCurrencySymbol = £
reverseCurrencyPosition =
embedGoogleMaps =
embedGoogleMapsZoom = 10
debugEvents =
disable_metabox_custom_fields = show
pro-schema-version = 4.0.1
stylesheetOption = skeleton
tribeEventsTemplate = page-events.php
viewOption = list
tribeDisableTribeBar = 1
hideLocationSearch = 1
hideRelatedEvents = 1
week_view_hide_weekends =
monthEventAmount = 999
enable_month_view_cache =
dateWithYearFormat = l d F Y
dateWithoutYearFormat = l d F Y
monthAndYearFormat = F Y
weekDayFormat = l d F
dateTimeSeparator = from
timeRangeSeparator = to
datepickerFormat = 3
tribeEventsBeforeHTML =
tribeEventsAfterHTML =
hideSubsequentRecurrencesDefault =
userToggleSubsequentRecurrences =
recurrenceMaxMonthsBefore = 24
recurrenceMaxMonthsAfter = 24
geoloc_default_geofence = 25
geoloc_default_unit = miles
earliest_date = 2015-11-30 02:00:00
latest_date = 2016-02-27 01:59:59
custom-fields = Array
(
)
custom-fields-max-index = 4
tribe_events_timezone_mode = event
tribe_events_timezones_show_zone =
WORDPRESS TIMEZONE
Europe/London
SERVER TIMEZONE
UTC
COMMON LIBRARY DIR
/home2/orange/public_html/wp-content/plugins/the-events-calendar/common/src/Tribe
COMMON LIBRARY VERSION
4.0.1If you need anything further, do let me know.
Kind regards,
Mat
December 12, 2015 at 11:12 am #1040246GeorgeParticipantThanks for this Matt, things look good for the most part and nothing stands out as immediately problematic.
With that being said, issues are still persisting according to your most recent report, and I’m sorry about that! The good news, hopefully, is that some stock-related bugs have indeed been identified within Event Tickets and Event Tickets Plus, and are being actively worked on now. Hopefully a set of bugfixes will be included in an update soon – if that is set to happen soon, I will post here as soon as I find out.
As for the original issue here, the error, I’m unfortunately going to have to keep digging 🙁 I will even try to rope in some developers here to see if they have any deeper insights.
I’m sorry that things are at somewhat of a stalemate, Matt – the stock issues are being worked on, and I’m still working on (and scratching my head about) the original error message reported here…
Just wanted to post here to update you on things and keep you in the loop – thank you so much for your patience and for all of the information you’ve been providing!
Sincerely,
GeorgeDecember 17, 2015 at 1:44 am #1042665mattconradParticipantHi George,
Thanks for this. I noticed that there were plugin updates last night so have done the update and there aren;t currently any changes to the issues which are still apparent.
Just so you know, the system status is now as follows:
URL
INSTALL KEYS
events-calendar-pro = f9484552f09aacc24e979e476b7d1a0f518020db
tribe-wootickets = 69fa76a87fac8d71ed265100142eb0e89bdd9b35
WORDPRESS VERSION
4.4
PHP VERSION
5.4.45
PLUGINS
Gravity Forms version 1.9.15 by rocketgenius(http://www.rocketgenius.com)
Advanced Custom Fields Pro version 5.3.0 by elliot condon(http://www.elliotcondon.com/)
Advanced Custom Fields version 4.4.4 by Elliot Condon(http://www.elliotcondon.com/)
Akismet version 3.1.6 by Automattic(http://automattic.com/wordpress-plugins/)
All In One SEO Pack version 2.2.7.5 by Michael Torbert(http://michaeltorbert.com)
The Events Calendar PRO version 4.0.2 by Modern Tribe, Inc.(http://m.tri.be/20)
Fold Page List version 1.9 by Rob Schumann(http://www.webspaceworks.com/)
Gravity Forms MailChimp Add-On version 3.7.1 by rocketgenius(http://www.rocketgenius.com)
myFancybox version 1.0 beta by m.r.d.a
Page-list version 5.1 by webvitaly(http://web-profile.com.ua/wordpress/plugins/)
Quick Page/Post Redirect Plugin version 5.1.5 by Don Fischer(http://www.fischercreativemedia.com/)
Srizon Facebook Album Pro version 3.1.1 by Afzal(http://www.srizon.com/contact)
The Events Calendar version 4.0.2 by Modern Tribe, Inc.(http://m.tri.be/1x)
WooCommerce Checkout Field Editor version 1.4.10 by WooThemes(http://woothemes.com)
WooCommerce SagePay Form and SagePay Direct Gateway version 3.1.8 by Add On Enterprises (Andrew Benbow)(http://www.addonenterprises.com)
WooCommerce MailChimp version 1.3.7 by Adam Anderly(http://anderly.com)
WooCommerce version 2.4.12 by WooThemes(http://woothemes.com)
WooThemes Helper version 1.5.9 by WooThemes(http://woothemes.com/)
The Events Calendar: WooCommerce Tickets version 3.12.1 by Modern Tribe, Inc.(http://m.tri.be/28)
Wordfence Security version 6.0.22 by Wordfence(http://www.wordfence.com/)
WordPress Importer version 0.6.1 by wordpressdotorg(http://wordpress.org/)
Acunetix WP Security version 4.0.5 by Acunetix(http://www.acunetix.com/)
NETWORK PLUGINS
–
MU PLUGINS
–
THEME
Orange Rooms
MULTISITE
–
SETTINGS
tribeEnableViews = Array
(
[0] => list
)
schema-version = 4.0.2
recurring_events_are_hidden = exposed
previous_ecp_versions = Array
(
[0] => 0
[1] => 3.11.2
[2] => 3.12
[3] => 3.12.1
[4] => 3.12.2
[5] => 3.12.3
[6] => 3.12.6
[7] => 4.0
[8] => 4.0.1
)
latest_ecp_version = 4.0.2
last-update-message = 3.11.2
donate-link =
postsPerPage = 999
liveFiltersUpdate =
showComments =
showEventsInMainLoop =
eventsSlug = events
singleEventSlug = event
multiDayCutoff = 02:00
defaultCurrencySymbol = £
reverseCurrencyPosition =
embedGoogleMaps =
embedGoogleMapsZoom = 10
debugEvents =
disable_metabox_custom_fields = show
pro-schema-version = 4.0.2
stylesheetOption = skeleton
tribeEventsTemplate = page-events.php
viewOption = list
tribeDisableTribeBar = 1
hideLocationSearch = 1
hideRelatedEvents = 1
week_view_hide_weekends =
monthEventAmount = 999
enable_month_view_cache =
dateWithYearFormat = l d F Y
dateWithoutYearFormat = l d F Y
monthAndYearFormat = F Y
weekDayFormat = l d F
dateTimeSeparator = from
timeRangeSeparator = to
datepickerFormat = 3
tribeEventsBeforeHTML =
tribeEventsAfterHTML =
hideSubsequentRecurrencesDefault =
userToggleSubsequentRecurrences =
recurrenceMaxMonthsBefore = 24
recurrenceMaxMonthsAfter = 24
geoloc_default_geofence = 25
geoloc_default_unit = miles
earliest_date = 2015-11-30 02:00:00
latest_date = 2016-02-27 01:59:59
custom-fields = Array
(
)
custom-fields-max-index = 4
tribe_events_timezone_mode = event
tribe_events_timezones_show_zone =
WORDPRESS TIMEZONE
Europe/London
SERVER TIMEZONE
UTC
COMMON LIBRARY DIR
/home2/orange/public_html/wp-content/plugins/the-events-calendar/common/src/Tribe
COMMON LIBRARY VERSION
4.0.2Kind regards,
Matt
December 17, 2015 at 9:31 am #1043021GeorgeParticipantThanks for this Matt!
Stay tuned here, I am still unable to get this error, but as soon as I can do that we can start fixing it from there…
Thank you SO MUCH for your continued patience here! Seriously! 😀
— George
January 12, 2016 at 1:05 pm #1054824RexParticipantI am also experiencing the same problem.
This error does not display on my local development site, but does appear on two instances of the site posted on two different servers.
The error may be seen here:
and here:
http://053.f42.myftpupload.comAny help would be greatly appreciated.
Thanks!
January 12, 2016 at 1:06 pm #1054827GeorgeParticipantHey Rex,
This thread is very old and so I will actually close this thread for now.
Please post your problem in a new thread, and include your “system information” when doing so. You can see how to include system information here → https://theeventscalendar.com/knowledgebase/sharing-sys-info/
Thank you,
GeorgeJanuary 12, 2016 at 11:55 pm #1054996mattconradParticipantHi George,
Please don’t close this thread – it’s old because no one there has been able to identify the issue, when there clearly is one as I’m not the only one experiencing it, so please don’t close it. Are you able to take look through mine and Rex’s comments and help with a solution?
Kind regards,
Matt
January 13, 2016 at 10:51 am #1055455GeorgeParticipantHey Matt,
I understand your points completely and am sorry to have raised the alarm by mentioning closing this thread.
The problem is that, at this time, we still are not recreating your issue. Rex has reported the issue too, but if you see how much information we went through in regards to your own site, my main goal of moving Rex to another thread was just to keep things organized as I request system information and such for this THREE websites.
I have indeed looked through your comments above in this whole thread to try and arrive at a solution, but there is unfortunately just not a solution at this time 🙁 I am very sorry about this! It’s a bug we are not able to recreate yet but are still trying to.
Leaving this thread open does not move us forward on finding the bug, but I will leave it open for a bit to hear more from you about my comments here. Closing the thread will help us keep track of each individual’s own complaints – if you’re concerned about being notified of a bug fix, there are two places we publish bug fixes when they arrive:
• The changelogs of updates when they arrive in your wp-admin dashboard.
• Release notes on http://theeventscalendar.com/blog
Please let me know what you think here, Matt – sorry to have raised the alarm about my comments about closing this thread!
—
@Rex, regardless of the state of this current thread, can you still post your issues in a separate, new thread as described in my last post?Thank you both for your cooperation and patience!
George
February 8, 2016 at 10:15 am #1069627RexParticipantAs requested, I have started a new thread here regarding this problem:
Thanks
February 8, 2016 at 11:18 am #1069664RexParticipantUPDATE
George was able to diagnose my particular problem here:
Matt, I hope this may help you as well.
February 8, 2016 at 1:20 pm #1069757February 9, 2016 at 12:43 am #1069954mattconradParticipantThanks @Rex – that did work and the error no longer appears so thank you for forwarding the link 🙂
@George – it has brought up a further issue. I’m using the following code to pull put the event from today, but for some reason it’s now showing the event from yesterday. Am I doing something wrong?<?php global $post; $events = tribe_get_events( array( 'posts_per_page' => 1, 'start_date' => current_time( 'Y-m-d' ) ) ); foreach ( $events as $post ) { setup_postdata( $post ); ?>
Does the date format above need to match the date format in the settings or would it be something else?
Thanks in advance.
Matt
-
AuthorPosts
- The topic ‘Warning: strtotime() expects parameter 1 to be string, object given in’ is closed to new replies.