PWP wiki processor

FAQ

TextRules . SimpleTextRules . Installation . Configuration
UserManual . FAQ . »find more online

 · How safe are the text translations?
 · My text got cut! I lost data!
 · What about cookies, sessions and user tracking?
 · Does PWP work with SSL proxys?
 · Can I rename run.php?
 · The shown Wiki page size is wrong!
 · What is the file Config.backup.inc for?
 · What about HTML tags ADDRESS, CODE, CITE, Q, etc?
 · Is the generated HTML in compliance to the W3C?
 · What about XHTML?
 · Is a wipe out attack possible on an open PWP?
 · What is the cache for?

How safe are the text translations?

Translation will work well on ordinary text. Problems might arise if you have tricky text, e.g. with formulas in it - I cannot test every constellation of characters. In most cases you will be able to use a different formatting rule. Maybe you can replace '' by / or vice versa? This is especially necessary when you want to format an hyperlink italic; the :// will interfer with the '/' italic syntax. And stuff like C++ should be made fat by using the ''' syntax.

Just tell me if there are several things not working as expected!

My text got cut! I lost data!

You have probably allowed HTML tags defined in your config file:

$this->mProp['AllowedTags'] = '<b><i>';
and somewhere in your text are character combinations like '<0'. The 'AllowedTags' setting unequal to an empty string '' will invoke the strip_tags() function. This function removes all unknown tags, and '<0' is like the start of a very long unknown tag. Your text gets truncated. Consider writing ' < 0' with spaces around the less than sign - PWP takes care of this case (Only a single ' < ' or ' > '!). Or set 'AllowedTags' to an empty string '' and forget about HTML tags in your input box.

What about cookies, sessions and user tracking?

There are no cookies being set from PWP. Because PWP doesn't support the concept of page ownership, there are no sessions required. PWP doesn't log any user action, your webserver will do this for you.

Does PWP work with SSL proxys?

Yes. Some provider offer a proxy server for SSL access to their customers webpages. As PWP will work within any subdirectory, a proxy SSL solution is not a problem.

Can I rename run.php?

Yes. The script name is only referenced by a server provided variable; its name is not hard coded. Make sure to adapt the HTML forwarding in the corresponding 'index.html'.

The shown Wiki page size is wrong!

The size of the Wiki pages shown in several lists (index, etc.) doesn't match the HTML file size and the size of the Wiki mark-up in the edit box. What's wrong there?

The size of Wiki pages as displayed in list views, etc. is the size of your data files at server side. The data file at server side will be a little bit bigger than the amount of data you wrote into the edit box due to some server side formatting operations.

Wiki pages get much larger when they are converted into HTML: All variables are replaced by their values. The HTML mark-up requires more characters than the Wiki mark-up. You can roughly add 20..25%. And a HTML page gets composed with header and footer.

The size printed in list views should give you a rough idea about how much information are stored in a certain Wiki page. In most cases you have to cope with simple numbers form 0..9 KB.

The size of uploaded files is always the real and right size.

What is the file Config.backup.inc for?

This file gets created or replaced every time you save variables or InterWiki link targets via web interface. It contains the contents of your Config.inc before the save action took place.

What about HTML tags ADDRESS, CODE, CITE, Q, etc?

The answer is KISS: Keep it simple and stupid. The idea behind a Wiki is not to provide a complete replacement for HTML mark-up. It should be simple community tool - and PWP has more text rules than I intended to give it. Adding further rules would require the WikiEngine to do more translations which would consume more time on each request and slow down PWP.

Is the generated HTML in compliance to the W3C?

The short answer: 95%. The longer explanation:

PWP is targeting towards HTML 4.0.

Blockquote is recognized by the W3C as a way of indenting text but style sheets are recommended. The original meaning of BLOCKQUOTE is, surprise, a long quote. PWP uses BLOCKQUOTE to indent text. This might be changed in later releases but it will not collide with your existing Wiki pages in any way.

Underline is deprecated, but supported by PWP since most Wiki solutions use this, too. Underline might become replaced by a style sheet solution in a later release. This will not collide with your existing Wiki pages in any way.

PWP does not check for wrong user input, like ' + / ' closed wrongly ' + / '.

What about XHTML?

PWP cannot generate a well formed XML document structure. It uses only opening tags for paragrapghs and list items, which is allowed by the HTML 4.0 specification but violates the XHTML specification.

Is a wipe out attack possible on an open PWP?

The Wiki pages and uploaded files might become deleted into the trash bin. But they can be restored from there. The older revisions won't get lost either. Physically, a file can be deleted from trash or from the history if it has been a certain time of X days (configurable) in the trash bin or in the history.

What is the cache for?

As of PWP 1.5.0, it stores lists of Wiki pages and uploaded files as well as file name search results and full text search results. Wiki pages itself are not cached any longer; the performance benefit was too low.

   (Powered by PWP Version 1-5-1)