You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experimenting with using Orchard Core in a headless mode with a Javascript client. I have a content type that uses the AutoRoute part so that we can get automatically created unique URLs (e.g. "The Page Name" will get slug "the-page-name"). I don't actually want Orchard to directly serve those content items at that URL path though... e.g. I want to query for it and display its content from my Javascript client but I don't want the user to be able to type in /the-page-name and have Orchard return the content item.
Is there a way to keep AutoRoute enabled but not let Orchard serve any content items directly?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm experimenting with using Orchard Core in a headless mode with a Javascript client. I have a content type that uses the AutoRoute part so that we can get automatically created unique URLs (e.g. "The Page Name" will get slug "the-page-name"). I don't actually want Orchard to directly serve those content items at that URL path though... e.g. I want to query for it and display its content from my Javascript client but I don't want the user to be able to type in /the-page-name and have Orchard return the content item.
Is there a way to keep AutoRoute enabled but not let Orchard serve any content items directly?
Beta Was this translation helpful? Give feedback.
All reactions