Closing time is now going up

OH! I think you'll need your cron job to be setup.

run: rake loomio:close_lapsed_motions within your loomio environment and it will close all the proposals for you.

thanks. I will try that. I did setup cron jobs but mayeb they didnt take thanks

It is probably good to have a fallback when the cron jobs have not run. looks odd to see the time increasing. :)

How do you imagine that working, Adam?

Not a ruby developer sorry. But have worked many years in IT as a PHP programmer and more recently meteorjs. In any case the time remaining is obviously being calculated in some way - this in itself is flawed as it is now counting the time when the proposal should've closed.
I would think that it should be relatively simple to close the proposal when it is found that the proposal is still open and the time left is less than 0.

That's fine, I just want to ask what you think should happen.

Closing a proposal late is actually pretty bad, in terms of Loomio doing what it promised to do. I wonder if Loomio can tell you when you've finished setup or something.

I guess for loomio to know that everything is setup correctly including cron would be to actually have a cronjob that specifically checks everything else.. unfortuantely that job would have to be set to run every minute. However it could look for an ENV variable that it sets when it confirms everything is setup.. if the variable is there then no more checks needed which means little load on the server.

Yea. I think it would need to be a database thing. A table that contains logs of cronjobs being run or something. If the table is empty assume that cronjobs have not been setup.

Still seems a bit over the top to me.. I think a documentation checklist, and improvements to the wiki/docs would be more effective.