Events Made Easy › Forums › Bug fixed or feature request implemented › Events with same date disappear on 4.0 upgrade, reappear on downgrade to 3.3.5
- This topic has 7 replies, 3 voices, and was last updated 13 years, 3 months ago by Anonymous.
-
AuthorPosts
-
Fri 26 Aug 2011 at 19:24 #43440AnonymousInactive
Wordpress 3.1.3 (cannot upgrade to 3.2 until host upgrades PHP, which is currently at 5.1.6)
EME 4.0 and events database updated
When I upgraded EME to 4.0, all but one of events which had the same date disappeared (i.e. only one event scheduled for Aug 26 showed up). This is true of the WordPress Dashboard EME Edit panel, and of the events display on the website. The mysql database still held onto the entries. Fortunately, downgrading EME to 3.3.5 resolved the problem, but I’m not sure what incompatibilities might arise from the events database update that came with 4.0. (Very regretful that I didn’t make a database backup previous to updating EME, sorry)
Can you look into compatibility with WordPress 3.1?
Fri 26 Aug 2011 at 19:54 #48381FrankyKeymasterThe plugin works with 3.1, but in eme 4.0 future events no longer include events of today. Look at the show_ongoing option for [events_list]for that.
Fri 26 Aug 2011 at 20:04 #48382AnonymousInactiveThanks, I’ll give it another go.
Fri 26 Aug 2011 at 20:17 #48383AnonymousInactiveHow is this handled in the widget?
Fri 26 Aug 2011 at 20:18 #48384FrankyKeymasterI think the doc is wrong there: show_ongoing is 0 by default I think (need to check when I get home)
Fri 26 Aug 2011 at 23:11 #48385FrankyKeymasterOk, fixed in trunk: scope=future once again shows events of today as well. I’ll release by the end of the weekend again.
New scope=nottoday–future allows you to specify events really in the future.
Also you can now specify any scope in the widget (no longer a dropdown).
For the future scope: I’ll release by the end of the weekend. For now, change this in eme_events.php:
(the event_start_date and event_end_date comparisons changed):
if ($scope == "future") {
//$conditions [] = " ((event_start_date = '$today' AND event_start_time >= '$this_time') OR (event_start_date > '$today') OR (event_end_date > '$today' AND event_end_date != '0000-00-00' AND event_end_date IS NOT NULL) OR (event_end_date = '$today' AND event_end_time >= '$this_time'))";
// not taking the hour into account until we can enter timezone info as well
if ($show_ongoing)
$conditions [] = " (event_start_date > '$today' OR (event_end_date > '$today' AND event_end_date != '0000-00-00' AND event_end_date IS NOT NULL))";
else
$conditions [] = " (event_start_date > '$today')";
}to
if ($scope == "future") {
//$conditions [] = " ((event_start_date = '$today' AND event_start_time >= '$this_time') OR (event_start_date > '$today') OR (event_end_date > '$today' AND event_end_date != '0000-00-00' AND event_end_date IS NOT NULL) OR (event_end_date = '$today' AND event_end_time >= '$this_time'))";
// not taking the hour into account until we can enter timezone info as well
if ($show_ongoing)
$conditions [] = " (event_start_date >= '$today' OR (event_end_date >= '$today' AND event_end_date != '0000-00-00' AND event_end_date IS NOT NULL))";
else
$conditions [] = " (event_start_date >= '$today')";
}Sat 27 Aug 2011 at 04:11 #48386AnonymousInactiveGreat, thanks for the quick attention to this matter!
Sat 27 Aug 2011 at 11:13 #48387AnonymousInactiveditto
-
AuthorPosts
- The forum ‘Bug fixed or feature request implemented’ is closed to new topics and replies.