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

why to escape it at all?

escaping is something that you should do on output, not input

@MarkKaplun so does a URL entered into the field, for security purposes, need to be sanitized?

no

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)

@TimMalone Thanks for the suggestion. Ultimately, it may all be inconsequential as the question seems intent on closure. But... oops O.o

@bosco I have just edited the revision comments.

@toscho many thanks, Great One. I won't repeat such nonsense =D

Yes, you will.

Probably ='(

trying to figure out why tax query is slower than raw SQL and it's AAA!

@Rarst Heavy TAXation, eh? eh?

basically I got an API query that is twice slower than raw SQL and at the end of the day I can't even tell why

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

@Rarst but that is curious

that's not curios anymore, that's messed up

I know the general reason — it does more stuff

well, I need to do more stuff fast

So will you end up using a raw SQL implementation then? O.o

I already have raw SQL (it's work stuff), I need to get rid of it since it does less and is bugged up

github.com/Yoast/wordpress-seo/pull/4595/files

that's quite the annoying caveat

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 :(