[wp-trac] [WordPress Trac] #47357: $allowedentitynames could be null
WordPress Trac
noreply at wordpress.org
Sun Jul 31 15:46:10 UTC 2022
#47357: $allowedentitynames could be null
--------------------------+----------------------
Reporter: doctorlai | Owner: (none)
Type: defect (bug) | Status: closed
Priority: normal | Milestone:
Component: Formatting | Version:
Severity: normal | Resolution: wontfix
Keywords: | Focuses:
--------------------------+----------------------
Comment (by TJNowell):
Given that this has security implications, allowing `null` while warning
the user in the log could lull them into a false sense of security if
they've just followed an old article that mentions `CUSTOM_TAGS` and don't
know about error logs etc.
Perhaps the `else` case would be a good place for it though, as well as
checks if those variables exist and have values. It would still result in
the same situation but the user would have an idea of how to fix it rather
than being stuck not knowing what to do.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47357#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list