I'm creating a new login routine today, and was setting up the Security Provider Executor to handle this and I wanted to create two different possible notifications using HTML5 Responsive Notify extension - one for onLoginFailed and a different one for onInvalid.

The first indication of a problem was after I had set up the first one for onInvalid and was attempting to set up the second notification for onLoginFailed. I clicked the event for onLoginFailed, then Control HTML5 Responsive Notify, and as soon as that dialog came up, the fields were already populated with the notification I had already set up for onInvalid. Hmm... is that supposed to happen?

I went ahead and filled in the notification I wanted for onLoginFailed and then clicked on. As soon as I did, I got a javascript Dreamweaver error:



From this point on, I get this error whenever I try and edit either of the onLoginFailed or onInvalid notify messages I set up. If I click the ok button on the error, the edit dialog for HTML5 Responsive Notify only shows the notification for the second one I set up.

Are you not able to use two different responsive notify messages within the same behavior connector or is this a bug?

Can you offer any help or suggestions?

Hi Steve,
There is no any limit on how many events you can use the responsive notify.
Please try clearing your DW Cache, as the error you see only points to a corrupted cache file: www.dmxzone.com/go/16740/clearing-dreamweaver-s-cache/

I cleared my cache, but I'm still getting this same error any time I try and edit a responsive notify event in the behavior connector.

You can also try reinstalling the extension and applying it once again.

I did a little bit more testing, and the error does not come up at all if there is only one behavior connector event. It only happens when there is more than one event in the behavior connector. I don't know if that tells you anything but there it is....

Hi Steve,
We tried to replicate the issue on our machines but there seems to be no problems here adding multiple behaviors. Could you please email your page/code to so we can check it?

It seems to have had something to do with the order in which I created the multiple behaviors, but I have had a hard time repeating this. I remove all behaviors and the recreated them, and that somehow seemed to have resolved the problem.