I'll just repost from yesterday just one more time:

@Rarst Maybe?

not so far

I hadn't even looked what they are going to do with language packs and stuff. can't say I expect to be happy about.

So manually manage them with repo? Can't even easily create composer packages as that would end up having subfolders, right?

probably for now. I don't do much language stuff myself.

Okay thanks.

Now into investigating why as soon as you add a language (freshly downloaded) WP screams for an Update (While already on 4.0) Good Morning WP...

updated to PHPStorm 8 ... all console commands are gone. sigh

which do you mean?

Terminal in Storm doesn't recognize a single command

"real" terminal or "pseudo" terminal with built-in commands?

what do you mean? what is "real" and what is "pseudo"?

there is actual terminal (like normal one, just in phpstorm) and there is thing they did earlier that only supports specific utilities

how do I determine the difference/know which one I am using?

real is Alt+F12 (says Terminal), pseudo is Ctrl+Shift+X (says Commands output)

Ah. Haven't ever used the "pseudo" Terminal

yeah, it's from before the real one :)

Point is that the Settings have been pointed to cmd.exe, which works stand alone, but not in Storm. Now switched to Git/sh.exe. Problem is that it starts breaking terribly.

don't know, upgraded without issue for me

PHPStorm names "pseudo" as "Command Lines Tool console" ... ha!

@Rarst on Win?

yes

Hm. The command that kills it is vagrant status... :/

@kaiser No more constants github.com/ThemeFuse/Unyson/releases/tag/v1.2.0

@moldcraft oh, wow. nice! congratulations :)

Wow that is what I call quick response!

@kraftner I think your Q is a valid trac ticket - Core still notifies users of an update even when it can't update it itself, can't see why plug-ins shouldn't also have a "notify admin" update alert.

@moldcraft :)

A 2k user is asking a WooCommerce question. I don’t get it.

@StephenHarris Great. So no simple fix and years of waiting for Core ;)

Thanks anyway.

@kraftner Well you can always use after_plugin_row_{plugin} hook. I just think it's something that should be fixed :).

@kraftner just re-read your Q, update_plugins isn't populated if DISALLOW_FILE_MODS is enabled? sigh

I already quickly tried to go in there, it just seems that this is spread over various places. Will have a closer look as soon as I find some time and maybe file a ticket.

At least I'm sure now it isn't some noob config error.

Well I don't think you can visit the update page, but I thought plug-ins checked for updates on the plug-ins page too (hourly) and every 24 hours in the background. It's a bit of a maze.

@kraftner see github.com/WordPress/WordPress/blob/master/wp-includes/… - I think update_plugins should be populated anyway, but I've not checked...

No I can't. Tried that. But they are checked when visiting the plugins page. (Deleted transient, visited plugins page, transient returns)

@toscho makes no sense, if ignorance is reversely correlated to reputation

I guess you've found the black swan event

It is only about the display. And that is weirdly connected to the current_user_can('update_plugins' ) all over the place.

As if the ability to DO an update was the same as the ability to be notified that there is one.

@kraftner That's exactly what's happening. With core updates at least they do something like:

if( current_user_can( <update> ){
	<click to update>
}else{
	<tell an admin to update>
}

there's no else for plug-ins and there should be. Probably an oversight.

Exactly. Put filing a proper ticket on my todo list, will let you know once I'll find time to.

Does anyone have or seen a nice overview of the init process of WP? Like a flowchart or something.

Make sense of WordPress core load

nice

Is there a way to prevent errors when using extract();? like forcing the variables to exist, without having to actually define the variables before extracting? -- Does that make sense?

not using extract()

extract($data);

$this->posts = $posts;

$posts is underlined as error.

but if I add $posts = null before extracting, it's fine.

just to make this a bit more clear: do not use extract()

What's wrong with extract();?

I've been using compact(); and extract(); in a lot of my code.

Trac ticket

@MichaelEcklund it exists

@Rarst Makes sense.

So not using compact(); and extract(); is opinionated. There's nothing WRONG with using them. It's just for readability. If someone defined the variables before extracting, like you're supposed to do, then it wouldn't be so hard to understand.

just for readability? pretty much nothing matters in code but readability

reading code is complex, what it does is most of the time primitive

Okay, I won't argue. I guess I'll stop using them then.

compact() isn't bad, it being reverse doesn't mean it has same issues

okay, I'll still use compact(); then.

Thanks for the advice. @Rarst = friendly; @kaiser = Angry bird;

:D

@MichaelEcklund The problem isn't only readability. It's IDEs not able to handle it as well.

greetings anyone free to educate me on uploading images in regards to dynamically greeting fixed thumbnails thought large uploaded images are set on a min/max width

@Matt I'm not really getting what you are trying to do

I'm tempted to say, educate yourself, anyway

but joking aside, ask a question on the main site, it does actually work :)

I dont mind asking on the main site just trying to prevent a duplicate question if it has been asked

you can always search for duplicates, but a good explanation of the question with no assumptions or ambiguity is key

Gotcha.. ill try to be very detailed in my question

it's not so much details, as assumptions

e.g.

you didn't say where or why you were uploading images, what you meant by dynamically, where does a greeting factor in? What about your thumbnails are fixed? Which large uploaded images have what min max width?

Well what I'm trying to find out how to resize an image to a certain width regardless of the height then take that same image a set a fixed size width and height thumbnail

Ive been looking at wp_get_attachment_image and thumbnail