Inaccuracy in Docs:Manual

[moioci]

"You cannot create or edit notes which start with Docs:, Special: or New:."
Special:Header, Special:Footer, Special:SetStyleSheet, and Special:Badge are user-editable.

[ACGarland]

I'm seeing a problem now trying to edit special pages. For one thing, some of them don't show up when I search on "Special:". For another, when I locate them by using links from the manual, and then edit them, when I go to save the page, it says, "'Special:Header' is not a valid page name. A page cannot have the prefix Docs:, Special;, New: or File:'

Have I missed something? These pages used to be editable on my device -- or so I thought -- but now their content is blank and I can't restore what they used to contain?

[mgkennard]

I've tried this on my personal Trunk Notes installation and on an out of the box installation, however I've been unable to reproduce your problem.

Special:Header, Special:Footer and Special:Badge are installed by Trunk Notes when first run, it should then allow those to be edited. You cannot however add Special: pages yourself. The Special:SetStyleSheet is created when you turn on custom stylesheets in the Settings.

If, when viewing pages, you tap in the search bar at the top you should be able to start typing in Special and see the Special:Header, etc pages. If not then something has gone wrong.

One thing to try is creating the files Special:Header, Special:Footer and Special:Badge on your computer, zipping them up and then uploading to Trunk Notes. If you cannot create those files because you are using Windows (which has a large number of special characters it doesn't like in filenames) then create each file without the : but include on the first line of the file the text "Title: Special:Header", etc

Matthew
Apps On The Move

[ACGarland]

Thanks for the suggestions.

The special files did exist on the device -- but had become empty for whatever reason. (I had a custom header and style sheet.) I tried restoring them from a backup but they still were uneditable on the device. I finally did a backup, uninstalled, reinstalled, and a restore -- after which point they were once again editable as they are supposed to be. So for now I'm over the glitch.