Login functionality with permissions table for WordPress - sub-topic, to be completed, quite urgent

Closed job

Vanhem

Employer

29 deals

Job category:

Desktop/web applications

Expected budget:

Negotiable

Preferable skills:

php wordpress

Published: on 2022-05-29

Valid until: on 2022-06-28

Job description

Hello,

I need to complete the login functionality for a certain area of WordPress.

Currently part of the logic is written, need to add the rest.

How should it work?

1) The user goes to the address of the registration page and receives a form with a table, in which the checkboxes are used to select pages and fields (from ACF) to which he wants to have access.

2. sends the form or registers an account in WP. The account is in a waiting mode for activation. The user receives an e-mail that his account is waiting for approval. The administrator receives an e-mail that there is a new account, along with a link to go to the WP users page. There, he sees the new account and an active table field dump. He can confirm the user or change the access range in the table and then approve. 3.

After confirmation the user receives an email that his account has been activated along with a snapshot of information from the table - that is information where he has been granted access.

4. at any time, the administrator can edit the user's account, assigning or taking away permissions to a particular area "from the table".

Additional guidelines:

1) At the moment, manually enlisted ACF fields, which are the same for all subpages, enter the table based on their names.

2) Currently, a dynamically pulled list of subpages (children of certain manually specified pages) enters the table. This needs to work so that every time the table is edited, the previously assigned accesses are not lost and new subpages are potentially seen if they appear.

(3) The user must also be able to see this table on the "my account" page but only in preview mode without editing. The user will not have access to the wordpress panel only the themes pulled to the front end.

The rest of the information in the "required features" field because it doesn't fit here :D

Required functions:

The information from the table should be saved to the meta data of the user account along with the key on how to use it later. They will be used so that when the user displays a subpage with an ID that is in the table for each ACF field with a name that is in the table and some parameter (0/1) we will either show the field or not. What do we have and what is to be done? 1. we have an array with subpages id 2. we have an array with acf fields 3. we have templates and subpage addresses (you don't have to create it) - login, registration etc. what is needed is the meat of this functionality together with necessary views: 1. the table itself with the option to select, read, save and update data 2. option that the user is in acceptance waiting mode 3. e-mail notifications in the right moment 4. code allowing to extract information if someone has permission to a given field or not that's it :) - It does not have to look perfunctory but it has to work. It will be further processed by a frontend designer :) The topic is quite urgent, because the previous person did not finish it.... I assume that it is still a few hours of work, maybe someone has them free :)