NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: broche on February 04, 2016, 10:42:26 PM
-
NT 9.05
Cl 10
ST 2.43
All text fields in my application are showing the same behaviour and I use them a lot, please help.
Enter text in the text field, say one line and it saves OK
Enter multiple lines with soime blank lines in there and the text disapears before the record is saved.
I have tried this in many places in the app and all the text fileds seem to behave this way.
Brian
Am trying one of the examples now to see if it is there as well.
-
Tested on web1 sample app and duplicated the same issue.
Added a text field to the dictionary then entered data - the following seems to be true.
Enter line one, then line 2 then line three then leave a blank line
Then add another line
Text disapears
-
Hi Brian,
I don't know if this applies to your situation, but I've seen this behaviour when a text field has different definitions in the dct and the data base, for example string in the dct and varchar in the db (or maybe vice versa).
Peter
-
Thanks Peter - will check
I use Postgres as the backend but have not had this issue prior to 9.04
I allowed xHTML on those fields and that seemed toi work until I entered some more data and then the recently added data dispaeared as well.
Brian.
-
Checked the Database and the DCT and all seem in-line.
This is happening in the Sample app as well which is TPS.
-
Hi Brian,
please post your altered sample app here so I can check it please.
cheers
Bruce
-
Here is the sample app Bruce.
-
Also a link to show what is happening in my app
http://screencast.com/t/Go2fLMNjbF
-
fixed in 9.06
-
Bruce,
I'm using NT 9.06 and it does not seem to be fixed for me. Specifically, this behavior is only in IE 11. It works as expected with the latest Chrome and FireFox browsers. Can you look into this again?
Thanks,
Jeff
-
Bruce,
This seems to be fixed now, after I did a recompile. I made a change to the text on the Change buttons, and maybe this forced a specific module recompile. At this point it does seem to work in IE. I'll follow up if it happens again.
Thanks,
Jeff