The GeoLiteCity.dat file must be removed before making this public due to licensing reasons.

In the coupled sample if updating nuxt to 3.0.0-rc.12 or newer the ContentResolver throws an undefined exception, and no content loads

When navigating around the front end site all links are pointing to the backend server URL i.e.

Is there any SDK for ReactJS
Can you share the if there is any sample or road map for it.

Hi!

Since the content delivery api backend supports cookie authentication (https://world.optimizely.com/documentation/developer-guides/content-delivery-api/getting-started/authorization-service/) I was thinking it might be nice to include the possibility to add a cookie header via the frontend repository.

I noticed that apiClient.ts accepts optional headers in the get-method, so what if the resolveContent method inside contentResolver.ts could be changed to include optional headers that are sent in to #api? Or maybe the ContentDeliveryConfig could be modified to include getHeaders() (like getAccessToken) and used in the call to #api.get?

(I suppose this applies to contentLoader as well)

What do you think?

In version 3.0 of the Content Delivery API the requests are made to an unfriendly url e.g.

http://localhost:8081/api/episerver/v3.0/content?contentUrl=%2F&matchExact=true&expand=*

in version 2.0 it was similar to http://localhost:8081/url-segment and request header of accept='application/json'

Hi,

We would like to access some custom headers in the reponse from the Content Delivery Api.

Would you consider adding the response.headers (Map<string,string>) to the result of the contentResolver.ts -> resolveContent method?

Thanks

Hi,

First I want to say impressive work and really easy to get the sample project up and running. It seems that the onpage editing is not working. Get 214 to a file locally:
http://localhost:8081/episerver/cms/latest/clientresources/epi-cms/communicationinjector.js

If I google this I get a hit to this file:
https://github.com/Romanets/RestImageResize/blob/master/AppData/Modules/CMS/1.0.431/ClientResources/EPi/cms/communicationInjector.js

Maybe it can be something just on my local installation. If I then manually add (communicationinjector.js) to the project I get: Uncaught DOMException: Blocked a frame with origin "http://localhost:8080" from accessing a cross-origin frame.

When looking closer to communicationInjector script I see what it does. It tries tom manipulate an iFrame with dojo. Probably to get access to the iframe which is used i CMS edit mode. This will not work unless both frontend has the same host and portnumber for security reasons in browsers. In the sample it set to localhost:8081 //backend localhost:8080 //fronend, ie. different portnumber. Also see this stackoverflow:
https://stackoverflow.com/a/25098153

Trying to summarize my question here are there other documented ways to connect and use on-page-edit functionality with Optimizely cms using content-delivery-js-sdk?

I am having a hard time making OPE work in the decoupled sample.

I am logged in to the CMS server on port 8081, and running the SPA on 8081.

But no matter what I keep getting the Default (view) mode.

I guess It has something todo with that the fact that I don't have window.epi?

Can you help me?

Rename import/export to push/pull in content definitions CLI.

When are you going to support API v3.0?

For example SiteDefinition.contentRoots model is missing startPage definition.