mannym / viennacms Goto Github PK

Support for changing the IP address reported for reverse proxies should be 
added. This would be implemented with a check for a 'trusted IP' and then 
cutting off the first part of the X-Forwarded-For header and placing it in 
REMOTE_ADDR.

What steps will reproduce the problem?
1. Create an URL using German accents like 'u with umlaut'

What is the expected output? What do you see instead?
The URL should contain 'u', instead, another character is shown.

What steps will reproduce the problem?
1. Upload a text file to the Files folder
2. Download the file from the widget
3. Open the text file in an utility like Notepad

What is the expected output? What do you see instead?
The file contains the basic page layout and seems to be processed by
LayoutController. this is likey due to wrong return values being passed.

The status widget should display a warning whenever the code detects a 
reverse proxy might be in use. This could be detected various ways, the best 
would be a check if > 20% (?) of site users (once a registration system is in 
place) share the same IP address (when the total user count > 15, possibly). 
Dismissal of this message should obviously be possible.

The administration control panel should have a dashboard section with 
(possibly) the following information:

- system status (any errors, needed updates, and so on)
- initial steps (creating a node, help)
- recent updates (comments, whatever)

This page should have a 2-column 'start.com' style widget layout, and widgets 
should be providable by modules using the type registry.

Whenever an extension providing a specific node type is disabled, this node
becomes invalid, having no icon, and other things. This is a major
usability issue, and should be resolved.

The solution could be like this:
1. any type registered by an extension is checked for references
2. when the extension is disabled, any referenced type should be checked.
In case of nodes, for instance, one option could be selected:
2.a. downgrading the node to an existing node type
2.b. prohibiting the disabling of the extension
2.c. unlinking the node from the tree temporarily/hiding the node (if
conversion is impossible or unwanted)

Any other registered types which do not have a dereference handler should
simply prohibit the extension from being disabled.

As the subject says.

Browser support is good enough for making UTF-8 URLs directly usable
without removal of characters. Even if not supported, urlencoding should
fix it.

Example: Wikipedia directly encodes UTF-8 characters.

What is the expected output? What do you see instead?

Expected: 777
Instead: strange output, possible caused by 0777?