nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Cannot save module in page/modules/deploy

bisana

Hi
I was trying out the link,http://localhost:8080/share/page/modules/deploy to deploy and I am getting the following error

Could not save module: "Alfresco Portlet Extension"
Could not save deployment configuration, please ensure you are authenticated. Changes will not survive server restart.‍‍

Why I am getting such error message
Thanks
Joseph John

Find more posts tagged with

Comments

hunjet

Hi Joseph John,

As David wrote:

One of the main problems that can occur when deploying modules is that different authentication mechanisms are used for WebScript and remote client calls. This means you might be authenticated to access a WebScript (i.e. the module deployment script) but not to actually persist changes to the remote client. The end result would be that modules might be deployed in application memory but would not survive a server restart.

Check his blog at http://blogs.alfresco.com/wp/ddraper/2012/01/04/extensibilty-updates-roundup/.

To avoid this error, login as administrator to Share and then in second browser's tab open deploy page (again login as administrator).

Regards,
Blaz

dnallsopp

I still get this error after logging into Share as admin and re-opening the Module Deployment page in a new tab. The new tab doesn't ask me to authenticate again.

d_franz

I have the same Problem. Do I have to do something within the Alfresco Explorer to set a Module static?

ddraper

The error message is something of a "catch all" and doesn't necessarily indicate that you're not authenticated, just that the save wasn't possible. If you're running in automatic module deployment then you won't actually need to save anything (all available modules will automatically be deployed on startup). Also, it's worth noting that it's not the Share authentication but the "WebScript" authentication that is required… you should be prompted with a basic authentication popup when viewing the module deployment page. I think its fair to say that we need to make some improvements to the module deployment page (I'd actually like to make an Admin Console page for it in Share). Hopefully I'll get a chance to work on this soon.

A silly question, but have you checked whether or not your deployed modules *are* actually surviving a server restart? Also, it might be worth you raising a JIRA issue to track this - if you do, please provide as much information as possible.

Many thanks,
Dave

d_franz

After a server-restart the module wasn’t working. So, in the moment I had to apply it after every restart.
Now I found out that my code for the auto- deployment was wrong. With the new Code in share-config-costume.xml it is applied after every start:

    <config evaluator="string-compare" condition="WebFramework">
         <web-framework>
            <module-deployment>
                <enable-auto-deploy-modules>true</enable-auto-deploy-modules>
                <mode>auto</mode>
            </module-deployment>
        </web-framework>
   </config>‍‍‍‍‍‍‍‍

Should it usually survive a restart without auto-deployment?

ddraper

If you're running in auto deployment mode then it's not so much a case of your modules "surviving a restart" as the fact they'll be automatically deployed at startup anyway - so they will be deployed and in effect.

Regards,
Dave