Doc #25208 [Com]: Typos in the security chapter
| From: | lildurk25208 at gmail dot com | Date: | Wed, 01 Sep 2021 18:52:10 +0000 |
| Subject: | Doc #25208 [Com]: Typos in the security chapter | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-19148@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=25208&edit=1
ID: 25208
Comment by: lildurk25208 at gmail dot com
Reported by: lboshell@php.net
Summary: Typos in the security chapter
Status: Closed
Type: Documentation Problem
Package: Documentation problem
Operating System: Irrelevant
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
Lil Durk is a private agency dedicated to providing responsible access to legal cannabis for adults
aged 19 and older. Weâre an exclusively online retailer and wholesaler for recreational
cannabis and a trusted source for information about cannabis and cannabis-related issues. We believe
our work is meaningful and we take pride in our mandate to promote the socially responsible use of
legal cannabis. https://lildurk.com/
Previous Comments:
------------------------------------------------------------------------
[2003-08-23 04:40:14] ali@php.net
I added the XHTML entity for the ampersand in the example, as i also think an XHTML compatible doc
makes sense.
I'm setting this bug-status to closed, altough this contributes to an inconsistent manual.
-ali
------------------------------------------------------------------------
[2003-08-23 04:09:34] goba@php.net
Erm, using & and & interchangeably in URLs is not a solution. That page should either
use & or & for every URL parameter. IMHO the later would be good.
------------------------------------------------------------------------
[2003-08-22 07:39:18] didou@php.net
I have fixed the error (b) in CVS, the bug is closed now.
+1 for a XHTML compliant documentation, but this shuold be discussed on phpdocs@lists.php.net, not
in a bug report ;)
didou
------------------------------------------------------------------------
[2003-08-22 07:21:27] davey@php.net
Actually for XHTML/HTML Conformance, that first & *should* be an & and so should the
the second &.
Which brings about the question, should we start to change things like this to bring examples upto
standards compliant (X)HTML? Has the decision been made whether HTML in the manual should be HTML or
XHTML yet?
He is right about the extraneous " after the 1 though.
- Davey
------------------------------------------------------------------------
[2003-08-22 06:58:46] lboshell@php.net
Description:
------------
The second example included in the section `security.errors' ("Error Reporting"),
goes something like this:
<form method="POST"
action="attacktarget?errors=Y&showerrors=1"&debug=1">
<input type="hidden" name="errors" value="Y">
<input type="hidden" name="showerrors" value="1">
<input type="hidden" name="debug" value="1">
</form>
There's a couple of errors in the
form' tag: (a) the &' entity
shouldn't be there, and (b) there is one `"' too many.
Thanks.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=25208&edit=1