@Howdy_McGee the first returns the URI the latter returns the path, two different use cases... neither contains a trailing slash

@Howdy_McGee developer.wordpress.org/reference/functions/… & developer.wordpress.org/reference/functions/… ;) As @userabuser said, one is the URI (i.e. http://......), the other is the path (e.g. /home/user/public_html/...)

REST API should be a clean slate not to perpetuate confusion found in core WP API, but alas... wontfix. Sad. github.com/WP-API/WP-API/issues/1202

To all members with 3000 rep or more: Please use up your close votes!

@userabuser anything added to core will be of equal or worse quality

hi

plz solve it

what the hell?

we are not that loop :D

solved

@toscho worng

nope

I'm always right, it's built-in.

@toscho but you are wrong this this time

nope

you are

its a script

see it

@Rarst Certainly seems that way after traversing through its code. I would have thought that the REST API, at the very least, would be an opportunity for some kind of fresh start... boy was I wrong, same shit, same attitudes :/

ya

i am saying this only

This is not the solve a problem that you refuse to explain chat.

I think I worked it out...

@userabuser nope. any development is subject to situational constraints. developing something for core is under enormous constraints just from that.

and it's not because of people and attitudes really. it can't go any other way under circumstances.

@Rarst definitely understand that for some situations, but to say you wont make your filter more context appropriate because core doesn't to me is just perpetuating poor form... but hey, WP right... ¯_(ツ)_/¯

note that these battles are often had already been had and lost internally, WP devs don't like to admit these things

who am I to argue with their demi-god

Is there a bot running to flag all the WooCommerce questions that are too old to migrate? The Close Votes are getting 193+ :(

@MayeenulIslam It's worse than bots, it's humans: meta.wordpress.stackexchange.com/questions/4193/…

humans are in infallible

@TimMalone and I are heading a cleanup action in posts and tags. If everybody just follows our orders, no one will get hurt.

It's WordPress, someone always gets hurt!

@cjbj Hmm. Human aliens. :)

Funny, I was thinking of writing a user script to help with it ;). Open woocommerce tagged question.. look for wc_ function/filter in code.. downvote/flag/comment and move to next ;)

Seriously though, yes, it is me. I have been doing about 30-40 of them a day, using up all my votes. If they don't get closed most of them will get deleted automatically by the Community bot (Roomba) within 30 days.

But it would obviously be better to close them sooner.

@MayeenulIslam The cleanup effort is documented here: meta.wordpress.stackexchange.com/questions/4193/… - love to have your suggestions

@userabuser, having bad ambigious code is a good way to ensure job security :(

the sad thing is that in most places the first prototypes/versions are a "prof of concept" and it is silly to point to previous code as if it is a "bible" to how to properly do things.

It is just the kind of culture of core development, hacking quickly something together is way more important then investing time in thinking how to do it properly in the first place.

which is part of why rest api is several years late

now spare us the additional rants and don't looks at all at the fields API ;)

@MarkKaplun oh... already looked at the fields API, f**K that thing...

lol, sorry for being late in warning you :)

The REST API on the other hand I have a real use and need for in production projects... I was just a bit amazed at the "don't give a rats" attitude towards a fundamental design flaw in the REST API itself that could easily be avoided simply by adding a suffix to a filter! The backward thinking that because core doesn't address collision issues on CPT and taxon names doesn't have any bearing on writing good shit in the REST API - but apparently I am wrong.

The Fields API is a lot like looking into the sun...

this is because the res API itself was never designed, never had any use cases it should answer

fields api is mostly a copy of the customizer, for some unknown reason

Customizer API is really good

ok, lets agree to disagree here, but sure at least it was designed for what it does instead of just being copy and pasted

come on now, you should have known what was up when I said "good"

:)

For a long time I was sure that it is some complex JS app that queries the server every time, now I wrote the code to use it and understand why people claim it is not scalable

yup... try loading the customizer outside of the backend too great fun

A wet dream of mine is to do a chrome extension that replaces the need for the customizer

hmmm, seems like my client still exists better to go and do some actual work :)

Wet dreams do come true...

cya :)

We used to have a max-width tag. Used to.

@userabuser if I needed a (reasonably simple) API for WP right now I'd just take Fractal and write it

@cjbj Sigh.