Skip to main content
P
ptc-22689331-Visitor
1-Visitor
January 24, 2013
Question

moving customizations from 5.4 to 6.0

  • January 24, 2013
  • 14 replies
  • 2232 views

Wondering if anyone ran into issues upgrading customizations from 5.4 to 6.0. Could you do it on your own, or did you need external support? We have a unique application and custom folder that rest outside of the install path\custom folder. When we move forward to 6.0, the stylesheets can upgrade, but since i have APTAPPLICATION set I believe, it's not find the java dita.application object. I guess the bigger question is, how do you model customizations forward to the new release?


Thanks


Bryon Thomas

    14 replies

    Show previous replies
    L
    largyres1-Visitor
    1-Visitor
    January 24, 2013

    One of ournetwork tech handles the license server so I can't say.


    During testing it had a problem on thelocal box when I tried to add a test licensewith an additional feature. That required a support call, but I couldn't follow what the PTC tech did to restart the FLEX server and force it to recognize the new license.

    L
    largyres1-Visitor
    1-Visitor
    January 24, 2013

    Thanks all. "APTLIGATURESENABLED = no" did the trick.

    P
    ptc-22689331-VisitorAuthor
    1-Visitor
    January 25, 2013

    I was able to update my application folder with the 6.0 upgrade by comparing the 5.4 application folder with the custom, then with 6.0, and change as needed. I'm now able to find the java dita.application, however now for some reason Arbortext cant find the ditabase.pcf file in the ditabase folder. It's still listed in the dcf files as @APTAPPLICATION/com.arbortext.dita/doctypes/ditabase/ditabase.pcf. Am I missing something?

    P
    ptc-22689331-VisitorAuthor
    1-Visitor
    January 25, 2013

    Fixed it. The pcf call in sma-module was supposed to be commented out. Arbortext Editor couldn't handle there being two profile calls from the dcf, so it caput them both and defaulted to the install path. Thanks

    Terms & ConditionsCookie settingsAccessibility statement