Hi there, I’m totally first-time trying frontity and I’m totally thrilled and I want work to with my local installation of WordPress but, I’m having a really bad time as I’m not able to connect with api and I get this error Add the URL of your WordPress REST API in state.source.api. in console–full error below. On address http://localhost:3000 I see “Internal Server Error.” But I’ve added api link in frontity.settings.js file like:
What’s wrong happening IDK? I tried to change to Permalinks in WP setting and tried al l but still not working. But the API works fine in browser and postman which means problem isn’t with WP. Check my shell log at:https://asciinema.org/a/qc7GyEU3LGlxqxOaPIe6CdbQP
I’m curious about what you are building with Frontity, can you share something?
Please let us know if there’s anything that you need, we love to hear feedback from people using Frontity for the first time to improve our framework and docs
Thanks for asking. But right now I’m just testing and learning… I fond frontity super cool maybe I want to make blog with it. Can I just ask you if you’ve any experience that wordpress.com free plan offer API use? If yes how can I access them? Nice idea would be to make a tutorial blog/video…
TY!
I’m totally inspired with frontity now. I just have to enter API address and it works… Wondering why I don’t have to authorize it or etc… But is this safe? Not everyone can steal data?
Hey @inamkbmail the API you are accessing is only exposing the public data of your site, which in the end is the same data that is available in the content. Consider it just a different way to access your content, instead of HTML your WordPress is exposing it in a JSON which is easier to process.
Yes, I understand it but this isn’t the same way like anyone could grab someone data and display it on his web. Suppose I fetch someone copyright data and use it easily. But that’s not a problem till now.
But what if I’ve to keep some data private or some pages accessible for certain people?
Yes, I understand it but this isn’t the same way like anyone could grab someone data and display it on his web. Suppose I fetch someone copyright data and use it easily.
As long as the data is public you could scrap it and post it anywhere else without an API.
But what if I’ve to keep some data private or some pages accessible for certain people?
Then you would need to make those parts private, and not expose them in the public API. And also to implement an authentication system. So you’ll be forced to use a wp.org instance instead of a wp.com so you can customise the REST API response.
Great! Keep us posted and let us know your impressions