Order of events in full calendar

[Anonymous]

Salutations;

Upgraded from the buggy version – and I’m finding that now this could be a fantastic plug-in. If I can get it to be what I know an events calendar should be – it should be SOP for every WordPress installation. Also I am finding the forum here a wealth of knowledge – but having found my particular problem. I don’t know if this is a bug or not – most likely just me missing one of those ‘ or ” but…

In my full calendar (http://sincity-247.com/e-guide/?page_id=3027) the events are out of time order – I have tried using a “$order=” in the short code calling the calendar – but no luck. The Events list (http://sincity-247.com/e-guide/?page_id=4409) is fine so I’m at a loss. Any suggestions?

Any suggestions?

[Franky]

Hi,

this is indeed a bug, but luckily with an easy fix: in dbem_calendar.php, search for the string “ORDER BY” and change it from

ORDER BY event_start_date

to

ORDER BY event_start_date ASC, event_start_time ASC

That should fix it.

[Anonymous]

Thanks for the quick reply – unfortunately, when I made the change – I received this error:

Parse error: syntax error, unexpected ‘”‘ in /home/lvtsg3/public_html/sincity-247/e-guide/wp-content/plugins/events-manager-extended/dbem_calendar.php on line 149

I couldn’t find the referenced syntax error – so I simply copied my back up copy of the dbem_calendar.php into the editor – but I am still receiving the error message. What did I do now?

– Mike

[Franky]

The line I told you to edit is on about line 264, no way near 149. Since you got the same error when copying your old one back, you probably made an error before changing what I told you so.

Get the 3.1.1 version from here:

http://plugins.svn.wordpress.org/events-manager-extended/tags/3.1.1/dbem_calendar.php

and change what I said.

[Anonymous]

Actually – my bad. I guess I was trying to edit the PHP code while it the plug in was still active. I deactivated the plugin, copied over the original code. Reactivated the plug in – and all was AOK. I then deactivated the plugin, made the change and then reactivated it – and the fix is fine.

Thanks again

– Mike

[Author]

Posts