🍔? it is too early for that, maybe later

Never do early for that

yes, I was sure that this kind of answer will come. Actually took more time than I expected :)

Looks like I forgot to check for typos before I sent the message xD

and get_template_directory too

wrong. it works

well... someone can be help me with a child theme? its the first time I use it and.. I think that is just the file that I put in the child themes was override but it won't load the other files..

I use only header.php /fonction.php/style.css

Impossible to answer without seeing the context. Plus, checking for "mobile" (whatever that is) on the server side is broken anyway.

what you want to see?

no

=_="

Usually, all functions from the parent theme are available in templates of the child theme. If they aren't, something very weird is going on.

it is maybe the content is not loaded?

what content?

well.. In my function.. I have nothing except the /* author: .... etc..

the header is the copy/past of the parent theme

css is the samething

I thought you don't want to call your function but one from the parent theme?

yeah.

but I can copy/past the function too. but it doesnt, work anyway

> With the additional plugins loaded, the REST API was about 16% faster, and had an average response time of 490ms compared to 567ms over admin-ajax.php

that's both horrible! :\

Hopefully more people throw in their nomination - I don't want to just be defaulted in :/

they will get to it :) always slow to pick up

yeah a part of my problem works. but now.. my js child wont override the parent

he have the same path

why does it take so long for the json api? wasn't it part of the point of short circuting things?

ok, will try to read ;)

sad results. it basically mean that the whole development effort did not bring any "game changing" difference, so now it is even less clear why anyone needs that inteface in the first place, if you can do almost everything with almost the same performance with the ajax end point

he is never trigged -_-"

@MarkKaplun I don't think they ever promised big performance gains, people [without a clue about WP core] just kind of assumed that

I am disappointed too, but to be fair this still is a 13% improvement which is not that bad

ok big.... big failed..: wordpress.stackexchange.com/questions/233935/…

might be faster to use just a custom ajax file that opens its on db connection and ignores WP completely

@rarst I know they didn't promise, but I guess I was on the clueless group here and assumed the impact of not going via the ajax garbage will be bigger

@kraftner, since the recommended front end handling adds some JS garbage the net result will probably be less for anyone just following official docs

Very expensive are the loaded translation files. Some plugins like Yoast SEO are loading their translation on every request

yes. especially german translations with all the long strings

so maybe the impact will actually be bigger on non english lacale since at least some of the plugins load translations only on admin

and with WPML.. ^^

beed a way to actually optionally shortcut plugin and theme initialization

can probably turn off localization, but it is a bummer to do it one step at a time

In retrospect I actually sugested to ryan to have a wp-json.php file which could have enabled all kinds of config defines, but I will leave you to guess his answer

looking again at the test, it doesn't actually mean much. people intrested in performance will run a site on php7 and object caching. This might change the result if the difference is php parsing related

@toscho if you think Yoast SEO loads slow go install some of those monstrous field frameworks and page builder on top :)

@MarkKaplun ajax endpoint overhead is zilch, it's just a hook. it's a core load and all its mountain of backwards compat that takes a while to wake up.

Whats everyone's favourite IDE to use while programming?

PhpStorm

I just flagged this post as 'too localized' because it's about an old WP bug (v4.4.1) and should probably be closed. Is too localized the right reason to use for that?

(it's also an old post that isn't going to be answered; the link to the patch was in the comments - it's only coming up on the active list because someone edited it)

not sure, it could have been a valid answer but since it's sort of resolved and specific to a version...

@MarkKaplun I actually just got to thinking about what you said the other day... Not sure I 100% agree with that. That's true what you said, but that doesn't actually fix the problem, it just masks it.

@TimMalone I'm not sure we should close questions regarding old versions of WordPress. Old or not it's still WordPress Development and may pertain to the many people who don't update WP.

It certainly has a valid answer - posted as a comment. Someone could certainly swoop in and post that comment as an answer if Goosen isn't interested.

people who don’t update WP are dead to us

@CoderSte: phpStorm

@MichaelEcklund, you always balance between things. You use plugins which might be written in a more efficient way, but if you fix their code it means that you fork them and need to maintain them. you rarely have a one obvious good solution.

if you are on a smaller server then having it bigger makes you more tolerant to spikes and ready to host more site, which at the current prices of hardware makes it to be an easy decision. when your hardware upgrade start to cost more is when you go back to check the pro and con of software vs hardware solution

@Howdy_McGee I guess that's possible. At least, that makes it clear that 'too localized' probably wasn't the right choice. I'm coming from the point of view of trying to clean up the unanswered questions list. Perhaps the best option for this one is to move the 'answer' from the comments to an answer.