| /plugin/scrape/HTMLPurifier/ConfigSchema/schema/ |
| H A D | Core.MaintainLineNumbers.txt | |
| H A D | Attr.AllowedFrameTargets.txt | |
| H A D | CSS.MaxImgLength.txt | |
| /plugin/elwikiupgrade/lang/en/ |
| H A D | step0.txt | 1 …ur wiki to the newest available DokuWiki version. Before continuing, you should read the [[doku>ch…
|
| /plugin/findologicxmlexport/vendor/twig/twig/doc/tags/ |
| H A D | verbatim.rst | 7 The ``verbatim`` tag marks sections as being raw text that should not be
|
| /plugin/webcode/_test/data/pages/ |
| H A D | two.txt | 13 * The below snippet should show only one emoji and not the above emoji
|
| /plugin/findologicxmlexport/vendor/phpunit/php-token-stream/ |
| H A D | README.md | 11 …ing development, for instance to run your project's test suite, then you should add it as a develo…
|
| /plugin/orgapp/ |
| H A D | README.md | 15 … to include the definition within the tag orgapp, in the second case you should use the attribute …
|
| /plugin/elasticsearch/lang/en/ |
| H A D | confmanager_description.txt | 5 Define parsers for each file extension that should be processed. Use ''%in%'' to specify the input file for CLI tools. Web services must accept the input file as POST data.
|
| /plugin/upgrade/lang/en/ |
| H A D | step0.txt | 1 This plugin will automatically upgrade your wiki to the newest available DokuWiki version. Before continuing, you should read the [[doku>changes|Changelog]] to check if there are any additional steps for you to perform before or after upgrading.
|
| /plugin/bibtex/OSBib/format/ |
| H A D | README.txt | 59 …should use STYLEMAPBIBTEX.php instead as this has been specially devised to offer an out-of-the-bo…
61 1/ You should edit $this->types.
62 2/ You should edit each resource type's array changing ONLY the key of each element. However, do N…
74 …-encoded strings with functions such as strtolower(), strlen() etc., you should strongly consider …
115 …-encoded strings with functions such as strtolower(), strlen() etc., you should strongly consider …
122 …ur database stores or accesses its data in a form similar to BibTeX, you should set the constructo…
143 The following should be called for each database row you wish to process.
156 This method should be called for each type of creator the resource has. (See BIBSTYLE.php for an e…
172 …hic system allows users to specify a groups of letters in the title that should not be lowercased …
|
| /plugin/findologicxmlexport/vendor/symfony/yaml/Tests/Fixtures/ |
| H A D | YtsErrorTests.yml | 19 # This is actually valid YAML now. Someone should tell showell.
|
| /plugin/supa/ |
| H A D | changelog.txt | 11 Support google chrome browser (should also fix Apple Mac clients)
|
| /plugin/flexpaper/ |
| H A D | README.md | 14 These files path should be:
|
| /plugin/findologicxmlexport/vendor/phpunit/phpunit/tests/Regression/GitHub/ |
| H A D | 244.phpt | 2 GH-244: Expected Exception should support string codes
|
| /plugin/math2/phpmathpublisher/ |
| H A D | CHANGELOG | 3 - WARNING : the $dirfonts and $dirimg parameters should not be finished any more by /.
|
| /plugin/abc/ |
| H A D | style.css | 29 /* if you allow midi files per mime(.local).conf, you should comment the follow lines out
|
| /plugin/epub/lang/en/ |
| H A D | remove.txt | 2 When you are finished with this book, however, you should remove its id from the list of book creat…
|
| /plugin/geonav/tpl/startermap/ |
| H A D | style.ini | 7 ; Please don't forget to copy the section your changes should be under
11 ; defines for which output media the style should be loaded. Currently
|
| /plugin/matomo/ |
| H A D | README.md | 54 …- Matomo plugin should now be enabled and you should see the trackingcode in the rendered html on …
|
| /plugin/acronym/ |
| H A D | README | 33 2010-08-20: 1 hour: preblock and codeblock should start on the same column
35 2010-07-22: 5 hours: preformatted text should work with SUSE and Ubuntu. Solution is simple: AddEnt…
|
| /plugin/deletepagebutton/ |
| H A D | README.md | 49 and should work with later versions as well.
59 Other Templates should work as well, as long as they use the same markup for
|
| /plugin/bibtex4dw/ |
| H A D | TODO.md | 3 Things that need to/should be done, as of May 2023
8 The code is not in very good shape and should be refactored and properly documented.
|
| /plugin/aichat/vendor/erusev/parsedown/ |
| H A D | README.md | 51 In both cases you should strongly consider employing defence-in-depth measures, like [deploying a Content-Security-Policy](https://scotthelme.co.uk/content-security-policy-an-introduction/) (a browser security feature) so that your page is likely to be safe even if an attacker finds a vulnerability in one of the first lines of defence above.
55 Safe mode does not necessarily yield safe results when using extensions to Parsedown. Extensions should be evaluated on their own to determine their specific safety against XSS.
78 It passes most of the CommonMark tests. Most of the tests that don't pass deal with cases that are quite uncommon. Still, as CommonMark matures, compliance should improve.
|
| /plugin/userimportextended/lang/en/ |
| H A D | intro.txt | 4 The CSV fields should be separated by commas (,) and strings delimited by quotation marks (%%""%%).…
|