Source evidence

Plugin Conflicts

Project Force Field · support · 2014-04-18T14:58:00+00:00

Project Force Field plugin evidence original source source API

complaintsentiment

mediumseverity

0.93relevance

3replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 20 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

16 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

Faison unresolved

I want to make this thread a place to list out known plugin conflicts with Project Force Field, so that I can figure out how to fix the issues in the future. WordPress HTTPS – If you need to use WordPress HTTPS, don’t use Project Force Field for now. Certain settings in WordPress HTTPS combined with Project Force Field make the login process jarring and sometimes impossible. I’ll add a note when the conflict is resolved. Please reply to this message if you find any conflicts. Thanks, Faison https://wordpress.org/plugins/project-force-field/ A conflict with Ajax login widget in s2Members Pro was reported here: http://wordpress.org/support/topic/no-member-i-suppose FYI: I don’t use the WordPress HTTPS plugin on any of my sites, but on several sites I do have both the WordPress Address and Site Address (under General Settings) set to https://mysitename.com After activating the Project Force Field plugin in those sites, the sites no longer open using SSL. Deactivating the plugin, however, restores the sites to the correct https mode. Project Force Field is a great (and much needed) plugin. Thanks! Thank you for reporting. I have a site that I can use to test out and work out the issue.

Commercial Context

Opportunity

trust and abuse-prevention operations

Brute Force abuse-prevention assurance for keeping sites trusted, protected, and recoverable

Buyer: site owners, agencies, and maintenance teams

Wedge: test brute force lockouts, bot/spam defenses, risky access changes, and incident alerts

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Plugin Conflicts: users show bugs, compatibility, missing feature pain that may indicate a product gap.

Evidence quote: Plugin Conflicts I want to make this thread a place to list out known plugin conflicts with Project Force Field, so that I can figure out how to fix the issues in the future.

Affected feature: restore

bugs compatibility missing feature support

Plugin

API

Project Force Field

20 active installs · 3.6K downloads · rating 92.0

apache brute force brute force attack brute force protection modrewrite

Comments

3 shown

Faison 2014-04-23T03:15:00+00:00

A conflict with Ajax login widget in s2Members Pro was reported here: http://wordpress.org/support/topic/no-member-i-suppose

KevinABarnes 2014-05-04T12:06:00+00:00

FYI: I don’t use the WordPress HTTPS plugin on any of my sites, but on several sites I do have both the WordPress Address and Site Address (under General Settings) set to https://mysitename.com After activating the Project Force Field plugin in those sites, the sites no longer open using SSL. Deactivating the plugin, however, restores the sites to the correct https mode. Project Force Field is a great (and much needed) plugin. Thanks!

Faison 2014-05-06T17:01:00+00:00

Thank you for reporting. I have a site that I can use to test out and work out the issue.