anyone got a minute to explain how to use esc url raw on update_post_meta? I've referenced several questions but I'm unsure still how to take a URL passed to an input in the post and prepare it before it is saved
or, it is unlikely, unless you want to filter out some url. text by itself should not cause security issues when using the core APIs
.... at least the higher level ones
This is at least my current thinking. You should always escape the output to generate proper HTML, and it is better to just escape it when doing the output over assumin that it was done at some previous time by another process
black and white rules are just easier to remeber and follow, and you spend less time wandering if something was ecaped before or not
Euuuugh. Mods, I made a boo boo. I arrogantly included "removed arrogance" in a revision description, then thought the better of it and attempted to change it to "applied aggressive desalination", but editing the revision didn't remove my arrogant comment so I made a rollback aaaaand...
Well now I've just kind of made a mess and a mockery of the whole editing system
I hope that one day you may find it in your hearts to forgive me D=
@bosco I haven't read your edit in detail but you could just rollback to 5 again... and then a mod could possibly remove revisions 4 and 6 from the history (I think they have the ability to remove revisions)
Today - thanks to our amazing community beta testers - we're shipping our [biggest expansion to Stack Overflow][1] since it first launched: Documentation.
I had to use some hooks to insert a tax query into the WHERE clause of some template tag function at some point - I distinctly remember being horrified by the mass of JOINs
SO Documentation Parameters seem too inflexible. A topic might cover multiple functions - those functions may have parameters with the same names, but which accept different variable types or may be optional or required depending on the function they're used in. Two columns isn't enough :(
