.framework in oxygen24 and oxygen26 for a custom insert operation

[vishwavaranasi]

image2022-9-12_19-8-18.png (3.35 KiB) Viewed 259 times

Hello Team ,
We have a custom insert image operation for the below

image2022-9-12_19-8-18.png (3.35 KiB) Viewed 259 times

our .framework file distributed via add-ons and the custom operation works fine in oxygen 24 version.
here is the entry

Code: Select all

<poPatch>
        <field name="fieldPath">
            <String>authorExtensionDescriptor/actionDescriptors/[11]/actionModes</String>
        </field>
        <field name="index">
            <Integer>0</Integer>
        </field>
        <field name="value">
            <actionMode>
                <field name="xpathCondition">
                    <String>oxy:allows-child-element("*", "class", " topic/image ")</String>
                </field>
               <field name="argValues">
                  <serializableOrderedMap/>
               </field>
               <field name="operationID">
                <String>com.custom.operations.InsertImageOperation</String>
               </field>
            </actionMode>
        </field>
        <field name="patchHandling">
            <String>addIndex</String>
        </field>
        <field name="anchor">
            <null/>
        </field>
</poPatch>

The mapping of the operation shows in oxygen as below in oxygen 24 - showing correctly our mapped operation

oxygen24.png (47.22 KiB) Viewed 259 times

where as when we installed same framework file to oxygen 26 - showing 2 entries - our custom is in 2 entry
entry 1 is oxygen default and entry 2 - which is pointing to our custom insert - because of these 2 entries in oxygen 26 the insert image showing oxygen default instead our custom.

oxygen26.png (75.61 KiB) Viewed 259 times

would you please help us to make sure the .framework file works for both oxygen 24 and oxygen 26 version.

[Radu]

Hi,
Oxygen 24 is in our end of life stage so we no longer officially support it in any way (including technical support, security patches, fixes):
https://www.oxygenxml.com/eol.html

Instead of creating your own "insert.my.image" action and using it in the content completion, toolbars and menus instead of the original "insert.image", you edited the original "insert.image" action and changed the custom operation that it calls. This indeed saves a patch with your changes in the framework. Later on I think probably in a newer Oxygen version the base "insert.image" action was changed by us and its xpath was changed. And somehow now there are problems as Oxygen is unable to correctly apply the patch so that it works both with Oxygen 24 and 26.1 (or our latest Oxygen

As possible workarounds I see:
- Give up support for Oxygen 24 and support only Oxygen 26 or newer, making changes to the framework extension only in Oxygen 26.
- Create in Oxygen 24 your own custom action "insert.my.image" in your framework extension and use that in all places (toolbars, menus, content completion window) instead of editing the base "insert.image" action.
- Keep two extension framework files, one for Oxygen 24 and one for Oxygen 26 and maybe two add-ons to install your frameworks, one for each Oxygen version.

Regards,
Radu

[vishwavaranasi]

Thanks for the inputs Radu.
We will consider moving to newer version of oxygen.
Thanks,
Vishwa