Try our conversational search powered by Generative AI!
AI OnAI Off
ContentDeliveryApi blocks HTTP 404 error
Hi Niklas ,
Do you set access right for For All sites in Admin Mode ?
You need to have permission on For All Sites in order to access the block
Edited,
Aug 03, 2018 10:09
Yep. On for all sites, root, Start, actually everything has the same access rights except Recycle Bin. Even the block itself has the same. And it is like this.
Administrator: Everything
Content Api Access: Read
Everyone: Read
Aug 03, 2018 10:28
Hi Niklas ,
Thanks for your information. I will investigate the problem and be back here soon.
Aug 03, 2018 11:03
Thanks. Did you notice my original post update that it happens for all blocks. Not just Forms blocks.
Aug 03, 2018 11:05
Hi Niklas,
After investigating I found that the problem happens with version 1.x (happens for all blocks as you said)
We're working on version 2.0.0 to improve ContentDelivery API and the problem has been fixed in this version.
The package will be released in next couple of weeks I think.
Thanks !
Aug 03, 2018 12:04
Hi Niklas,
it's going to the hand of QAs the next few days. But we have a pre-release packages, you can try it Lemme know your email address :)
Edited,
Oct 02, 2018 8:44
Yeah sure i love to give out my email ;-) Can't find a wat to send PM on this site. Well it is niklas.lord@connection.se :-D
Oct 02, 2018 19:02
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
If you request a Episerver Forms Form Container block using http:///api/episerver/v1.0/content/ it will give you a HTTP 404 if the block is located under "For all Sites".
But if you move the block to "For This Page" it works just fine.
Anyone have problems with this? Is it a permission problem?
UPATE:
I just noticed that the same thing happens to all blocks. So this is not a Forms problem and this thread should be move to a different part of the forum.
EDIT:
Title changed