berkeleypa

That was a great help, thanks!

Hi there,
It turns out our server configuration was messed up, and all admin links were pointing to http and not https, which was the cause of the problem. Not the plugin at all. Sorry for the false alarm, and thanks for your time.

Sorry, not a js error but an error in Firebug console. No plugins to enforce https, but configured on the server. Do you force admin access to SSL, or just login? We were having issues with another plugin when we forced all admin, so restricted it to login only, which was when we started getting these mixed content errors.

If anyone is interested I was able to fix this by replacing the following line of code in more-fields-object.php:

if (!current_user_can($capability)) continue;

with this:

$user = wp_get_current_user();
$userrole = $user->roles[0];
if (!in_array( $userrole, $box['more_access_cap'])) continue;

@daniel yes but this is the behavior that we are expecting, that when you drag a post from one date to another, the date of publication should change accordingly. Otherwise how does the new date come into play? It does seem to be saved somewhere in the database, but both post_date and post_date_gmt were sticking to the original date on which the post was created, which was causing the premature publishing problem.
Hope that’s clear. Thanks for your help!

Found the solution here: https://editflow.org/features/calendar/

ef_calendar_allow_ajax_to_set_timestamp (filter) – Whether or not dragging an unpublished post to a new date changes the publication timestamp for the post. This is off by default. You can enable it by placing the following in your theme’s functions.php file:

add_filter( ‘ef_calendar_allow_ajax_to_set_timestamp’, ‘__return_true’ );

Yes, you’re right mad283. Curious thing is on steps 3 and 4 above, the correct date is shown, but if you click OK (without changing the date) it still says “Publish immediately” instead of the date. It seems that dragging the post to a new date in the calendar should actually cause it display the date instead of “Publish immediately”, so therein lies the bug.

@cojennin: I can confirm your steps exactly. The problem lies in that when you click Schedule it then publishes right away. Does that happen for you?

Hi Daniel – did you find a workaround for this issue?

I think you’re onto something mad283. Our authors tend to use the calendar to drag and drop posts too. I just tried this with a test post created today – dragged it to 3 days in the future then in the editing screen clicked Schedule, and sure enough, it published! It’s like the post date is getting “stuck” on the date/time you create it when using the calendar to schedule.

Thanks for your reply. We have multiple authors and several have reported that when they create a new post, and come back to it later to edit, clicking the “Schedule” button causes it to publish immediately rather than schedule the time to publish. We do make use of custom statuses so often the post is left in one of those states. When this happened last I looked at the database and noticed that for that particular post the post_date_gmt was actually 5 days earlier than post_date, which I thought was very odd.

Our site is hosted by WP Engine, a managed WordPress hosting service. I do think it has to do with EditFlow, since it doesn’t happen with any of our other sites.

Do you have a suggestion as to how we implement those filters?

thanks!