A discussion is taking place about a potential delay in Discourse TL4 “Make Wiki” functionality. anon25879736 noticed that TL4 users cannot convert a post into a wiki until it is at least 5 minutes old, with no apparent setting to change this timeframe. cpradio speculated that this delay might be related to the “Grace Period” for editing posts, but anon21958287 and PJH clarified that this period is only about a minute (54 seconds, to be exact). anon25879736 further noted that this issue only affects TL4 users, as staff users can make posts of any age into wikis. Fortunately, eviltrout has since fixed this issue with a commit to the Discourse GitHub repository, as confirmed by sam.
It seems that TL4 users are unable to convert a post into a wiki until that post is at least 5 minutes old. Based on feedback from the admin at my primary forum (@PJH) there does not appear to be any settings to change this timeframe.
My guess is it relates to the “Grace Period” posts have for editing. Not sure why it prevents the Wiki setting though…
The “Grace Period” (ninja period, in the vernacular) is only about a minute where this has been observed.
Ah, well then, that rules out that possibility 
54 seconds. For some reason…
[postgres@sofa ~]$ psql -d discourse -c "select uh.updated_at, username, previous_value, new_value
from user_histories uh
join users u on u.id=acting_user_id
where subject='ninja_edit_window'
order by uh.updated_at asc;"
updated_at | username | previous_value | new_value
----------------------------+----------+----------------+-----------
2014-06-25 15:56:02.054118 | dhromed | 300 | 60
2014-07-15 16:05:28.750162 | PJH | 60 | 300
2014-07-15 16:05:33.381305 | PJH | 300 | 60
2014-10-29 00:50:43.081509 | system | 60 | 54
(4 rows)
[postgres@sofa ~]$
It should also be noted that this only affects TL4 users. Staff users are able to make posts of any age into wikis.
This was a bug, which I have fixed in this commit:
https://github.com/discourse/discourse/commit/f15b0d205f62dad5ffc468cded650677497be148
As always, thanks for letting me know about it!
I think @eviltrout just fixed this