Consider the case where you have the three following urls:
/foo
/bar
/baz
/foo is a vanity redirect, and should sent to content api as website_url
/bar is a section, and that section will be used by a template as the global content, but we want to use a content source that sends to site service so we can detect non-existent sections and return 404 when appropriate
/baz isn't either of the above and should 404
If resolvers supported conditional logic and could switch content sources based on the return status from the first content source, handle the error as normal, or pass on the request allowing the next lower priority resolver that still matches the pattern to handle it, this would allow cases like the one described above without the use of hard to maintain bespoke regular expressions.
Guest
I tried but I get sent to jitta website to search my error and still not getting any solution
Hi, can you reach to Arc Customer Support team? We should be able to understand and help better with your organization/environment details.
hi, I'm getting an error saying an error has occured on site service configuration when I try to access pagebuilder after running fusion start, can anyone help please
For now, please refer to the ALC documentation on how to manage these redirects: https://redirector.arcpublishing.com/alc/arc-products/contentapi/user-documentation/redirects-in-arc/
Thanks for this suggestion. We'll follow-up internally to dig into the problem this tries to solve, as there are several other plans that may address this issue. As proposed, this solution would result in multiple global content fetches which can easily increase load on APIs and degrade performance. We can explore other options.