ModularBase

Uninstalled and reinstalled plugin. Same problem occurs.

Sorry… because you have changed all the div classes and redesigned the plugin radically, I do not have the time or inclination to alter all the CSS I have set up which worked so well on this site. I will just uninstall the plugin.

Error is gone, but plugin does not display. site: https://www.chaseo.ca/
php on main page:

‘<?php
if( function_exists(‘fa_display_slider’) ){
fa_display_slider( 241 );
}
?>’

Width set to 100% – checked box “allow slider to display in full width (will keep width/height proportions)”
Height set at 444px in box “the slider height in pixels”
Theme and Layout variations set to Default

Okay. No rush.

php:

‘<?php if( function_exists(‘FA_display_slider’) ){ FA_display_slider(241); } ?>’

Updated plugin to version 3.1.3.
Got the same as well with message in WP admin – “ERROR: Step aborted: too many attempts!”

Standout Error seemed to be this – “ERROR: Dropbox API: (401) Access token not found.”

Solution for Backup to Dropbox…
Use Tar GZip.
Delete Dropbox access code and re-authenticate with full access.
Run backup.

Worked fine on all nine sites I administer.

1 – My Time Zone in WP Settings has always been set for Toronto :
UTC time is 2014-09-19 11:36:50 – Local time is 2014-09-19 7:36:50

2 – Here is the time I logged in today :
September 19, 2014 7:31 am

3 – Here is the Failed Logins I checked as soon as I logged in :
admin 64.34.173.227 September 19, 2014 10:36 am
[% tools.ua.random() %]

4 – Last entry from the Audit Log before I logged in :
September 19, 2014 6:36 am – Notice: 64.34.173.227; User authentication failed: admin

A difference of 4 hours between the Failed Logins and the Audit Log, which is the difference between UTC and Toronto Time Zone.

Every section of the Sucuri plugin reflects my Time Zone time of 4 hours from UTC except for the Failed Logins section.
10:36 am Sept. 19th could not have happened for me yet if I logged in at 7:36 am.

I had deactivated all other plugins the night before to see if there was another plugin affecting the Sucuri plugin, and left them deactivated until after checking the Failed Logins.

Change Dropdown to Checkboxes w/ Sales Reps names and make selection required, then people cannot bypass.

“I fixed this here 978150, the new code will be available in the next version of the plugin 1.6.9, this update includes new options in the Settings and I recommend to go and check them.”

I have version 1.7.0 and the timestamp is still UTC and not my loacal time on some options such as “Failed Logins”, which are logging times that are future times, in other words, not a time which has happened yet.

Example: I login at 11:36 a.m. today and the “Failed Logins” report has failed logins occuring at 2:47 p.m. the same day (today) – which is a few hours in the future – so I am assuming that this part of the plugin still logs at UTC.

Also… is there supposed to be an option for setting the time-zone within the plugin, or does the plugin use the site’s settings for time-zone? If so, I do not see any option.

Something for investigation, perhaps?

For some unexplainable reason, it has cleared up on its own. Can login fine without issues. Plugin working admirably.
Curious…

You’re welcome. Again… very excellent plugin.

Solved the error…

Set this in .htaccess…

<ifModule mod_headers.c>
Header set X-XSS-Protection "1; mode=block"
Header always append X-Frame-Options SAMEORIGIN
Header set X-Content-Type-Options: "nosniff”
</ifModule>

In the Recommendations after performing Malware Scan, then followig recommendation link, this line…
Header set X-Content-Type-Options: nosniff”
…is missing the first quotation marks in front of nosniff.
This could be corrected.

Excellent plugin. Works like a charm.

Thanks for your speedy assistance.

I enter this in the .htaccess file on my site, as suggested…

<ifModule mod_headers.c>
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
X-Content-Type-Options: nosniff
</ifModule>

…it gives an Internal Service Error.

Hmmm… never had that in the function before and worked fine. Possibly the latest update?
Anyhow, added the suggestion and all working fine.
Thanks.

Will mark resolved.

Thanks for your quick response.
I will wait for the updated version.