otiteb

Ok, i think it’s time to consider this one solved ??

@psybertron , it’s probably better that you start a separate thread to attention to your issue

@immortal

Just tried the plugin and it indeed fails on the “[cURL with a POST body] ” test. So now it’s waiting time for me (till the hosting provider gets the update done…)

@pfarley

cURL is the library wordpress uses to retrieve data from www.ads-software.com servers in the plugins and themes pages. How to update it depends on your server/hosting configuration (but you might want to check https://curl.haxx.se/libcurl/php/ as a starting point) … if you’re on a shared hosting (like the site i found the problem is), then most likely you won’t be able to do the update yourself and have to rely on the provider.

Also, from other thread, i got this:

https://core.trac.www.ads-software.com/ticket/25716

Apparently, it’s related to cURL 7.31
(might take a while till i can confirm this on ym case, but it does sound likely)

@immortal

Sounds promising ?? i checked the version that hosting is running and it’s 7.31.0 (i see that latest stable is 7.33.0 , is this the one under which you got the issue solved?)

I can’t confirm on my case sine i don’t control the shared php installation, i can’t update it by myself. I’ll ask the hosting provider to do it.

Thanks for the tip!

…scratch that “it didn’t break” statement: The “Popular tags” word cloud section on plugin search works ok, but plugin and theme search themselves don’t. (i type to search, and i again get the error)

My main instance (the one i downgraded to 3.6.1) works completely fine again.

…so there’s definitely something going on with 3.7 (at least in this particualr hosting scenario) … anything else i can try?

That would make sense to me… anyways, to keep on testing, i tried somethign else this time:

-manually downgrade the 3.7 instance to 3.6.1 –> this resulted in theme and plugin search working again on this particular site

-upgrade the 3.6.1 to 3.7 –>strangely, on this empty test site, the plugin and theme search didn’t break

…so can it be a theme/plugin issue, even if the problem presents itself after deactivating?

As a reference, i have the following on the “search broken” instance:
Themes
-Responsive by Cyberchimps (+1 child)
-2012 / 2013 (the default ones)
Plugins
-Responsive Add-ons (part of the responsive theme)
-Visual form builder

Just for curiosity, i’ll try to replicate the error in the “test” instance …

All seems fine when i enter there from the 3.7 instance(i mean, it has the Last checked on 2013/10/25 at [like 1 minute ago]”).

Not sure if it necessarily means server-to-www.ads-software.com connection is happening, but yeah, it seems ok

The 3.6.1 vs 3.7 test, however, definitely IS server-to-www.ads-software.com , so in this particular case i would believe that’s not the issue

(again, sorry for not being able to do the actual ping/tracert)

Hi again

Sadly this site is on a kind of crappy hosting, so i can’t enter the server itself to try the ping/tracert… BUT, i did think of a wat to test if it’s the server:

I’ve done a separate “test” install of WordPress 3.6.1 (same web server, even same db, separate prefix). Entered the plugin section, and it all works fine there. Just for the sake of making this more comparable, i disabled all plugins on both instances and switched to twenty thirteen.

So now i have, on the same web and db server:
-An instance with 3.6.1, plugin and theme search working
-another instance with 3.7, plugin and theme search not working

I think this should rule server configuration/firewall out, right? But if so… what’s causing this misconnection? Still puzzled

Ummm, manual installation through… and no changes in the error

Hi Ipstenu,

Just went through you link, and it seems like, other than manual installation, i’ve covered the basics there… i guess i’ll try the manual thing now, unless there’s some common config i should look at?

Hi

Just tried, no changes.

I deactivated all active plugins and reverted the theme to twenty thirteen, then tried the theme and plugin search again: got the same error.