I just wonder if its possible to Create one or more fields and show it in User profile and make it not published until the admin approve it.

And if the user edit it again it will be un-published again and need admin approval.

CommentFileSizeAuthor
#3 Diagram.jpg1.27 MBwooody
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

wooody created an issue. See original summary.

johnv’s picture

Issue summary: View changes

So you want:
- each state has a 'published'/ 'unpublished' field.
- whenever the state of an entity (i.c. User) changes, the 'Published' status changes accordingly.

Is that correct?

wooody’s picture

FileSize
1.27 MB

Hi John,
Thank you for your answer. I am not sure about what u mean but What I see for workflow and moderation that its moderate all the node or profile. And I am looking for only moderate a field inside user profile.

I have made this digram and screenshot to explain the idea more.

USER B:
User with B role. request for join Listing.
Waiting for approve or reject from listing owner.
If reject. it will show msg that its rejected.
If appoved it will show msg that its appoved now

If appoved, user can change that and will need
to wait for approve or reject again.

If its approved so it will be removed from the old listing
and added to the new listing

USER A
User with A role. Can add thier listing
User can approve or disapprove user B request.

johnv’s picture

OK, so nothing to do with publishing.
Do you mean: "depending on the value fo the State field, I want other fields of the User Profile to be hidden"?

I that case, you may use one of the following modules:
- https://www.drupal.org/project/conditional_fields
- https://www.drupal.org/project/field_conditional_state (no D8 version)
- https://www.drupal.org/project/workflow_fields (needed for D7-implementation of Workflow, but in D8, conditional_fields should work)
- https://www.drupal.org/project/wf_required_fields (needed for D7-implementation of Workflow, but in D8, conditional_fields should work)
So from aboe list, I'd recommende trying the first module.

Please keep me posted of your results! I would like to add your info to the documentation

wooody’s picture

Hi John,
No really its not like Conditional fields.. Its more like User-A create listing,, and User-B can join that list and User-A need to approve that first. And User-A will only see the users that want to join him and manage them.( accept or reject )
I think workflow could do that but if its going to fields level not all node level.

Edit: I tried with flag and flag application module and its seems working. but need to limit the users that showing for each node.
So if user-A create node1 and user-b want to join it.. user-a can manage that user only ( approve or deny ) ( not all users as now)

D7
https://www.drupal.org/project/flag
https://www.drupal.org/node/2020689/git-instructions/7.x-3.x/nonmaintainer

Regards

johnv’s picture

O. I don't think this is a workflow issue anymore. Good luck.

johnv’s picture

Status: Active » Closed (won't fix)