Fixing these failures now.

Evan Winslow
http://community.elgg.org/profile/ewinslow


On Sat, Apr 5, 2014 at 7:50 PM, Paweł Sroka <notifications@github.com>wrote:

> In docs/design/security.rst:
>
> > +
> > +XSS
> > +===
> > +
> > +Filtering is used in Elgg to make XSS attacks more difficult. The purpose of the filtering is to remove Javascript and other dangerous input from users.
> > +
> > +Filtering is performed through the function ``filter_tags()``. This function takes in a string and returns a filtered string. It triggers a ``validate, input`` plugin hook.
> > +
> > +By default Elgg comes with the htmLawed filtering code as a plugin. Developers can drop in any additional or replacement filtering code as a plugin.
> > +
> > +The ``filter_tags()`` function is called on any user input as long as the input is obtained through a call to ``get_input()``. If for some reason a developer did not want to perform the default filtering on some user input, the ``get_input()`` function has a parameter for turning off filtering.
> > +
> > +XSRF
> > +====
> > +
> > +Elgg generates security tokens to prevent XSRF attacks. These are embedded in all forms and state-modifying AJAX requests as long as the correct API is used. Read more in the Actions_ developer guide.
>
> Apparently tests are failing on this line: /home/travis/build/Elgg/Elgg/docs/design/security.rst:93:
> ERROR: Unknown target name: "actions".
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Elgg/Elgg/pull/6688/files#r11324217>
> .
>