The following error displays in my browser console every time I try to interact with an existing form or create a new one in the back-end.
Several instances of the error happen on every click. I am not able to edit/create any forms, but I can see them all fine on the front-end.
I read http://www.chronoengine.com/faqs/56-cfv4/cfv4-other-faqs/5125-chronoformschronoconnectivity-fails-after-a-joomla-upgrade.html, but it seems to be nothing relative as I don't have "version" folders.
Error: Syntax error, unrecognized expression: #basic-{N}
jquery.min.js:2:12733
Empty string passed to getElementById().
Several instances of the error happen on every click. I am not able to edit/create any forms, but I can see them all fine on the front-end.
I read http://www.chronoengine.com/faqs/56-cfv4/cfv4-other-faqs/5125-chronoformschronoconnectivity-fails-after-a-joomla-upgrade.html, but it seems to be nothing relative as I don't have "version" folders.
Hello yaegerdesign,
I'm not a Chrono professional, but after checking your new post, I think that the following links may help:
Using jQuery maskMoney with CFV5
P.S: I'm just an automated service😉
I'm not a Chrono professional, but after checking your new post, I think that the following links may help:
Using jQuery maskMoney with CFV5
P.S: I'm just an automated service😉
Hi yaegerdesign,
This isn't the version problem, as you say, that is a CFv4 issue.
What has happened is that is a recent release Max replaced the string {N} with _XNX_ in all of the actions as {N} gave an irritating JavaScript warning.
All the standard actions should have been replaced when you upgrade - any custom actions like the TCPDF action, or my [GH] custom actions need to be upgraded separately. Are you using any of those?
Bob
This isn't the version problem, as you say, that is a CFv4 issue.
What has happened is that is a recent release Max replaced the string {N} with _XNX_ in all of the actions as {N} gave an irritating JavaScript warning.
All the standard actions should have been replaced when you upgrade - any custom actions like the TCPDF action, or my [GH] custom actions need to be upgraded separately. Are you using any of those?
Bob
It seems that what you suggest isn't the root cause of blocking the back-end functionality, but I could try uploading the component again to see if that clears it.
The line that keeps getting repeated on every mouse click (i.e. "save", "close", or some random place on the page) is the following:
In the console, the first few clicks cause 2x of above, next few cause 4x, next few cause 8x, etc. The errors keep multiplying.
The line that keeps getting repeated on every mouse click (i.e. "save", "close", or some random place on the page) is the following:
Empty string passed to getElementById(). jquery.min.js:2:24932
In the console, the first few clicks cause 2x of above, next few cause 4x, next few cause 8x, etc. The errors keep multiplying.
I, also, get a few of:
Notice the change in last number. Then the errors go back to previous number.
Empty string passed to getElementById(). jquery.min.js:2:24930
Notice the change in last number. Then the errors go back to previous number.
Further testing reveals that all of the buttons on the CF dashboard work fine, and the buttons on those inner pages work fine (settings, install language, install action, etc.). It is only the "new" or "edit" form pages that do not work.
It seems that what you suggest isn't the root cause of blocking the back-end functionality...
Maybe I was wrong on this as the empty strings are just WARNINGS. The "basic-{N}" message is an actual ERROR:
Error: Syntax error, unrecognized expression: #basic-{N} jquery.min.js:2:12733
t</fa.error()
jquery.min.js:2
t</fa.tokenize()
jquery.min.js:2
t</fa.select()
jquery.min.js:2
fa()
jquery.min.js:2
a.find()
jquery-migrate.min.js:2
.find()
jquery.min.js:2
a.fn.find()
jquery-migrate.min.js:2
n.fn.init()
jquery.min.js:2
a.fn.init()
jquery-migrate.min.js:2
n()
jquery.min.js:2
t.prototype.refresh/n<()
bootstrap.min.js:8
n.prototype.map/<()
jquery.min.js:2
.map()
jquery.min.js:2
n.prototype.map()
jquery.min.js:2
t.prototype.refresh()
bootstrap.min.js:8
t()
bootstrap.min.js:8
e.fn.scrollspy/<()
bootstrap.min.js:8
.each()
jquery.min.js:2
n.prototype.each()
jquery.min.js:2
e.fn.scrollspy()
bootstrap.min.js:8
processScrollInit()
template.js:141
<anonymous>
template.js:124
n.Callbacks/i()
jquery.min.js:2
n.Callbacks/j.fireWith()
jquery.min.js:2
.ready()
jquery.min.js:2
K()
jquery.min.js:2
Hi yaegerdesign,
. . . any custom actions like the TCPDF action, or my [GH] custom actions need to be upgraded separately. Are you using any of those?
Bob
. . . any custom actions like the TCPDF action, or my [GH] custom actions need to be upgraded separately. Are you using any of those?
Bob
I am definitely not using them and can't find any trace of them being installed. Where would I look?
Seems like TCPDF may be the issue as I am seeing the same thing as here:
http://www.chronoengine.com/forums/posts/t101815/p358946/chronoforms-doesnt-work-after-tcpdf-installation.html
I would just assume uninstall TCPDF as I'm not using it at the moment, but the patch may be just as good. I just need to get the quickest fix as I'm stuck for now.
http://www.chronoengine.com/forums/posts/t101815/p358946/chronoforms-doesnt-work-after-tcpdf-installation.html
I would just assume uninstall TCPDF as I'm not using it at the moment, but the patch may be just as good. I just need to get the quickest fix as I'm stuck for now.
I did a search on the server and found there was a TCPDF folder deep inside com_chronoforms5. I downloaded the TCPDF action from http://www.chronoengine.com/downloads/chronoforms.html and now all seems to be resolved!
So, now the issue is how to manage actions that you can't see? Or, how to uninstall those you don't need anymore? If there is always a patch needed, that seems like an unnecessary point of failure...
So, now the issue is how to manage actions that you can't see? Or, how to uninstall those you don't need anymore? If there is always a patch needed, that seems like an unnecessary point of failure...
Hi yaegerdesign,
You can uninstall an action by deleting the action folder. And all the installed actions are visible on the Setup Tab in the form Wizard (but not in the Simple Wizard).
Bob
You can uninstall an action by deleting the action folder. And all the installed actions are visible on the Setup Tab in the form Wizard (but not in the Simple Wizard).
Bob
I guess that's all fine and dandy when everything is working properly. I would suggest a list of installed actions in the "Install Action" section with an option to uninstall.
This topic is locked and no more replies can be posted.