Re: [Serna] Migrating Custom DITA Templates from 3.4 to 3.5.1

Paul Antonov wrote:
> 
> Eliot,
> 
> there are no implications, except that you should place .sdt files in 
> locations where they will be found (if you want to keep your project 
> outside Serna, use 'Additional plugins' path setting), and that it is a 
> best practice to use $TEMPLATE_PATH for building relative paths for 
> files which are stored inside your plugin folder. Nothing prevents you 
> to use absolute paths and/or $DATA_DIR relative paths, however.

I think the documentation may be out of date. Looking at the entry for 
Document Template Development in the 3.5 Developer's Guide (via the 
online help), there is only this statement about finding templates:

"In order to be visible for Serna, the document templates must reside 
either in directory sernaInstallationPath/xml/templates or in any 
subdirectory of sernaInstallationPath/plugins and have suffix *.sdt."

It doesn't say anything about the the additional plugins path, although 
I do see that in the options.

The "additional plugins" path is very good--just the right way to do it, 
I think.

I removed my templates from the Serna xml/ directory and added their 
base location to the additional plugins path. I verified that my 
templates show up in the File->New... dialog and was able to create a 
new doc with the template with no errors on open.

Looking at the document properties (also very nice) I see that it's 
using the correct template and my local Toolkit catalogs are in the 
catalog list.

However, I still get no elements listed in the insertion list for new 
elements (e.g., ctrl+enter) and the "revalidate" option is still greyed out.

So something else is going on. I am getting this same behavior with 3.4 
so I suspect it's something not related to the template organization.

Thanks,

Eliot

--

-- 
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 610.631.6770
www.reallysi.com
www.rsuitecms.com