LFGabel

Thank you for your quick response via email. I appreciate it. However, your suggestion of a database restore likely won’t solve the issue because I can see the page data via phpMyAdmin in the MySQL postmeta table. For some reason the page isn’t being displayed.

I may have to investigate other options, perhaps outside of WordPress. A landing page failure is a big problem, especially when advertising is backing it.

With thanks.

Thanks for your patience, murphdog. It is strange that I get the same issues on multiple browsers on multiple devices.

Where to I go to now? It seems to me that the “Websites” link would be best, but I’m not sure. I have no idea where exactly to “create” my application.

If anything, the instructions for Facebook with this plugin need clarification.

Thanks.

I tried IE and Safari. IE just went into an infinite redirection loop and Safari never even mkes it to the login screen, telling me the “server isn’t responding”. I tried “http” and “https”.

I tried Safari and Chrome on an iPad. Safari went into a redirection loop, and Chrome did nothing, stalling on the login page.

Maybe the developer resource moved? Could this be it? https://developers.facebook.com/tools/ I don’t really know what I’m looking for.

Nevermind. Found the problem.

My appologies for wasting your time, Scott. It appears the theme I was using was doing something to the .htaccess file upon login/logout.

Didn’t happen with the twenty-eleven theme. Thanks for the suggestion.

However, I haven’t touched the permalinks settings since I set up the website, and that was months ago. This problem didn’t start until I installed this plugin.

Are the permalink setting modified in some other way?

Update:

It appears this is not just affecting the .htaccess file. On another wordpress installation, it’s updating the date stamp of a file called “stats/logs” and the peculiar thing about this case is the “stats/logs” file can’t be seen via FTP. Is it possible this file is hidden?

It’s always just one file. Anyone else notice this?

17 hours after resetting, I get this:

Total lockouts: 4 lockouts since last reset
Active lockouts: 2 IP is currently blocked from trying to log in

I dug into the “wp_options” table and it does show the IPs that were logged in the option variable “limit_login_lockouts”, but does not add the IPs to the option variable “limit_login_logged”. When I visit the settings page for the plugin, the logged IPs do not show up at the bottom like in your supplied “screenshot-3.gif”. This is expected since in your code, the log is displayed only if “limit_login_logged” has information stored in it, and it doesn’t, but should it if there’s data in the option variable “limit_login_lockouts”?

5 hours after resetting, I get this:

Total lockouts: 1 lockout since last reset
Active lockouts: 1 IP is currently blocked from trying to log in

Should there be log information now? If there should be, it’s not showing up.

I’ll try removing and reinstalling the plugin.

Perhaps not. Would resetting the total and active lockouts activate the logging? I’ll try it and get back to you.

Thanks for the hint.

All the best,
Lee

Isn’t that required to allow automatic upgrades of WP and plugins? Changing the permissions to allow creation of new folders and files?

There should be an easier way around this for non-techincal users.

The way I got around it was to:

– set temp folder permission to 777 (via ftp, like filezilla)
– set wp-content and upload (and subfolders) permission to 777
– upload media through dashboard
– revert temp, wp-content, upload (and subfolders) back to 755.

You need to do this for every upload session.

Yeah, pain in the mother frickin’ ass.

Hey, WP developers, why not make this easier for everyone?