xanaftp

I am here to mention that this problem still exists in WordPress HTTPS 3.1.1 with WordPress 3.4.1

This thread did not help. “Thanks for working with me offline to resolve this.”.

What exactly did you do?

I am faced with the exact same problem, however javascript console shows errors (like unsecured content) that are completely unrelated to P3.

Suggestions?

Thanks for the update Vasyl… the issue has been resolved!

Hi Vasyl I appreciate your quick fix to this issue!

…and I do really like the Advanced Access Manager plugin as it controls which of the functions of WordPress is available to different positions of my council.

I wish I could support it, but at this time my organization has no funding available for it. I may in the future get the pro version if funding permits and the need for it is there.

…I will mark this topic as resolved when I confirm 1.6.5.1 beta fixes this issue.

Thanks again!
-Patrick

Alright thanks Vasyl I really appreciate that!

I would use manual menus (under appearance) but unfortunately I tried and it didn’t work as I wanted them to.

No it builds automatically based off of pages.

Unfortunately I deactivated it, deleted it and its data from plugins, re-installed and activated it, and it did not solve the problem. :/

I’m not sure what you mean by giving you an admin log. If you mean admin access to my website, I cannot do that because my website is under increased security right now since an IP from the Netherlands keeps repeatedly trying to log in to a phony account automated. Even if I were to give you my username and password, you still will be denied access as you need an additional dynamic code.

If you mean giving the output of the “admin log” plugin, I also cannot do that for the “admin log” plugin is outdated and not supported by 3.3.2 .

Vasyl…

I checked the settings for posts & Taxonomies… nothing is excluded. Plus, I can’t use this function as I do not have the pro version; I cannot edit any of the settings in that tab.

—Italiano—

Per qualche ragione essa si fissa dopo aver reinstallato molti dei miei strumenti di Internet come php e utility di rete. Io uso Ubuntu quindi non credo che nessuno di voi lo usano. Se quindi per favore dimmi e cercherò di dirvi quello che ho fatto!

–ENGLISH—

For some reason after reinstalling it fixed many of my Internet tools like php and network utilities. I use Ubuntu so I do not think any of you use it. If so please tell me and I’ll tell you what I did!

—PERSONAL—

Hmm Google Translate seems to be a piece of crap! lol.

UPDATE: I have no idea what the problem was… I was fiddling with my computer reinstalling things and resetting the local network and… now it works.

Interesting… I have no idea what the problem was. It might have been an issue with routing of the IP address.

Regardless cURL is now working and speeds are back to normal.

Thanks for the help!

I do not have other sites on this host… so I couldn’t tell you.

I don’t know if I mentioned… probably it was in another thread… but I already tried that.

After checking settings… it’s not cURL causing the problem. It’s something else. ALL transports (PHP Streams, PHP fsock(), and cURL) are taking over 20 seconds to resolve an address. I do not know why… because normal http requests from my web browser are only a couple seconds. This only happens with the server.

Does anyone have any ideas?

This is a copy from another thread I thought was mine but wasn’t so I accidentally posted a reply there:

I cannot fix this issue with cURL… any suggestions?

I installed Core Control on WordPress and disabled cURL. The only other transport option is PHP Streams… for some reason php fsockopen is not available even though it is enabled in php.ini .

However I HATE php streams transport… it’s SLOOOWWWW! It takes almost 30 seconds to load the add new plugins page… and 30 seconds every time I search for a plugin or go to the next page.

I want my curl back!

Tried reinstalling curl, php5, php5-curl, it all did not work. Tried reconfiguring my internet router… did not work! Disabled all plugins… did not work! Replaced wp-includes and wp-admin… did not work!

By the way do not know if I mentioned this… but this problem started very randomly.