Skip to content

custom error pages - Reference to security functions warning is no more #6771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

hvt
Copy link
Contributor

@hvt hvt commented Jul 27, 2016

Reference to security functions warning is no longer needed in > 2.8.

In the example code of the custom error page, there was a comment reference to the `Avoiding Exceptions when Using Security Functions in Error Templates' section, that lived in the pre-2.8 documentation. That subsection is no longer there.

…re in 2.8

In the example code of the custom error page, there was a comment reference to the `Avoiding Exceptions when Using Security Functions in Error Templates' section, that lived in the pre-2.8 documentation. That subsection is no longer there.
@xabbuh
Copy link
Member

xabbuh commented Aug 3, 2016

👍

Status: Reviewed

wouterj added a commit that referenced this pull request Aug 5, 2016
This PR was submitted for the master branch but it was merged into the 2.8 branch instead (closes #6850).

Discussion
----------

Remove outdated reference

Finishes #6771

Original description:

 > In the example code of the custom error page, there was a comment reference to the `Avoiding Exceptions when Using Security Functions in Error Templates' section, that lived in the pre-2.8 documentation. That subsection is no longer there.

Commits
-------

21fcb72 custom error pages - Reference to security functions warning is no more in 2.8
@wouterj
Copy link
Member

wouterj commented Aug 5, 2016

Hi @hvt! Thank you updating the example. It indeed looks like we forgot to remove this reference.

As we recently restructured the docs, there was a problem merging this PR. I've taken your commit, applied it on the new structure and created (and merged) #6850 . In short: Your change is now in the documentation and you're the author of that change.

Thanks!

@wouterj wouterj closed this Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants