Specific Pager per User

[marmelflo]

Hello,

first of all, I think this question was asked before in a similiar way. But I am a Processwire newbie and just don't understand all of the posts I have read before.

My idea is to create pages for users and in that pages (in the frontend) are attached documents, which I attach from the backend. The user should not edit anything in the backend and should only be allowed to see a destined page in the frontend. Perhaps this could be realized with sites that have the name of the user.

mypage/user1

mypage/user2

The sites are not visible to anyone else. So when user1 logs in via processwire backend, he cannot edit anything, but can open the URL

mypage/user1 and sees the frontend, where he can download files attached to it.

Thank you very much!

[elabx]

I would add fields to users (as they are themselves Pages) and you could call the added fields using the API from another page that's visible in your page tree under Home. Maybe you could link the frontend page with the actual user Page with a Page select field. 

[LostKobrakai]

What's the reasoning behind going through the admin interface and then back to the frontend?

[marmelflo]

Hello,

Because I want to create a customer download portal, with a standard layout in the template, showing different Data for each user page. I don't want any CMS feature for the customer and due to that no backend. Is it perhaps possible to make an if condition in the template file, which prooves if the name of the logged in user equals the page name (then renders content) and on the login I could set a redirect with the name of the User in the URL. This could work if the name of the User and the page are the same. But I think maybe there is a more elegant way