Added to Technical TODO list (nlabmeta):
]]>The “category: XXX” label at the bottom of a page should probably not be displayed when the page is included into another page. For instance, this is relevant to pages with
category:svg
.
Added to Technical TODO list (nlabmeta)
]]>When announcing an anonymous edit at the nForum, maybe the user’s IP address should be included, to make it easy to see at a glance that two such edits are probably the same person.
Have done a little bookkeeping at Technical TODO list (nlabmeta), so that it should be up to date now.
]]>Tweaked the dashboard entry at Technical TODO list (nlabmeta).
]]>A major pain with editing large entries with many automatically numbered items occurs when one accidentally duplicates an anchor label: This breaks the automatic numbering subordinate to section numbers, as it falls back to linear numbering (hence some Prop. 3.41 will now be referred to as Prop. 272, or the like).
This is of course trivial to fix, but only IF one knows which label got accidentally duplicated. With enough !includes, knowing this is non-trivial.
But I suspect the duplicated label will be reported somewhere in the logs!? Hence my request for the ToDo list:
Let anchor label duplication errors be read out from the logs and announced as error messages (similar to how duplicate redirects are already being reported as error messages).
]]>I have added to item 1 (make large pages load less sluggishly) a comment on what the issue here is, paraphrasing what Richard had explained somewhere:
]]>(Apparently the actual issue here is that large pages are currently not being cached, since the agent that requests the page in order to store it times out before it receives the page. So the fix ought to consist simply in increasing the timeout threshold for the caching agent.)
Great, thanks!
]]>Hehe, feel fee to make a wiki page :-). Maybe it would be a bit strange to have it on the nLab itself, but I don’t mind.
Very good that you are adding things here. I am still very busy and do not have time to look into things, so it is very useful to have a list for me to come back to later. I try to check most nForum posts, but there has been quite a bit of activity recently and I am not checking everything, so it is excellent to record here anything that people want action taking towards, with a link to relevant discussion, as you are doing.
]]>Another:
You know, it occurs to me that a better place to maintain a to-do list than a discussion thread would be, perhaps… a wiki page? (-:O
]]>Another:
New item:
A couple of further items for the TODO list.
]]>The precise error message in #9 is
]]>Some problems were encountered
There was a problem authenticating your post information.
Re #9 and #10: noted! Re #10: whether or not it is intended, it seems a bit weird, so I can look into changing it unless someone objects!
]]>Something I’ve been meaning to ask about for a while: it seems I only get email notifications of new comments on nForum threads I’m following when I’m actively logged in to the nForum site. Is this intended behaviour?
]]>Something else to put on the to-do list: the nForum has a weird bug whereby it sometimes refuses to post a comment, saying it was unable to authenticate. Generally just clicking the “post” button again makes it work, but this is a little annoying (and may be more offputting for new users who aren’t familiar with it).
]]>Re #6: Removing the checkbox does prevent the possibility of indicating one’s edit without making any comments. But nobody seems to use this, and maybe we would like to enforce making a comment anyway, so this may be for the best. Otherwise I cannot think of any objection; if nobody raises an objection reasonably soon, I’ll implement it.
]]>Just adding a couple more items to the TODO list (see here for the discussion which has led to this).
1) Remove use of form-spam-protection plugin from all pages.
2) Improve design of file upload/deletion, etc. E.g. after one has uploaded a pdf, one should get a link to it, without needing to change syntax. The design seems a bit clunky and unintuitive at the moment.
]]>I would suggest #3; does anyone have an argument for a different behavior?
]]>Re #2: Thanks for the suggestion! Definitely I should fix it, it is also part of what is needed for 3) in my list in #1.
Re #3 and #4:
Oh, I guess maybe we want to be able to describe trivial changes for the nLab history but not announce them at the forum?
Currently actually no description is logged if one does not tick to announce! Only that a trivial edit has been made, the time of it, page name, and author is logged. Happy to change it though, if people think it best. Equally happy to change as in #3 if preferred.
]]>Oh, I guess maybe we want to be able to describe trivial changes for the nLab history but not announce them at the forum?
]]>write my announcment text, but forget to click the checkbox, then again the announcement text is lost.
This makes me wonder whether the checkbox is really necessary at all. Could it just be replaced by nonemptiness of the textbox?
]]>Thanks again for all your work! It’s amazing.
Since you ask, I’ll point out one very minor issue:
When I am done with my edit cycle, and then go and write my announcement text, it is lost upon submitting if I did not remember to make a last change to the entry, for instance by adding or removing a whitespace.
Similarly but complementarily, if I remember to make a last edit, then write my announcment text, but forget to click the checkbox, then again the announcement text is lost.
Clearly I can handle this myself. But if it is not too hard to make the software behave a little more forgivingly, it would be a convenience.
]]>