• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 137 subscribers
  • Views 2226 views
  • Users 0 members are here
Options

Why is XMetaL authoring bridge changing resourceIDs to "all caps?"

CMS Administrators2

Using SDL Tridion Docs R13 and XMetaL 12 with Authoring Bridge 13.0.4115. Have not made any changes to client tools for over a year. Have not changed our XML plugin settings.

Suddenly when we check in DITA topics, <resourceID id="" changes to "all caps." This was not happening until about 2 weeks ago.

We have some resourceID CSH values that use lowercase letters in our UIs. Now they're broken when we update and check in the associated topics (and then publish).

As shown in the attached screen shot, the "demo" portion of the "demo16" ID that I entered remains in lowercase when saved in XMetaL. But then it changes to DEMO16 upon checkin.

Anyone have any ideas? Thanks!

Paul M.

Screenshot of a general discussion forum post by Paul M. describing an issue with resourceID changing to uppercase upon check-in in SDL Tridion Docs R13.

Generated Image Alt-Text
[edited by: RWS Community AI at 2:21 PM (GMT 0) on 14 Nov 2024]
emoji
Rate translation
×
Suggest better translation
×
  • 0

    Hi Paul,

    Two classic questions...

    1. First, what has changed? Although you highlight no changes like XMetaL patches and no XML Plugin settings changes. Still would be my prime subjects
    2. Second, cut the problem in smaller pieces. Use the web client (ISHCM) so you drop AuthoringBridge and XMetaL from the equation. So submit a file there and check if the plugins uppercase by also downloading the file from the web client. Or check how 'file system DITA" works in XMetaL

    Best wishes,
    Dave
  • 0

    This has happened at FICO randomly too … it's strange indeed. 
  • 0

    Hi Paul,

    It sure does sound like a "Wrike Plug-in XML setting" making the case change. I would check your xml plugin setting for the xpath of resourceid. Also If it just started happening I would compare the markup for resourceID tag from a older document to see what's different. When we first started using SDL, we ran into a lot of issues with IDs capitalizing upon checking, especially on image tags if the scope attr is not set to external it capitalizes the href, making the path invalid.