mahara-contributors team mailing list archive

[François Marier <francois@xxxxxxxxxx>]

You latest idea does sound like it would work.

The one thing that worries me however, is that it would increase the
complexity of sending forum emails quite a bit and might lead to bugs
that are much harder to find/fix.

Going back to the problem we are trying to solve: the mismatch between a
user expecting to be able to edit something and then not being able to
edit that post because the deadline has passed. In other words:

1- the error message sucks (i.e. "Access denied" != "Deadline has passed")
2- there is no visibility as to how much time you have left because the message is sent out

Both of these things could be addressed without changing the email
delivery workflow. Is that anything else you think may need to be
addressed?

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/731990

Title:
  Forum post editing timeout issue

Status in Mahara ePortfolio:
  New

Bug description:
  We have postdelay forum config parameter that defines for how long it
  is allowed to edit the post after it has been submitted. Say it is set
  to 30 mins. When user decides to edit the post just before timeout,
  s/he will be allowed to do so, but submission might not be possible
  due to the timeout (Access denied error).

  What I suggest is to make possible to submit the post even if time is
  out (but editing was initiated before timeout).