XSLT Refactoring: Only available in "Developer" but not in "Editor" mode

[Frank Ralf]

Hi,

Contrary to the documentation (XSLT Editor, XSLT Refactoring Actions, XSLT Refactoring) on my machine the XSLT Refactoring Actions are only available when I start oXygen in "Developer" mode, not in "Editor" mode. I expected the "Editor" mode to be the full-fledged oXygen mode that combines "Author" and "Developer" features. Am I doing something wrong?

Best regards,
Frank

(oXygen 18.1 - Windows 7)

[Radu]

Hi Frank,

Not sure why this does not work for you.
Oxygen XML Editor may not share the same global preferences with XML Developer or Author.
Are you referring to custom XSLT refactoring scripts you implemented? If so, where did you add those scripts? Did you create a custom folder and add it to the Preferences->"XML / XML Refactoring" page? Or did you create the custom refactoring scripts at framework level? Or did you just copy them to the "OXYGEN_INSTALL_DIR\refactoring" folder?
Or do you mean that even the default XSLT refactoring scripts we ship do not appear in the "XML Refactoring" dialog?

Regards,
Radu

[Frank Ralf]

Hi Radu,

Thanks for your quick reply. I made no customization. The problem was that the XSLT refactoring actions didn't show in the context menu. But I think I found the culprit. I had imported my preferred global options (dating back to oXygen 16 or even 15). After I reset the global options everything worked as expected. I still have to look what exactly caused this strange behavior.

Kind regards,
Frank

[Frank Ralf]

Update:

I have looked through the changes I made to global options but could not find any related to XSLT refactoring that could have caused this strange behavior. Could the fact that I imported global options from an oXygen Author version (16.1) to an Editor version (18.1) be the reason?

Frank

[Radu]

Hi Frank,

I would somehow need to reproduce this on my side. If you write us an email (support@oxygenxml.com), give us some steps and an XML file to import on my side I could try to look into it.

Regards,
Radu

[Frank Ralf]

Hi Radu,

Thanks for looking into this. I've send you the exported global options file.

Best regards,
Frank

[Radu]

Hi,

Thanks for the samples.I answered via email. I'm also updating this forum post.
So what I think happened is that you exported your global options from an "XML Author" installation and then you imported them in an "XML Editor" installation.
If you look in the XML Author Preferences->"File Types" page it maps the "xsl" extension to the "XML Editor" because it lacks an internal XSLT editor. This particular preferences page was saved in the XML document and then ported to the "XML Editor" so that the "xsl" extension became there associated to the "XML Editor" type.
We have an internal issue logged in to avoid such problems so probably in a future version this kind of problem will not occur anymore.

Regards,
Radu

[Frank Ralf]

Many thanks for your fix and for reporting the solution here in the forum, Radu!

Best regards,
Frank