mahara-contributors team mailing list archive

[Ruslan Kabalin <731990@xxxxxxxxxxxxxxxxxx>]

As a possible solution, the edit time could be stored in the session
when editing is initiated and substituted instead of $post->ctime on the
edit submission. This will allow to submit the last post edit within
"postdelay" value (e.g. 30 mins) since edit button was clicked. The
patch below implements it. It also ensures that there is no mangling
with stored edit time (e.g. by starting editing other post while post
edit window is open to amend the time for the first post) as the
post/topic id is also stored. It only allows editing one post/topic at
the time at the moment.


** Patch added: "0001-forum-Introduce-per-post-edit-timeout-bug-731990.patch"
   https://bugs.launchpad.net/mahara/+bug/731990/+attachment/1898356/+files/0001-forum-Introduce-per-post-edit-timeout-bug-731990.patch

-- 
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).