• Do not
register here on develop.twiki.org, login with your twiki.org account.
• Use Item7848
for generic doc work
for TWiki-6.1.1. Use Item7851
for doc work on extensions
that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
• Does this site look broken?. Use the LitterTray web for test cases.
Item7714: PublishContrib bug fixes and enhancements 2016-01
Item Form Data
- it didn't work with a web housed in non-default disk in %SYSTEMWEB%.UsingMultipleDisks installation
- An HTTP response header kind of string is displayed on the result page
- PUBLISH_INSTANCE needs to be eliminated because it allows access to an arbitrary file on the server
- Both in inclusions and exclusions input fields
- "?" meant a character or nothing. It's supposed to mean a character period
- Spaces after a comma were not ignored. So "Abc, Def" meant "Abc" and " Def"
- enable/disable plugins is harmful in Fast CGI and mod_perl. So an option is needed to disable the feature
- inefficiency -- each published topic was read twice
- if access restriction is set by "Edit settings" rather than the topic text, that restriction is not observed
- If a css file has
url('data:...'), it was mis-recognized and an error occurs
A*,B* was specified as inclusions, it was translated into
^A.*|B.*$ rather than
^(A.*|B.*)$, which resulted in totally unexpected behavior
- Documentation improvements
- A TWiki admin may not want to provide some output formats. E.g. a PDF file generator may not be available. So there need to be ways to disable some formats.
- There was no way to put attachment list on a published page. There need to be a way while leaving the current behavior as default.
- You may want to set TWiki variables while publishing. For example, you probably want to disable tool bars having Edit, Attach, Raw view, etc on published topics. You can achieve that by setting
Set PUBLISHVAR_READONLYSKINMODE = 1
- Links to other topics may be written in absolute URLs, which is not a good practice but some do anyway. There might be URLs not matching the
TWiki::getScriptURL("view") value but still work. There need to be a way to specify such URLs in a regular expression.