Hello,
I've a trouble configuring the presentation of the steps. In fact in a test case I have a step with about 8600 characters and 213 lines long. When I have a look in the database, it appears to be complete and embedded in the steps column of the tcversions table.
Once my test case is edited, when I go back on it, I only get the first 3000 characters displayed.
Is there a setting to configure the number of lines/chars visibles for the test case? Does this comes from the driver for the database?
Any clue?
testlink 1.7.4 on SQL2005 - heigh of steps
Moderators: Amaradana, TurboPT, TL Developers
Hello havlatm,
Thanks for the answer. I looked in the 1.8 installation doc and didn't see anything which could apply to me about the setting I'm looking for. I mean that for me it's only a presentation of the data (which is complete in the database - no troubles of UTF-8 coding) since it has been commited correctly in the database. If there was a trouble shouldn't it be on both parts: writing and reading in MSSQL 2005? As I wrote before I can see the testcase completly and embedded in the steps column of the tcversions table of the TestLink database but it is cut off before the end in the middle of a word while viewing or editing the testcase.
So, Is there a limitation or a setting in adodb/testlink/fckeditor to avoid this?
Regards,
Thanks for the answer. I looked in the 1.8 installation doc and didn't see anything which could apply to me about the setting I'm looking for. I mean that for me it's only a presentation of the data (which is complete in the database - no troubles of UTF-8 coding) since it has been commited correctly in the database. If there was a trouble shouldn't it be on both parts: writing and reading in MSSQL 2005? As I wrote before I can see the testcase completly and embedded in the steps column of the tcversions table of the TestLink database but it is cut off before the end in the middle of a word while viewing or editing the testcase.
So, Is there a limitation or a setting in adodb/testlink/fckeditor to avoid this?
Regards,