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.

External Invited Users aren't Enabled 4.0d

jtrask

Hello,

The following bug is occurring with our installation of Alfresco Community 4.0d:

https://issues.alfresco.com/jira/browse/ALF-12242

The bug has been changed to "Fixed" for Alfresco Enterprise 4.0.1, however Alfresco Community 4.0d still exhibits this bug.

How can you tell when bug fixes are also applied to Alfresco Community Version, or how can I grab the patch and apply it to the Alfresco Community 4.0d source and re-compile it for our environment?

Find more posts tagged with

Comments

rays

Hi,

Same question from us. Can someone with knowledge please advise us? This error is preventing us from upgrading currently.

Thanks, in advance, for your support.

Ray

rays

Same question from us. Can someone with knowledge please advise us? This error is preventing us from upgrading currently.

After starting over from a known good state (Alfresco 3.4d installation with external invites verified as working as expected) and upgrading to 4.0d using the replacement of alfresco.war and share.war method, editing out the resulting siteLoadPatch ban bug after first re-start, I was able to complete the entire upgrade procedure with external invites working as expected at the end of the process.

I have been unable to ascertain what was done in the previous upgrade attempt which caused the external invites to fail so was unable to rectify that attempt.

:?

mrogers

ALF-12242 was merged to HEAD on 13th April.

rays

ALF-12242 was merged to HEAD on 13th April.

Is there any chance that a 4.0e CE version (or later!) might be released any time soon which would release this bug fix to the wider community?

Thanks