datapharmer

We saw the same and It appears to be related to ninja forms submissions but I’m still investigating the details.

Thank you for posting this. Saved me from this headache when we updated php! I hope the author will update the plugin as this patch seems to work marvelously.

So what are we supposed to do with existing users that cause the “Error: The password you entered for username is incorrect” to allow them to login?

either check generate a certificate and click save or if that fails you will need to generate one from the commandline using openssl: https://www.akadia.com/services/ssh_test_certificate.html

I suggest using a 4096 instead of 1024 and not specifying des3 using the above.

Hi Jeff, yes, we were having a problem with main blog and sub blogs. Network activate caused all sorts of problems. I fought with the main site and got it working (I think uninstalling, reinstalling and activating just on that blog worked), but the subblogs are still causing problems. It definitely seems to be related to the custom posts types.

I even tried uninstalling the plugin and reinstalling, deleting the pages related to tml and recreating them, and the best I can get is that now the tml pages show the standard login (the shortcode seems to be ignored or at least does not inject the custom css properly).

Thanks for the fast reply.

I am using 6.3.5 on a multi-blog install and all TML pages (login, logout etc) are now showing 404s. There are no visible errors – please help!

The site is in a limited beta, so while I can do some debugging it is limited as to how much I can interfere with the site. Is there a tool you can suggest running that will help to gather this information that can be installed that won’t break the site completely (it is ok if it is affected cosmetically, but posting capability needs to stay operational). The site is currently hosted on webfaction.

Thanks!

running the built-in wordpress debugger just gives:

[14-Dec-2012 19:53:53] PHP Notice: Trying to get property of non-object in /wp-includes/post-template.php on line 206
[14-Dec-2012 19:53:53] PHP Notice: Trying to get property of non-object in /wp-includes/post-template.php on line 263
[14-Dec-2012 19:53:53] PHP Notice: Trying to get property of non-object in /wp-includes/post-template.php on line 206
[14-Dec-2012 19:53:53] PHP Notice: Trying to get property of non-object in /wp-includes/general-template.php on line 1475

with or without the code you provided (probably related to a plugin)

substituting xmlrpc_call_success_mw_newPost and a few other hooks in place of wp_insert_post and removed the check for if XMLRPC_REQUEST was defined… all had no effect

I’ve looked over the server access and error logs doesn’t really show anything… all of the xmlrpc returns 200 ok

If you have other debugging suggestions I would be happy to look further.

Thanks for the reply Daniel. I understand you are busy and appreciate that free support is just that!

Unfortunately adding that in to the functions.php didn’t seem to do the trick. I’ve tried using a couple different hooks too without success. Not sure why it is so difficult to get this triggered by the xmlrpc, and if it is the post id or the author that isn’t getting passed, but it might be related to how xmlrpc triggers the content_save_pre filter.

Anyhow any other suggestions would be greatly appreciated!

I understand many folks are very busy this time of year, but if anyone reading here has a suggestion for what filter would help with this, all suggestions would be appreciated. Thanks again for a great plugin!

1. Have you checked to make sure emails are working from wordpress in general? For example, if you click the forgot password link do you get an email containing a link to reset your password?

2. Did you click update/save/submit after checking the boxes?

Jeff, I can now verify this problem. With theme-my-login enabled if a user goes to an http login page it sends their data insecurely and then redirects them to the https version of the login page before they can actually sign in. Strangely, trying to do a php or apache redirect from https://domain.com/login to https://domain.com/login results in a redirect loop, although I haven’t had the time to figure out exactly why that is happening so far. Example to reproduce redirect loop: install and activate WPSSL (WordPress with SSL) plugin, mark the theme-my-login page as force ssl in the wordpress editor and click update.

Details: multisite subfolder install, using cloudflare

Good to know it is on the way. I understand facebook is a moving target and that’s got to be hard. Much appreciated, and I look forward to version 2. Thanks for a great plugin.

Unfortunately, that isn’t very realistic as it would break all of the websites since it would disable domain mapping and everyone visiting the sites would get a 404…. That said I am in the process of setting up a non-production environment and will test this combo in it to narrow things down.

Looked into this more, and determined it only happens under certain conditions when w3 total cache is installed. It is not inherent to this plugin, as removing w3 total cache solves the issue.