Sami's Site: CSB - Trellix Publish
previous    next
CSB Publishing Settings   ·   Using FTP   ·   Search engines: Spiders & Robots   ·   Meta Tag, Keywords, Page Properties   ·   Frames or No-Frames?   ·   Subdirectory   ·   Working Window   ·   Design file image errors   ·   Design file will not save   ·   Publishing Errors   ·   Page Layout   ·   CSB3 & CSB4 Known Issues (Problems)   ·   CSB5 NOTES   ·   Upgrade to CSB5

Design file will not save
The design file refuses to save.  Now what do you do?!

The information on this page came from a post on the Globalscape Discussion Board.  
Etienne had a corrupted large CSB design file that would not publish and eventually would not save!  
He graciously offered advice to others that could potentially save time and effort while diagnosing problems.


I found 2 ways to sort out problems in a tlx file that are not related to this thread, but just thought I'd mention them in case someone reads this. You might already know them. They relate to the file not wanting to save, or the spell checker shutting down without completing the checkeing of all the pages in a file.

I just thought of mentioning these because I have spent many frustrating hours not knowing where to find problems, and these techniques speeded things up.
Etienne

1.   Assuming you can open the file, open the map, and systematically click on each page until you receive a message that says "Null code encountered" with some sort on coding behind it ot "Null error". That page has an error on it. There might be more than one page with an error on it. The error could be an HTML insert that CSB is not happy with. The solution is to create a new page. One can copy everything that you think is OK accross. Then delete the original page and save the tlx file, but be careful when copying from one page to another that you do not duplicate the cause of the error.
2.   Using the spell checker is also another "last resort" way of finding an error in a file that saves but has an error in it somewhere. Run the spell checker and carefully watch it progressing though the pages in the file. Write down the page name or reference number. In these cases the spell checker "boms-out" on the same page every time it is run. Now that you know which page is causing the problem, look for things such as unrecognisable characters, things pasted, HTML code entered that might not make sense to the spell checker, or even text such as the ampersand sign in the properties on the page.