Issue with Extension module of Alfresco Share

[mitpatoliya]

I have developed Alfresco share extension module with Alfresco 4.2 community version.
Now when I am trying to do same for the 4.1.1.3 Enterprise version It appears that it does not support this feature.
I am trying to hide few panels of document details page though alfresco share extension module.

When I have checked though surf-bug I see there was nothing in the section
"Extensibility Directives" for version 4.1.1.3 but in version
4.2 I was able to see listing of "widget","css","html" etc.. under same section.

[scouil]

Hi mits,

Yes, most of the markup sections don't exist yet in the enterprise version. Even in the latest 4.1.5.
You can just deploy an alfresco enterprise vanilla an look into the deployed folder to see the enterprise version of the .ftl and see if you can actually extend it with surf extensions.
I have great hopes for enterprise 4.2 though. But for now having some code compatible with both enterprise and community is still a pain.

Regards,

[ddraper]

We do understand that there could to be potential issues with customizations between versions but we are trying to move Share forward. However, it should be noted that new extensibility features added for 4.2 (such as the <@markup> sections) will not be retro-fitted into previous releases (such as 4.1.x)

[scouil]

Actually after some more investigation, the ftl are the only one that are hard to deal with cross-version.
The .get.js works perfectly fine, and you can add client-side js and css by injecting the dependencies when declaring the module.
So if you manage to write your extensions with only those and avoid the ftl (even if it does require you to generate part of the html modifications from your client-side javascript) you should be fine.

A few warnings though:
- Your client-side dependency is injected AFTER the createWidget runs. This means that changing the widget name to something you declare in you js will only work if you include the js from the ftl. Not with module dependencies.
- You can't access model variables from the javascript injected via module dependencies.

[mitpatoliya]

Thanks a lot for all of your replies. I got my mistake.
Things are sorted out I had to override the OOTB webscripts to achieve this.