** Changed in: mahara
Status: Fix Committed = Fix Released
--
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:
** Changed in: mahara
Status: Confirmed = Fix Committed
--
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:
I guess I was wondering whether I had missed anything in terms of
defining the problem we are trying to solve (as opposed to describing a
possible solution).
Cheers,
Francois
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
For the case when email notification workflow is not changed, there is
nothing else I can think about.
--
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
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
what's to prevent me from changing my session and editing the post hours after
it has been sent out via email
It will not let you to start editing if more than 30 minutes has passed from
the time when you opened edit window. But, I agree, email sending has not been
considered.
I had another
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
Maybe I'm missing something here, but by essentially moving the check
from the server to the client (i.e. in the session) then what's to
prevent me from changing my session and editing the post hours after it
has been sent out via email?
Or more simply clicking the edit link, leaving the browser
That's indeed a very annoying behaviour.
However, the solution sounds a bit complicated (and error prone). We'd
need to have a new timeout (how long somehow has to edit a post) and
keep track of when editing was started.
A few scenarios to consider:
- user clicks edit and submits the edited
9 matches
Mail list logo
