ive been getting the same error have you been able to figure out what could be the cause?

@@King-hs9zc i was using the official wp site for creation than I saw some videos and all pf them are making wp locally using local wp i did the same and it worked

Hey Haikel, what would help you out or make learning easier for you?

@@millertchris can i just create a custom post layout like a card then i can just pull in data from ACF to appear on that card

Thanks, Edan! We need to catch up soon.

You're right, thank you for sharing!

Not that I'm aware of - but the PRO version is 100% worth it, especially if you're building a lot of sites for clients.

Best of luck!

Yes! There are several methods of testing WordPress plugins using the REST API. One way is to use a tool like HTTPie, Postman, or Insomnia to send HTTP requests to the plugin's endpoints and analyze the responses. These tools allow you to easily test different request methods (e.g. GET, POST, PUT, DELETE) and inspect the returned data. A tutorial that demonstrates the benefits of using the REST API for plugin development could include information on how to interact with the API using these tools, as well as best practices for designing and implementing endpoints in a plugin. I'll definitely consider create another video about this in the future.

Thanks Chris !

nope

Glad it helped!

Yes, there are several ways to protect a custom REST API endpoint in WordPress, especially when handling sensitive data such as a POST request. Some common methods include: Authentication: Requiring a valid nonce or credentials for every request to the API. WordPress have its own authentication methods like JWT Authentication for WP-API plugin which allows you to secure your endpoints. Authorization: Checking if the user has the appropriate permissions to access the endpoint. WordPress has built-in capability system which can be used to assign capability to user roles. Input validation: Validating user input to ensure it meets certain criteria, such as the right format, length, or allowed characters. WordPress has built-in functions for validation like wp_verify_nonce() which can be used to validate nonce. Request rate limiting: Limiting the number of requests that can be made in a certain period of time to prevent overloading the server. This can be achieved by using plugin like "Limit Login Attempts Reloaded" SSL/TLS encryption: Encrypting all data exchanged between the client and the server to protect against eavesdropping and tampering. WordPress has built-in functions to handle SSL like is_ssl(). Using an API Gateway: An API Gateway acts as a reverse proxy and can handle many of the above security concerns, such as authentication and rate limiting. WordPress doesn't have built-in support for API gateway, but you can use plugins like "WooCommerce REST API Manager" to achieve this. It's important to note that these are some of the most common ways to secure an API in WordPress, but depending on the specific requirements of the API, other methods may need to be added.

I'm not aware of any at this time - however - I would suggest working with the native UI's provided to you in WordPress and ACF since they all have a natural integrated look to them. This can also free up a ton of time for you and your team, focusing more on how the features work, rather than how they look. Just a thought.

Could you elaborate more?

Exactly! You could use it in a JS application, mobile app, or anything else that can consume JSON.

@@millertchrisis it just good for posts? what else would it be great for making it worth doing wise?

@@antdx316 for example a sports page, you want to be able to query the data of stats by player or teams, leagues etc.

@@briansanchez7751 I've been coding like nuts for weeks with ChatGPT : )

Thanks, Gautam!