architecture of a pods based solution

[ad_1]

I’m starting the development of a solution based on pods (custom type, cf, relational fields…). The content entered into the cf (in principle the whole site) should only be accessible for logged in users. A user should only see those records entered by himself.

Now I’m confused wether I should focus on an interface in the WP backend or frontend. Should I redirect the user after the login to a front end page or present the data in the backend of WP?

I would like to build a nice user interface and this sounds like “use the front end” to me.

I would appreciate to get some ideas about the way to go and maybe a “why” would be helpful too.

[ad_2]
1 Comment
  1. Sounds like front-end work for me. Sounds like the CPT should have a relation to the user who’re allowed to see it, and then fetch it based on the current users ID. Might want to consider making the ID a request, and then check whether the User ID and the requested ID are the same, OR that the user is a admin type, so admins can view the front-end views as well.

 

This site will teach you how to build a WordPress website for beginners. We will cover everything from installing WordPress to adding pages, posts, and images to your site. You will learn how to customize your site with themes and plugins, as well as how to market your site online.

Buy WordPress Transfer