To register for the forums, please contact your Digital-Clay representative.
Anomaly
Anomaly
On all of our computers, we have documented a very interesting anomaly.
We search for a particular record, it comes up in the filter results (including the record details as usual), we open up the record. The main record interface which is a URL tab is missing the data entered (blank boxes), while the other native Digital Clay tabs are filled in as normal.
What could cause the main tab (URL) to be blank for one specific record while clearly the information was entered and is still present in the system?
We search for a particular record, it comes up in the filter results (including the record details as usual), we open up the record. The main record interface which is a URL tab is missing the data entered (blank boxes), while the other native Digital Clay tabs are filled in as normal.
What could cause the main tab (URL) to be blank for one specific record while clearly the information was entered and is still present in the system?
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Anomaly
You need to debug the code in your custom HTML addon to solve this. Probably there is something in the data it can't handle. Perhaps a special character of some sort like a quote or a backslash. (I am assuming this custom addon works fine for other records).
Re: Anomaly
The HTML works fine for all other records as far as we can tell. when we try to edit this record's information in the HTML tab, even the drop downs are not populated (like countries, cities, etc.) as well.
Re: Anomaly
If this only relates to one record (as far as we can tell), how can debugging the code of the addon help to find the issue for this specific record? the fact that even the drop down boxes are not populated seems very fishy.
Using a document template, we can see that the data that we should see in the HTML tab is in fact saved with in the system. Nevertheless, when we try to open this record, the info in the HTML tab is completely empty.
Using a document template, we can see that the data that we should see in the HTML tab is in fact saved with in the system. Nevertheless, when we try to open this record, the info in the HTML tab is completely empty.
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Anomaly
This behaviour is not fishy at all if it's a javascript bug.
Re: Anomaly
I tried to upload the file for you to take a look and it was rejected because the uploaded file was identified as a possible attack vector.
Is there an alternative way?
Is there an alternative way?
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Anomaly
Chances are that debugging your custom addon code will not be a simple matter and will probably require debugging it on the Clay system where it is running and especially with the specific record that is causing the problem. I could take a quick look at the source to see if anything comes to mind, but chances it will need to be debugged by the person that wrote the code on your system.
You can paste specific bits of the code here if you know where the problem starts, or perhaps you can use pastebin.com or similar sites for uploading/sharing files.
You can paste specific bits of the code here if you know where the problem starts, or perhaps you can use pastebin.com or similar sites for uploading/sharing files.
Re: Anomaly
The entire file of code was written by Roy Daya of Digital Clay back in ~2010 with small updates along the way. He is the only one I recall who really dealt with the file. Moshe probably reviewed it as well but we have not touched it much internally. That is why we are hesitant to take it apart too much.
Ok, will check options for sharing files.
Ok, will check options for sharing files.
Re: Anomaly
Maybe try this? https://pastebin.com/2Pd3NkXv
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Anomaly
It says it's private. In any case it's like I said, this is beyond the scope of free forum support and is a programming job.
Chances are it has to do with special characters in the specific records which aren't handled properly in the javascript code. That would be my first wild guess. But it has to be debugged on your system along with the problematic record.
You can try experimenting by changing the values in the problematic record (look for anything unusual like quotes and slashes).
Chances are it has to do with special characters in the specific records which aren't handled properly in the javascript code. That would be my first wild guess. But it has to be debugged on your system along with the problematic record.
You can try experimenting by changing the values in the problematic record (look for anything unusual like quotes and slashes).