Thatâs an endpoint to fetch the data from, itâs not a path that you would use with Frontity - Frontity uses the endpoint internally to get the data into the state so that you can work with it. To navigate a Frontity site you would use the same permalinks that WordPress uses.
Regarding the posts, where is the content for the plugin if itâs not in posts?
So the shortcode adds, or should be adding, the cookie info to the page content? If thatâs the case then you donât need the code you cited when you started this thread in your functions.php file. That code is only needed if you need to add a CPT to the REST API.
So now we need to figure out why the cookie info isnât in the page content that is being sent to Frontity.
OK, so I installed the plugin and did some digging around.
It turns out that the content for the cookie consent plugin is buried away in the WordPress wp_options table. It is in an option called CookieLawInfo-0.9 and it looks like all the info and settings for the plugin are contained within that option, including the text content. Iâve included screenshots (taken from Sequel Pro) below and have highlighted both the option and also the text content corresponding to the text in the Message field under the Customise Cookie Bar tab.
You will need to write some PHP code, either in the themeâs functions.php file or in a custom plugin, that retrieves that option and gets the content you want. You will then need to create a custom endpoint, again in PHP, exposing that content in the REST API, and then fetch it from Frontity and handle it.
TBH, unless you need to use WordPress to content manage this it might be simpler to just add a React component to your Frontity theme to display a consent bar.