Distributing cc_config file, and effects

Questions about XML that are not covered by the other forums should go here.
akmenting
Posts: 8

Distributing cc_config file, and effects

Tue Jan 10, 2017 9:24 pm

Hello-

I modified our cc_config file to exclude certain elements for selection - I'm new to config files and I have few questions before distributing the files to the writers (they were just loaded with oXygen 18, so they are starting from scratch):

[*]I only modified the excludeElements list for now, but if I need to modify this again in the future, will there be any "side effects" of distributing the new file for the writers? For example, if the writers have customized x, y, or z in the UI or elsewhere (not in the cc_config file), they need to do that again.
[*]Is the Global Options xml file only UI preferences, or does that have a role with the config file as well?
[*]What is the easiest way to distribute the new cc_config file? I could only think of emailing the file and requesting that the writers copy the file over to the correct resources folder locations. Is there a better way?

Many thanks,

Abby
alex_jitianu
Posts: 537

Re: Distributing cc_config file, and effects

Wed Jan 11, 2017 1:08 pm

Hello Abby,

[*]I only modified the excludeElements list for now, but if I need to modify this again in the future, will there be any "side effects" of distributing the new file for the writers? For example, if the writers have customized x, y, or z in the UI or elsewhere (not in the cc_config file), they need to do that again.

The cc_config.xml file is a customization layer. When you'll deploy a new version it will apply without interfering with the writers settings.
[*]Is the Global Options xml file only UI preferences, or does that have a role with the config file as well?

It has no connection with the content completion configuration file (cc_config.xml). All the options a writer will make inside Preferences will be stored inside this "Global Options" file. As a side note, options can be shared by using projects (perhaps you will find it useful to ensure that your writes are using the same set of options).
[*]What is the easiest way to distribute the new cc_config file? I could only think of emailing the file and requesting that the writers copy the file over to the correct resources folder locations. Is there a better way?

This configuration file resides inside the framework so I guess you could go with one of the recommended way of Sharing a Framework. Also, if you are making changes to a built-in framework it is better to extend it and Sharing the Extended Document Type.

Best regards,
Alex
akmenting
Posts: 8

Re: Distributing cc_config file, and effects

Thu Jan 12, 2017 8:16 pm

Thank you. I was able to remove the elements from the content completion menu and the elements menu by creating a dita extension file, but I was wondering why my rejectElements code in the cc_config file did not work on it's own - what am I doing wrong here?

Code: Select all

<!--
       Element Proposals
    -->      
    <elementProposals path="section" insertElements="title p"/>
   <elementProposals rejectElements="abstract" />
   <elementProposals rejectElements="apiname" />
   <elementProposals rejectElements="bodydiv" />
   <elementProposals rejectElements="boolean" />
   <elementProposals rejectElements="cmdname" />
   <elementProposals rejectElements="coderef" />
   <elementProposals rejectElements="conbodydiv" />
   <elementProposals rejectElements="critdates" />
   <elementProposals rejectElements="delim" />
   <elementProposals rejectElements="figgroup" />
   <elementProposals rejectElements="foreign" />
   <elementProposals rejectElements="fragment" />
   <elementProposals rejectElements="fragref" />
   <elementProposals rejectElements="itemgroup" />
   <elementProposals rejectElements="kwd" />
   <elementProposals rejectElements="linkinfo" />
   <elementProposals rejectElements="linklist" />
   <elementProposals rejectElements="linkpool" />
alex_jitianu
Posts: 537

Re: Distributing cc_config file, and effects

Fri Jan 13, 2017 3:47 pm

Hi,

Apparently, <elementProposals> do not stack together so your elements will override one another. I'll have a look to see if it is something that we can improve on the loading part or, at least, make the documentation clear. Meanwhile, you should group them all like this:

Code: Select all

<elementProposals rejectElements="abstract apiname bodydiv boolean" />


Best regards,
Alex

Return to “General XML Questions”

Who is online

Users browsing this forum: No registered users and 0 guests