Convert permalinks to site ID, blog ID, type (e.g. 'post'), and type ID – Part 2

Don’t close posts until they are resolved by the author.

Then I suggest that you do not abuse those who try to help you in all good faith.

YES those functions DO have to do with permalinks from where I am sitting.

You asked for an inverse function for a whole slew of id captures based on permalinks. When told that there wasn’t an inverse function, given another approach and even asked to discuss what it was that you wanted, your manner became distinctly unpleasant.

I’m the author of the original Nginx ruleset that’s in use on the WP Codex.

I couldn’t care less what you authored. If you want help here, then you need to treat others with some respect.

…forum submit broken…edit in a few seconds….

https://codex.www.ads-software.com/Forum_Welcome#Posting_Code
Duplicate topics are also deleted on sight.

The idea here is to call url_to_internal_info($url) with the permalink and you get back an array of ‘blog_id’, ‘type’, and ‘type_id’. Usually ‘type’ will be ‘post’ and ‘type_id’ will be the post ID, but not always (you know how WP is ??

@esmi – “I couldn’t care less what you authored.” ?? Took me a month to build that ruleset and it has helped all sorts of people so reading that made me sad. How about we now just call it even? I was mean. And you were mean. I’ll try to do better in the future – that’s all I can offer. I’ll also try to not have a migraine too when I post (migraines make me rather irritable).

switch_to_blog should be use sparingly, as it’s intensive and has weird issues with any caching plugin you may be running.

You’ve worked ‘a month’ to build a rule set. Esmi has worked YEARS to be the respected volunteer she is, and her ‘cred’ is a heck of a lot bigger than yours or mine ?? She was firm. This isn’t Esmi (or me) mean. You asked what the inverse function was called, she correctly told you there was none. She was not ‘unhelpful’ in any way shape or form.

From https://codex.www.ads-software.com/Forum_Welcome

We reserve the right to close posts that are non-productive to the community.

While many times non-productive posts are deleted, sometimes they had some bearing on relevancy. In those instances, we will close them so the information remains, but discussion can no longer be furthered. This includes, but is not restricted to, posts on the following topics: Hosting recomendations (for or against), off topic conversations (i.e. non-WordPress), old/outdated topics, clearly resolved topics, excessive rudeness or antagonistic, and requests for paid support.

Sometimes you might notice that your posts are closed as soon as you post them. Normally this means that they have been caught in the spam queue. This is an automated process and sometimes catches posts by mistake. If this happens, a moderator then has to (manually) unspam your posts, so it may take a little while to be rectified. Your patience is appreciated!