xxx was last updated 46 years ago

It might well be the case.

Its hard for me to tell.

You are far better positioned to make that judgement call.

And just like that I found out why it’s happening, but it’s not me, it’s WordPress.

Or rather, it’s the www.ads-software.com API for plugins.

On a clean build, I went to install the JSON api and saw this: https://cloudup.com/cREjgTq9FYV

46 years!

But when I went to the plugn page, it said the plugin was updated 1 minute ago! https://cloudup.com/cS9H8-yKdI1

Daheck I says. So I looked at the update log: https://cloudup.com/c5LrIE39eJw

Thus the answer is this: WordPress is drunk.

More reasonably, the issue is that the API is giving inconsistant results, which means the errors are on this end and I can’t fix them ?? I’m getting garbage data. I’ll talk to Otto about this, since the API shouldn’t be this derpy.

“derpy” is that even a word?

Anyway, meh. Told ya!

Happy new year Mika. Looks like its started off the right way at least.

All you wish yourself, to the ones you love and the ones who love you too.

Terence.

Prompted by something I just read of yours, I did a clean install of the latest version on to a localhost dev AMPPS server here, and got the following result 1) slows down the load of the installed plugins page, 2) its still derpy ~ https://drive.google.com/a/qloudpress.com/file/d/0B0SpkI7-vK5od3NxbmZOTkVJenc/view?usp=drivesdk ~ and now 3) the Server Type color bar has disappeared.

So, its going backwards here.

I think somehow it’s conflicting with your server and I cannot fathom why :/

Maybe your ampps box setup is derpy?

Does it have access to ping www.ads-software.com at all?

AMPPS is actually running, and Apache/mySQL as a service on the same PC I am using to write this. Its has 32G of ram, so its simple and easy for me to use aa a dev machine.

And yes it has www.ads-software.com access. No problem there.

So, I think you are wrong. Why? Because I have now tried it on three different servers. Two at DigitalOcean and one at Linode. And this, the fourth time, its on AMPPS, on my Windows box here at home.

Have you ever considered the remote possibility that its the environment YOU are testing in that’s, well, how shall I put it… derpy?

I tested on 5 different servers, different hosts, VVV and MAMP and I’ve only been able to reproduce it with one instance.

https://www.ads-software.com/plugins/json-rest-api/

Notice how it says the last update was 1 min ago? Actually it was almost 2 weeks. But when I check in any site’s wp-admin as if I was installing a new plugin, I get 46 years – https://cloudup.com/cREjgTq9FYV

Now. I know for a fact that happens when the API is caching a ‘zero’ response. However for all of your sites to always and forever be caching a zero, and for linux to be derpy and think that 0 = 2016-1970 = 46 years, is … well it sure could be me, but it’s ONLY you, which means something you’ve got is weird.

What happens if you go to install a plugin through the ‘Add New’ interface? Are those plugins all showing as 46 years for you?

It might well be me. I’ve been having a helluva year of it so far.

Maybe, as with most things, its the least obvious combination of things other than what we are expecting it to be.

For example, I am running Chrome on Windows, and I bet you ain’t.

Could it be the servers are getting infected with the Chrome 1946 bug?

And maybe yours is just a rare and isolated outbreak resulting from that strange half-strength voltage you are using, in combination with an Apple badged faux linux system?

Add new works fine, by the way, unless I have this whacky plugin of yours installed, that is.

Even if it did work OK, it doesn’t do anything particularly interesting that you should need a plugin to do for you; does it?

Your desktop should (should) have no bearing on what your server is doing.

But I did grab a windows laptop and check on Chrome. No issues with my plugin, exact same issues with JSON. Already talked to Otto about it, he knows it’s the API for the JSON issue, which is why I wonder if your setup, for whatever reason, just cannot reach the WP API and is thus throwing a constant 0.

Because THAT would explain why it’s slow.

Right? All the plugins (and you have a lot) are pinging wp.org to check for a version, they can’t reach it, they return 0, and the math says 46 years because linux is linux.

So I’m going to see if I can add in a check. If you can’t reach the API, you don’t get to have that feature.

ETA: FWIW, it’s already got this code in there. It’s SUPPOSED to say “Oh you’re not on .org, skip!” and clearly that’s just not working. Because all your 46 years old plugins are, again, the ones not hosted on .org.

Pushed v 2.2.2 which bails even earlier if the API can’t be reached or the plugin throws a bad slug (which some but not all non-wporg hosted ones do). This should cover the bases and possibly speed things up for you, but you do have a high numbers of non-org hosted plugins. The return is cachable, but it’s possible that the cache just isnt long enough for you. Still. The cache should only be triggered when you hit the plugin list page.

That’s not “a lot of plugins”. Ask Pippin.

I’m giving it another shot on a dev server.

It better work this time or I am coming round to your house and staying for lunch for about a week.

OK, that’s it. 2.2.2 is deactivated again because its slowing the whole site down to a crawl.

Plugins used on this site

Code Snippets by Shea Bunge.
Easy Updates Manager by kidsguide, ronalfy, pixolin, roary86.
Enhanced Admin Links in Multisite ‘My Sites’ Drop-Downs by Aaron T. Grogg.
IgnitionDeck Crowdfunding by Virtuous Giant.
IgnitionDeck Framework by Virtuous Giant.
Join My Multisite by Mika Epstein (Ipstenu).
Krown Shortcodes by Ruben Bristian.
oAuth Twitter Feed for Developers by Storm Consultancy (Liam Gladdy).
Plugins List by David Artiss.
Relative URL by Tunghsiao Liu.
Reveal Network Activated Plugins by David Gewirtz.
Shiny Updates by the WordPress team.

Whoa! That’s weird. Just reactivated it again to see if I could figure out which one of the functions/features was causing the problem, and the site runs fast again.

Even with UI Labs activated.

Its a miracle.

Nope its back again… the slowdown, that is.

When I switch from child blog to network admin, of say, plugins, it starts dragging its petutie again.

It feels like its off doing a lot of very slow checking of the credentials of all the plugins I have (9 active, 13 inactive) in the directory.

Since this is a dev site I am currently building it means I am in and out of the plugins folder all the time, which probably accounts for all the slow down.

Isnt there something you/I can do to prevent this. For example, only check the directory every so often, or if a new plugin is added, and not check every time you access the page?

Just my 2c.