Ascar
Forum Replies Created
-
Forum: Plugins
In reply to: [Email Template Designer - WP HTML Mail] Can’t save settingsI am on PHP 7.0.30 running on Ubuntu 16.4
MySQL 5.7.23
If you can spare a little time I will give you remote accessHello, @wpsolutions.
Please see if you can add a parameter to the plugin that would limit the number of emails sent. Your plugin is great, but if I have it installed on say 10 sites and I get on average 40-50 hack attempts per site – do I have to delete 500 messages every day?
We all need this kind of checkbox as in iThemes Security
And for the summary email
Thank you for your help in advance
- This reply was modified 7 years, 8 months ago by Ascar.
What plugin do you suggest that I deactivate? If I turn AIOS off there will not be Login Captcha anymore. If I have to turn SSL off then the idea of using AIOS will be defeated.
Just to make it clear – I can log in, I have access to the dashboard. I just can’t log in on the first go. When the login page loads it asks me to do some arithmetic calc e.g. enter the result of deduction of 1 from 11. When I enter 10 the page says the cookies are disabled. Then it gives me a new equation, e.g. how much is 13 + 14 and when I enter 27 it lets me in. So, I have to log in twice while I have to it just once.
Yeap, SSL certs issued by Cloudflare.
No, same problem in Chrome. This problem seems to be residing on the server side OR it has something to do with Cloudflare caching.
@mbrsolutions,
This issue seems to be specific to Firefox. I have just tried logging into dashboard in a pristine Firefox profile with 0 history and 0 add-ons installed and hit the same error message about cookies being disabled. When I entered a new calculated value I got logged in….
I will test with Chrome again to make sure it works smoothly in Chrome.
@mbrsolutions,
I mentioned in the original post that I have tested in Chrome and Firefox. My primary browser is Firefox. In fact, I have just tried Chrome and got logged in on first go. Hm, let me try a clean and fresh FF profile now.
Forum: Plugins
In reply to: [Move Login] Does not seem to work on IISHi, Greg.
Sorry for taking so long to reply.
My instance of WordPress is:
1. Single site
2. Root level install
3. WordPress is in the root directory (C:\WEBSITES\WORDPRESS\www.xyz.com) – the whole instance is installed into the folder named https://www.xyz.com<system.webServer> <rewrite> <rules><rule name="WordPress: https://www.xyz.com" patternSyntax="Wildcard"><match url="*"/><conditions><add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true"/><add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true"/></conditions><action type="Rewrite" url="index.php"/></rule><rule name="SF Move Login Rule 2" stopProcessing="true"><match url="^postpass/?$" ignoreCase="false"/><action type="Redirect" url="wp-login.php?action=postpass" redirectType="Permanent"/></rule><rule name="SF Move Login Rule 3" stopProcessing="true"><match url="^logout/?$" ignoreCase="false"/><action type="Redirect" url="wp-login.php?action=logout" redirectType="Permanent"/></rule><rule name="SF Move Login Rule 4" stopProcessing="true"><match url="^lostpassword/?$" ignoreCase="false"/><action type="Redirect" url="wp-login.php?action=lostpassword" redirectType="Permanent"/></rule><rule name="SF Move Login Rule 5" stopProcessing="true"><match url="^resetpass/?$" ignoreCase="false"/><action type="Redirect" url="wp-login.php?action=resetpass" redirectType="Permanent"/></rule><rule name="SF Move Login Rule 6" stopProcessing="true"><match url="^register/?$" ignoreCase="false"/><action type="Redirect" url="wp-login.php?action=register" redirectType="Permanent"/></rule> <rule name="SF Move Login Rule 1" stopProcessing="true"> <match url="^adminarealogin/?$" ignoreCase="false"/> <action type="Redirect" url="wp-login.php" redirectType="Permanent"/> </rule> <rule name="SF Move Login Rule 2" stopProcessing="true"> <match url="^postpass/?$" ignoreCase="false"/> <action type="Redirect" url="wp-login.php?action=postpass" redirectType="Permanent"/> </rule> <rule name="SF Move Login Rule 3" stopProcessing="true"> <match url="^logout/?$" ignoreCase="false"/> <action type="Redirect" url="wp-login.php?action=logout" redirectType="Permanent"/> </rule> <rule name="SF Move Login Rule 4" stopProcessing="true"> <match url="^lostpass/?$" ignoreCase="false"/> <action type="Redirect" url="wp-login.php?action=lostpassword" redirectType="Permanent"/> </rule> <rule name="SF Move Login Rule 5" stopProcessing="true"> <match url="^resetpass/?$" ignoreCase="false"/> <action type="Redirect" url="wp-login.php?action=resetpass" redirectType="Permanent"/> </rule> <rule name="SF Move Login Rule 6" stopProcessing="true"> <match url="^register/?$" ignoreCase="false"/> <action type="Redirect" url="wp-login.php?action=register" redirectType="Permanent"/> </rule></rules> </rewrite>
Forum: Plugins
In reply to: [Cloudflare] blank settings page. 3.0.3Good, so it is not platform (Windows/IIS) dependent.
Forum: Plugins
In reply to: [Cloudflare] blank settings page. 3.0.3API Key should contain all the information, specifically domain name
Forum: Plugins
In reply to: [Cloudflare] blank settings page. 3.0.3I forgot to mention that I am running WordPress on Windows and obviously my webserver is IIS, ver. 7
Forum: Plugins
In reply to: [Cloudflare] blank settings page. 3.0.3Hello,
I installed the WordPress plugin ver. 3.0.2 and activated it. When I open the settings screen in order to enter the API key I get only the blank grey screen without any logos, fields etc.
I cleared browser cache, deactivated – reactivated the plugin, uninstalled and reinstalled – no result. I then manually installed 1.3.25 and it worked, however after applying the update to 3.0.2 the screen again became blank and grey.
I also manually installed 3.0.1 and the screen was grey and empty.
I tried deactivating all plugins and keeping only Cloudflare plugin activated – did not work.
I run WordPress 4.6.1 with DIVI 3.0 theme, initially used PHP 5.3, but in the course of troubleshooting upgraded to ver 7.xI am on free plan at the moment, I opened a ticket #1214499 yesterday for the same issue. You can pull domain details from the ticket entry.
What may be the cause of this? Thanks for some suggestions.