Plugin interference BulletProof Security with other plugin

I installed this plugin, but it has no help instructions on what to do next or how to set it up. It has no useful help documentation on their website about what to do. I tried using logic and guessing at what should be done, but this plugin is not intuitive. Very, very poor user design and lack of user help or support information. It is very, very rare when I cannot guess how a poorly documented plugin is supposed to work.

So since I have no idea how this plugin is supposed to work and it does not work by itself. I see errors, things are not setup automatically, the support ticket page does not exist, no indication of what the problem is, no clues or help about what to do. So since this plugin is a complete disaster then assuming you managed to set it up correctly then….

Go to the BPS Security Log page and copy any Security Log entries that show what is being blocked by BPS. My suspicion is that BPS is not blocking anything and since this plugin is a complete disaster then it is probably a problem with the JS Support Ticket plugin itself.

Ok I see the general problem. The JS Support Ticket plugin ONLY works with the default WordPress Permalinks settings. This is a mistake in that plugin. All plugins should work with every/all WordPress Permalinks settings as a standard. Contact the JS Support Ticket plugin author and have them add the necessary additional code in the JS Support Ticket plugin so that all/every type of WordPress Permalinks settings will work correctly.

Oh wait a minute. After resaving Permalinks the JS Support Ticket plugin starting working correctly. So you just need to switch to the default WordPress Permalinks setting and then switch back to whichever custom permalink settings that you are actually using. Also email output was successful.

To: [email protected]
Subject: JS Tickets: New Ticket Received
Date: Wed, 13 May 2015 16:01:26 +0000
Return-Path: <[email protected]>
From: JS Support Ticket System <[email protected]>
Message-ID: <[email protected]>
X-Priority: 3
X-Mailer: PHPMailer 5.2.7 (https://github.com/PHPMailer/PHPMailer/)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hello,<br/><br/>A new support ticket <strong>test</strong> has been submitted. Ticket details.<br/><br/>Tracking ID: Npjd9hcLH<br/><br/>Email ID: [email protected]<br/><br/>Ticket message: <p>test</p><br/><br/><br/>You can manage this ticket here:<br/><a href=https://demo5.local/wp-admin/admin.php?page=ticket&layout=ticketdetail&jssupportticketid=2>Ticket Detail</a><br/><br/><span style="color: #ff0000;"><strong>*DO NOT REPLY TO THIS E-MAIL*</strong></span><br/>This is an automated e-mail message sent from our support system. Do not reply to this e-mail as we wonot receive your reply!

Clarification on what I meant by “disaster”. The JS Support Ticket plugin is very cool overall and it is doing some neat things, but if someone cannot figure out how to use a plugin then to me that qualifies as a “disaster” for both the end user and the plugin author. End users will get confused and frustrated resulting in the plugin author getting lots of complaints and users will give up on the plugin instead of trying to get it to work == disaster.

Is the issue/problem still occurring or is it resolved?

Thread Start Date: 5-12-2015 to 5-13-2015
Current Date: 5-14-2015
Comments: The JS Support Ticket plugin was tested with the BPS plugin and there were no conflicts or issues found. Both plugins work together without any problems.

Non-BPS plugin issue. This thread has been resolved.

Thread Start Date: 5-12-2015 to 5-13-2015
Current Date: 5-18-2015
Comments: The JS Support Ticket plugin was tested with the BPS plugin and there were no conflicts or issues found. Both plugins work together without any problems. The BPS plugin was also tested by the JS Support Ticket plugin author and no conflicts/issues/problems were found.