HTML5 Responsive Notify 2 Support Product Page
Responsive Notify with App Connect
Reported 27 Dec 2018 08:09:49
1
has this problem
27 Dec 2018 08:09:49 David Woolley posted:
I can't get Responsive Notify to work on a form mailer using an App Connect static event.I have the form submission working with a Reset dynamic event, as described in your video:
"Sending Form Data to Email". As soon as I add the Notify behavior, the Reset does not work either - the form still sends, but does not clear the fields.
When I remove the Notify event, the form sends then resets.
Chrome Dev Tools displays this error:
Exception: TypeError: jQuery.dmxNotify is not a function at dmxNotifyAction ...
I tried reinstalling Responsive Notify 2 & DMXzone Mailer, but no change.
I really do need the users to get some sort of notification that the form has been submitted and emailed.
I do have another website setup with a form to email, setup in exactly the same way with App Connect, where the Notify is working correctly.
Another issue - when I try to edit the Notify behavior, this javascript error appears, then deletes the title & description:
"While executing inspectBehavior in Control HTML5 Responsive Notify.htm, a JavaScript error occurred."
Deleted the wincache file in the configuration folder, but still get the error.
Replies
Replied 27 Dec 2018 21:39:42
27 Dec 2018 21:39:42 David Woolley replied:
I’ve solved the first problem with the Notify not showing.
There were links to 2 jQuery files – I decided to use the native Dreamweaver Bootstrap 3 for this project, which puts a jquery-1.11.3.min.js link just above the </body> tag. I removed this link, so now only using jquery-latest.pack.js in the <head>
However the javascript error is still there.
There were links to 2 jQuery files – I decided to use the native Dreamweaver Bootstrap 3 for this project, which puts a jquery-1.11.3.min.js link just above the </body> tag. I removed this link, so now only using jquery-latest.pack.js in the <head>
However the javascript error is still there.
Replied 02 Jan 2019 11:55:16
02 Jan 2019 11:55:16 Teodor Kuduschiev replied:
Please provide a link to your page, where we can check the error message.
Replied 02 Jan 2019 14:41:05
02 Jan 2019 14:41:05 David Woolley replied:
Hi Teodor
I have fixed the first issue above
The second issue:
When I try to edit the Notify behavior, this javascript error appears, then deletes the title & description:
"While executing inspectBehavior in Control HTML5 Responsive Notify.htm, a JavaScript error occurred."
Deleted the wincache file in the configuration folder, but still get the error.
I also reinstalled the Responsive Notify 2 extension.
This is an error with the extension in Dreamweaver, so you would not need to view a page.
The error shows on all my sites using the Responsive Notify 2 with App Connect & Mailer.
Cheers
Dave
I have fixed the first issue above
The second issue:
When I try to edit the Notify behavior, this javascript error appears, then deletes the title & description:
"While executing inspectBehavior in Control HTML5 Responsive Notify.htm, a JavaScript error occurred."
Deleted the wincache file in the configuration folder, but still get the error.
I also reinstalled the Responsive Notify 2 extension.
This is an error with the extension in Dreamweaver, so you would not need to view a page.
The error shows on all my sites using the Responsive Notify 2 with App Connect & Mailer.
Cheers
Dave
Replied 03 Jan 2019 09:08:06
03 Jan 2019 09:08:06 Teodor Kuduschiev replied:
For App Connect we have developed the App Connect Notifications extension: www.dmxzone.com/go/33235/app-connect-notifications
The responsive notify was used a few years back with the HTML5 Data Bindings and DW static events.
The responsive notify was used a few years back with the HTML5 Data Bindings and DW static events.
Replied 03 Jan 2019 09:22:46
03 Jan 2019 09:22:46 David Woolley replied:
Thanks Teodor - I did not realize the App Connect version was available. On my wish list!
The HTML5 version still works except for the JS error described.
I can live with that for the meantime.
Cheers
Dave
The HTML5 version still works except for the JS error described.
I can live with that for the meantime.
Cheers
Dave