I remember a few years ago now working on a Knowledge Base (for IBM, no less!) and the big hassle for us developers was the fact the actual content was stored in one RT field.
It was a multi-db app and the original developer decided to do all the linking using replica-ids instead of dbname. So inside all the content (13000 documents!) all the links to other docs were done on docid/replicaid, which made life very interesting when we had to make a new version of the knowledge base for a new version of the application that it was supporting.
In the end we bought a third party plugin (can't remember the name of it) to allow us to do some kind of automation with the rt field, e.g. creating a link to an entry in the Glossary database, but of course we couldn't put the newly created link in the current position of the cursor, it had to go in the top and the content developer had to cut and paste the link where they wanted it.
So any banging of heads against the wall about rich text fields, just know that you're not the only one to have gone there. :)
Rich text...arrggghhh!!!!!!
I remember a few years ago now working on a Knowledge Base (for IBM, no less!) and the big hassle for us developers was the fact the actual content was stored in one RT field.
It was a multi-db app and the original developer decided to do all the linking using replica-ids instead of dbname. So inside all the content (13000 documents!) all the links to other docs were done on docid/replicaid, which made life very interesting when we had to make a new version of the knowledge base for a new version of the application that it was supporting.
In the end we bought a third party plugin (can't remember the name of it) to allow us to do some kind of automation with the rt field, e.g. creating a link to an entry in the Glossary database, but of course we couldn't put the newly created link in the current position of the cursor, it had to go in the top and the content developer had to cut and paste the link where they wanted it.
So any banging of heads against the wall about rich text fields, just know that you're not the only one to have gone there. :)