01-21-2018, 09:57 AM
It can be difficult to know where they are coming from. Really, ever place that tries to read/write a field would have to log something, which could get messy. Generally speaking it's mostly dealt with by the fact that the intf editor these days shows you lots of such errors in the error list, and you can find them that way. But, for something like this, bringing back to life a lot of old stuff, that would require going through them all and checking them. Though that wouldn't be a bad thing, run through them and pass attention to the errors displayed.
It can't always catch them of course, since some are dynamically created, i.e. variables and such are used to build up the names of things, so the actual name isn't available at editing time.
I'll put it on the list to try to find some strategic places to log things. And actually some is already there, but not normally done because it's not THAT unusual for these things to happen, and if lots of stuff is being logged related to that it can generate a lot of output. But I'll look at it.
BTW, in that case, you can see the process is the web server. Unless you ahve written custom CML content being invoked on the web server, that almost certainly means WebRIVA, which means templates. So that slightly cuts it down. Other of course is to just bring up the log monitor program, which shows the logs live, and then bring up the IV and start interacting. When you do something and it generates errors, that's something to look at.
It can't always catch them of course, since some are dynamically created, i.e. variables and such are used to build up the names of things, so the actual name isn't available at editing time.
I'll put it on the list to try to find some strategic places to log things. And actually some is already there, but not normally done because it's not THAT unusual for these things to happen, and if lots of stuff is being logged related to that it can generate a lot of output. But I'll look at it.
BTW, in that case, you can see the process is the web server. Unless you ahve written custom CML content being invoked on the web server, that almost certainly means WebRIVA, which means templates. So that slightly cuts it down. Other of course is to just bring up the log monitor program, which shows the logs live, and then bring up the IV and start interacting. When you do something and it generates errors, that's something to look at.
Dean Roddey
Explorans limites defectum
Explorans limites defectum