Subassets won't publish and are giving 404's in publish instance

Forum|Forum|1 year ago
November 14, 2024
2 replies
1670 views

We have created a feature that needs access to each asset's subassets. But our subassets are not showing up in publish. We do not have a publish option on the subassets folder. Treeactivation does not seem to be working either. And when we ran the subassets through the ActivationModel workflow, they each have an indicator that makes it appear as if they are published, yet they still do not show up in Publish - they all throw 404's.

Is this a bug or is there a way to make subassets available on Publish?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Tethich

Are you using Dispatcher in local ? Cause it might be some rule there that forbids on remote env access to some path from assets or somethig. Can you check your .any files ?

Saravanan_Dharmaraj

Community Advisor

@laniweisbart Have you seen the log in replication queue and do you see error in the log when you did Tree activation?

L

laniweisbartAuthor

Level 2

I was able to get some subassets to publish via tree activation but we are still getting 404's on publish. Are there certain permissions needed to make subassets available on publish?

Tethich

Community Advisor

Do you have a way to visually access the publish instance data ? I believe in AEMaaCS you can have the Repository Browser. And sometimes in on-prem publish it can also be available if you can like open with /login path. My aim is to actually confirm the assets are not there.

Tethich

Community Advisor

Do you have AEMaaCS or on-prem ? Does the issue happen in local as well ?

L

laniweisbartAuthor

Level 2

We are on-prem. We are currently on Service pack 21 and also using Asset Share 3.8.4.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded