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.

Upgraded to Community Edition 23.4 from 23.1 - Some Share Sites Stopped Working

mxc

Hi all,

I recently upgrade our Alfresco Community install via our modified docker-compose file. Straight after the upgrade I could login to share and see all my sites. I even uploaded some documents to the one site. When I log in this morning I get most of the site returning the "something's wrong with this page..." screen.

The share starts to load and then is replaced with the error page. From the javascript console I get see it is getting a 410 response to the following:

HXR GET
https://alfresco.abc.co.za/share/proxy/alfresco/slingshot/doclib/doclist/documents/site/abc/documentLibrary?max=50&filter=recentlyModifiedByMe

[HTTP/2 410 187ms]

GET
https://alfresco.abc.co.za/share/proxy/alfresco/slingshot/doclib/doclist/documents/site/abc/documentLibrary?max=50&filter=recentlyModifiedByMe

Status
410

It seems like the cache is failing to create the response? Any ides where to look for the issue? Is it Solr6? I assume it some process that ran and delete the old file but didn't create the new one? Any assistance appreciated.

Find more posts tagged with

Alfresco Content Services

Comments

mxc

Here is the json response:

{
    "status" : 
  {
    "code" : 410,
    "name" : "Gone",
    "description" : "Resource is no longer available at the server and no forwarding address is known."
  },  
  
  "message" : "Site not found: 'abc'",  
  "exception" : "",
  
  "callstack" : 
  [

  ],
  
  "server" : "",
  "time" : "30 Jan 2025, 08:58:59"
}

mxc

Ok so here is what I have found:

I can view sites in share that have their visibility set to "MODERATED". I am the create of these sites.
I get a 410 status error for PRIVATE sites. I am the creator of these sites
Other users, who are site members of the PRIVATE sites, can login and view the site. Although the "Document Library" now shows an empty page even though they were working for a while.
If I change the site visibility to "MODERATED" the sites work fine again and I can see the "Document Library" too. I used the API to do this.
If I create a new site that is PRIVATE I get the same error as for previously created PRIVATE sites
I can create new MODERATED sites just fine.
I cannot delete any site. I get an error that I lack permissions.

So it appears to be something related to permissions. The content-app works fines. I tried downgrading share to the older version but still get the error. Anyone know how to reset permissions or to change them?

mxc

Hmm not luck. There is only 1 user that is experiencing this problem and is the owner of several sites. Other users of the sites can view them just fine.

mxc

Ok the other users can still login. Its just the 1 user. He is the owner of several sites and it appears he can only see the sites set to "moderated" as opposed to "private". Other users have no problems.