What version are you running, and on what server? There was a bug on 2.7.0-2.7.4, affecting Windows servers running php 5.2. This was resolved in 2.7.5.
It’s a CentoOS 6.5 Server running the most up to date plugin but is on 2.5.1 WordPress (I know it’s old)
it worked sometime in the past…. Not sure what/when changed
Ah, Event Organiser requires WordPress 3.3+. Its never been tested on earlier versions, and I’d really doubt it work at all on 2.5.1.
I’m not sure where my post went but it disappeared…
But I had said that it was actually “3.5.1” and not “2.5.1′ sorry
I thought it was weird that you’d managed to get as far as the saving the dates of an event before something broke on 2.5.1 :).
If you go to ...wp-admin/edit.php?post_type=event&page=debug you can download a ‘system information’ file. If you download that file and use this form to send it to me, that’ll help isolate the cause of the problem.
Thanks! It’s sent and just a FYI it wouldn’t take the md version even though it says it will… I renamed to .txt and it took it.
Thanks again!
Anything new on this? I’ve updated to the newest and it’s still an issue… Thanks
Hi Chris, I never got a reply to my e-mail, dated 16th May 2014.
The system information file didn’t throw up anything as a possible reason for the bug. As per the e-mail, if you can provide FTP and admin access then I’d be able to determine the problem, but so far I’ve not been able to replicate it.
Thanks, not sure what happened there.
The system is behind a VPN so I can’t give you that access…
I guess we’ll dive into the code more and see what we can find out.
Data from the user is collected in
Most of the code for editing the event details, including collecting the data can be found in event-organiser/event-organiser-edit.php.
That’s converted to a format that can be used by the API (eo_update_event()). See, in particular these lines: https://github.com/stephenharris/Event-Organiser/blob/2.8.2/event-organiser-edit.php#L389:L402 .
You should first check that the array $event_data is what you’d expect it to be. Then perhaps try to determine why (e.g. look in $_POST). It seems unlikely that the error is after that point. Though still possible, the API is unit tested which closes the net slightly and any bugs there would likely cause problems elsewhere (and for more people…).
Thanks for your help, I figured it out… Stupid Cron Control plugin was defining DOING_CRON always to true. Removed it and we’re good.
