mangozilla

Looks like you found a fix. What was the cause?

I don’t have first hand input for you, but in reviewing this plugin for my own purposes I came across https://darwinhub.com/category/events/, which has integrated the like button nicely on each event. I assume it’s a standard plugin.

@veganist- yes, as in my original description. I tried that on my local installation but I’m not getting the result. See the link to the image for a visual.

Still haven’t found the solution. Would a new sitemap do the trick?

FIXED: It’s a FIREWALL issue. I don’t understand the symptoms, but the fix was to shut down the firewall. I use CA ETrust Internet Security Suite, which includes Etrust Anti virus and Etrust Firewall. Shutting down the firewall let me resume access to the blog admin panels. I still leave the Windows firewall active. I’m not sure about any sucurity issues this may cause, but at least I can get in.

I hadn’t seen this solution (or probably better stated, a “workaround”) presented in numerous other login issue posts or on the WP troubleshooting pages. I hope this can help someone else.

Fixes after days of frustration!!! CCpyle’s fix above worked for me. DISABLE FIREWALL. I use CA Etrust, and I can now login if I close the Etrust firewall (leave the windows firewall in place). Don’t know why, and I’m not sure of teh security risks, but at least I can access my admin panel. I hadn’t seen that solution on the multiple other posts regarding login issues. Glad I found this one!

@neville- thanks. I read your post, & think mine’s a different issue. Not related to an upgrade, but a new install, and never had anything older than WP2.6.1 on my host server. Ihad also read your reference to the post citing “load balanced behind an ssl accelerator the SSL is added through the appliance and the apache/php install knows nothing of the https. I edited the two rows in the wp_options table that had http and changed it to https.” That’s pretty far over my head, but looked at the options table, found only 1 http reference, changed it to https, resulting in the login error:
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)
The page you are trying to view can not be shown because the authenticity of the received data could not be verified.

Again, don’t know what that means but I changed it back…

@mrmist – thanks for the offer. All three blogs on my host server are WP 2.6.1. The two new blogs are brand new installations, and when I had trouble after installing 2.6.2 I deleted and reinstalled with 2.6.1, which remains now.

Blog #1. (the original) – is a subdomain of a website I have (i.e., firstdomainname.com/blog). The index.php of the web site is in the root, and then the blog is in /blog#1.

Blog #2. Domain is domainname#2.com, and installed in /blog2
Blog #3. Domain is domainname#3.com, and installed in /blog3

At this point the issue seems to be isolated to my laptop, since I don’t experience the trouble using an offsite pc or even an old desktop I also have here at home. Haven’t tried taking the laptop to a wireless access point coffee shop, or something. I just can’t figure out what setting would be placed on my pc that remains regardless of browser, even after clearing cookies, cache, & flushdns. Also ran Spysd today – no help.

Summary: Login access to any ONE of three blogs installed on same server (only 1 in root, but no subdomains). Can change the blog I gain access to by reinstalling Firefox and logging into any blog, which becomes the new one & only one I get access to. Using IE produces same result.
Admin access to all three blogs using different PC (not mine) running Windows2000 (WinXP on my PC). Clearing cookies, cache, and flushdns fails to resolve. I have to believe there’s someone who can ID the solution. (pleeeease!)

NEW INFO THAT NARROWS POSSIBILITIES:

I uninstalled and reinstalled Firefox browser, and successfully logged into the first NEW blog I installed. Then tried to log into my original, ongoing blog (which had no previous login issues) on the same server but could not. No luck on any other blog. That login set something somewhere, because I opened up IE browser and got the identical new results – admin access only to the blog just accessed via Firefox, and no login access to any others. So something is telling both browsers about the first admin access that prevents other access.

What setting could effect each browser this way? And how can I fix it?

…and one more thing. Since I already have a blog as a subdirectory in the root domain, I wondered if that’s creating conflict. Tried using pw for that blog, and received ERROR: Incorrect password.
ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress. Bad password error was expected. I confirmed that cookies ARE allowed in FF and then specifically enabled cookies from that specific domain.

Issue still remains.

Yep. That was the first on my list of things I tried. Any other ideas?
Oh yeah. I forgot to add “changed password” to my original list of things I tried (not getting password error, just no login – so not the issue).