Components not Reusable Components
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 25
- Joined: Wed Jul 22, 2009 10:22 pm
- Location: Colorado, USA
Components not Reusable Components
The Components tab in the DITA Reusable Components view does not list any items when working with DITA content stored in Tridion Docs. The Components tab shows a message saying "There are no reusable components of type []", followed by instructions on how to define a reusable component file, and then a bulleted list of topics in the map that have reusable components.
The root map is correctly selected in the Root map list in Maps Manager. The references in the root map that contain the reusable components all have @processing-role="resource-only".
The version of oXygen Author is 20.1. The version of Tridion Docs is 13.0.2, with SDL Tridion Docs - Authoring Bridge 13.0.2.
Please let me know what other information I can provide.
Jason
The root map is correctly selected in the Root map list in Maps Manager. The references in the root map that contain the reusable components all have @processing-role="resource-only".
The version of oXygen Author is 20.1. The version of Tridion Docs is 13.0.2, with SDL Tridion Docs - Authoring Bridge 13.0.2.
Please let me know what other information I can provide.
Jason
-
- Posts: 9451
- Joined: Fri Jul 09, 2004 5:18 pm
Re: Components not Reusable Components
Hi Jason,
Honestly we have not tested our Reusable Components list to see how it works with CMS integrations.
Is the root map also opened in the "DITA Maps Manager" view?
In the Oxygen Preferences->"Open/Find Resource" page there is also a checkbox called "Enable indexing for remote resources". Could you also check that and then go to the Reusable Components list, find the top right drop-down button which looks like a cogwheel and use the "Reindex" action?
Regards,
Radu
Honestly we have not tested our Reusable Components list to see how it works with CMS integrations.
Is the root map also opened in the "DITA Maps Manager" view?
In the Oxygen Preferences->"Open/Find Resource" page there is also a checkbox called "Enable indexing for remote resources". Could you also check that and then go to the Reusable Components list, find the top right drop-down button which looks like a cogwheel and use the "Reindex" action?
Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com
<oXygen/> XML Editor
http://www.oxygenxml.com
-
- Posts: 25
- Joined: Wed Jul 22, 2009 10:22 pm
- Location: Colorado, USA
Re: Components not Reusable Components
The root map is open in the Maps Manager view.
I changed the preference in the Oxygen Preferences->"Open/Find Resource" page so that the checkbox called "Enable indexing for remote resources" is selected. I reopened oXygen and the root map and that forced the reindexing of the map in the Reusable Components view. The results are the same as before, where the reusable components are not listed in the Components tab of that view.
Note that I don't see an option in the Reusable Components view to force the reindexing of maps. The gear icon shows just one option for "Compact mode".
I changed the preference in the Oxygen Preferences->"Open/Find Resource" page so that the checkbox called "Enable indexing for remote resources" is selected. I reopened oXygen and the root map and that forced the reindexing of the map in the Reusable Components view. The results are the same as before, where the reusable components are not listed in the Components tab of that view.
Note that I don't see an option in the Reusable Components view to force the reindexing of maps. The gear icon shows just one option for "Compact mode".
-
- Posts: 1016
- Joined: Wed Nov 16, 2005 11:11 am
Re: Components not Reusable Components
Post by alex_jitianu »
Hi Jason,
I suspect that it has something to do with the default ignore filters. Please go to Options->Preferences... on page Open/Find Resource. On the Ignore content of these files* remove the token: */temp/* . Exit with OK and check if the components are presented.
Best regards,
Alex
I suspect that it has something to do with the default ignore filters. Please go to Options->Preferences... on page Open/Find Resource. On the Ignore content of these files* remove the token: */temp/* . Exit with OK and check if the components are presented.
Best regards,
Alex
-
- Posts: 25
- Joined: Wed Jul 22, 2009 10:22 pm
- Location: Colorado, USA
Re: Components not Reusable Components
Thanks for the suggestion. The change was applied but the behavior remains as before. In the Ignore content of these files field, */temp/*, was removed. I tried removing all values from that field to see if that made a difference but it did not change the behavior.
-
- Posts: 1016
- Joined: Wed Nov 16, 2005 11:11 am
Re: Components not Reusable Components
Post by alex_jitianu »
Hi Jason,
I've tested some more and I've found another possible cause. Apparently, we need these topics to have either an "xml" or a "dita" extension and inside SDL they don't have any extension whatsoever. I will add an issue to fix this because we already know that they are DITA reusable topics so the extension should not matter and we will include the fix in version 21.1 which is due to be released in a couple of week. Please let me know if you would like a beta version so you can confirm that it's working before the official release.
Best regards,
Alex
I've tested some more and I've found another possible cause. Apparently, we need these topics to have either an "xml" or a "dita" extension and inside SDL they don't have any extension whatsoever. I will add an issue to fix this because we already know that they are DITA reusable topics so the extension should not matter and we will include the fix in version 21.1 which is due to be released in a couple of week. Please let me know if you would like a beta version so you can confirm that it's working before the official release.
Best regards,
Alex
-
- Posts: 419
- Joined: Mon May 09, 2016 9:37 am
Re: Components not Reusable Components
Post by sorin_carbunaru »
Hello,
Just wanted to update this thread by announcing that oXygen 21.1 is out now, and it comes with the fix that Alex mentioned in the previous post.
Best wishes,
Sorin Carbunaru
oXygen XML
Just wanted to update this thread by announcing that oXygen 21.1 is out now, and it comes with the fix that Alex mentioned in the previous post.
Best wishes,
Sorin Carbunaru
oXygen XML
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service