DMXzone Database Connector PHP Support Product Page

Answered

flexdmx script error

Asked 30 Mar 2016 14:33:03
1
has this question
30 Mar 2016 14:33:03 Mehmet Sinan akdeniz posted:
I am getting ERROR like this
The following JavaScript error(s) occurred
........Application:Adobe DreamweaverCS6:Cofiguration:Shared:FlevDMX:script:anchoreDiv-sr-str.js"(error 2).

Replies

Replied 31 Mar 2016 08:42:33
31 Mar 2016 08:42:33 Teodor Kuduschiev replied:
Hello Mehmet,
When exactly are you seeing this error?
Replied 31 Mar 2016 10:10:35
31 Mar 2016 10:10:35 Mehmet Sinan akdeniz replied:
Teodor

Here you can see the error in my video below

www.sinanakdeniz.com/dmxError/errorDMX.mp4

Thanks

Replied 01 Apr 2016 23:54:48
01 Apr 2016 23:54:48 Mehmet Sinan akdeniz replied:
There is no SOLUTION for this problem?
Replied 04 Apr 2016 08:58:08
04 Apr 2016 08:58:08 Teodor Kuduschiev replied:
Hello,
this is not an error related to any of our extensions.
Replied 05 Apr 2016 12:33:30
05 Apr 2016 12:33:30 Mehmet Sinan akdeniz replied:
Teodor,

I bought every of your extensions and been a member since dec. 2002. Check my account you will see. Last time i upgraded some of them and bought new ones. You saw video and saying that this is NOT RELATED YOUR EXTENSION. Have you seen video? It says "FlevDMX"

This is really GOOD SUPPORT, and THANK YOU.
I NEVER USE and BUY YOUR EXTENSION ANYMORE. I DELETED DMXZONE.COM but i will keep my account because IPAID MORE THEN $750
Thanks again NOT or CAN NOT SOLVE my or your PROBLEM
This reply was removed on 4/5/2016 12:39:28 PM.
See the changelog
Replied 05 Apr 2016 12:49:56
05 Apr 2016 12:49:56 Teodor Kuduschiev replied:
Of course i have seen the video and i've investigated the error you are getting.
As i explained this is nothing to do with our extensions. You have installed some really old 3rd party extension(s) produced by "FlevOOware", like (scroller genie, layer genie, Persistent Layer Pro and many others) which are 15 YEARS OLD and their producer - FlevOOware is not supporting them anymore.
They are causing the issue.

Reply to this topic