VaultDweller

WP core installed and the plugin is the latest one.

The URL after entering correct OTP password is following

https://MYURL.DOMAIN/tuktuk?redirect_to=http%3A%2F%2FMYURL.DOMAIN%2Fwp-admin%2F&aiowps_login_msg_id=session_expired

where MYURL.DOMAIN — is my domain

If I delete everything after ? then everything is the same. I am not able to login ??

The reason of my problem was option FORBID_PROXY_COMMENTS

I removed the following lines from .htaccess and that fixed my problem.
#AIOWPS_FORBID_PROXY_COMMENTS_START
RewriteCond %{REQUEST_METHOD} =POST
RewriteCond %{HTTP:VIA}%{HTTP:FORWARDED}%{HTTP:USERAGENT_VIA}%{HTTP:X_FORWARDED_FOR}%{HTTP:PROXY_CONNECTION} !^$ [OR]
RewriteCond %{HTTP:XPROXY_CONNECTION}%{HTTP:HTTP_PC_REMOTE_ADDR}%{HTTP:HTTP_CLIENT_IP} !^$
RewriteCond %{REQUEST_URI} !^/(wp-login.php|wp-admin/|wp-content/plugins/|wp-includes/).* [NC]
RewriteRule .* – [F,NS,L]
#AIOWPS_FORBID_PROXY_COMMENTS_END

I also have the same problem…

The error mentioned above happes when I try to backup to DropBox

I checked the table and there were over 150K failed login records.
Could you please implement some warning in case of large number of failed logins?

> That memory you mentioned where did you increase it from?
In .htaccess file. I created phpinfo() and checked that it is working.
I doubt that increasing the memory could help. Anyway, what amount of memory you advise me to set?

Could it be due to the huge amount of failed login messsages? How to clean them?

Well, I was not insisting on using Github.
I just gave you examples, where users were shown contributing Lang files.

My key point was not to move your development to GitHub, but to ask you to include Lang files in the /languages folders so that users can start using translation right after installation.

If the Lang file is incomplete then it will motivate users to contribute translations.
Right now it is not clear for users where and how to add translation!

> What are the benefits (and disadvantages) of moving to git from subversion?
I gave you links to Github just to show examples of localization process.

Advantage of GitHub over other code hosters is it social attraction for users. GitHub UI is very user friendly.
I don’t want to start holy war. Just in my opinion GitHub is mainstream currently…
I personally don’t know even how to contribute to SVN based projects. Somehow it is inconvenient as it lacks UI simplicity…

> I should include all translations with the code?
Yes!
> Even one I know to be broken?
What does it mean “broken”? If it results in functional problem, then no. If some string are not translated then it is not a big deal. Users might translate it later.
> so adding translations to new code releases is probably going to leave some strings untranslated.
No a big deal. Users who need translation will translate!
> Clearly you know about *.mo files and the principles of i18n but most people want to install the code, turn it on and have it work without doing anything further.
That is what software needed for!
See examples how users contribute translation when they need it:
https://github.com/easydigitaldownloads/Easy-Digital-Downloads/commits/master/languages
https://github.com/kregwallace/speakup-email-petitions/commits/master/languages

And many more! That is the way it is working right now!

> That’s just going to result in more support requests saying the translations don’t work.
Answer to these request such a way: “I would be glad to include updated translation if you will send me on!”. Do the programming stuff and leave translations to users!

Old users will know about it only on new release.
New users will know straight away!

Not the bet practice, but as translation is not function related it can be sometimes used.

But if your releases are frequent enough then you don’t need to use this approach. Translation will be included with new version…

If someone needs latest translation he will install it from your Github.

> I don’t feel it’s right to push a code release that simply contains a new translation file when the core code remains identical.
Besides, you can update release with lang. files without making a new version of it!

> I get the translation files donated to me sporadically and some of the version I have are very old indeed.
That is not a big problem compared to the fact, that users currently are not getting ANY translations! Incomplete translation motivates users to update them!
That is the way most plugins I use are working!

> I don’t feel it’s right to push a code release that simply contains a new translation file when the core code remains identical.
You don’t need to do that. Push new localization updates with new version of software.

> Access to all the i18n files that have been submitted to me are available here
I was lucky to find this link as I wanted to start translation from zero!

You should definitely include all translations to release!
Besides, moving to GIThub will also be good for development of the project!