hi everyone i have only one confusion that why in drupal the issue of required field on user profile with Custom Field Permissions is come only with Hierarchical Select field not with other field? please anyone knows that please help me thank you very much Ahmad khalid

Comments

dddave’s picture

Status: Active » Closed (won't fix)

Sorry for won't fixing this but this seems to be a support request for the HS module. And you should try to make your problem more clear because I frankly don't understand your post.

qasimzee’s picture

Status: Closed (won't fix) » Active

I think, it happens when with Custom Permissions, you don't allow Anonymous Users to view/create/Edit field value and mark the field is required. It will not appear on the registration form but when user try to signup, the form shows the validation error that field is required.

dddave’s picture

Title: Reason why in Drupal Hierarchical Select field as required field on user profile with Custom Field Permissions issue? » Reason why in Drupal Hierarchical Select field as required field on user profile with Custom Field Permissions issue?
Status: Active » Closed (works as designed)

Well, then there is nothing to do for us. Make sure that users have the necessary permissions to fill out the fields that are required. Thanks @qasimzee for clarifying this issue.

qasimzee’s picture

Project: Drupal core » Hierarchical Select
Version: 7.x-dev » 7.x-3.x-dev
Component: other » Code
Status: Closed (works as designed) » Active

Just moving it to the right module

kars-t’s picture

Status: Active » Fixed

Dear fellow Drupal enthusiasts,

this issue is now lasting for a very long time in the issue queue and was unfortunately never solved. As Drupal is a open source project everyone is helping on voluntary basis. So that this is was not solved is nothing personal and means no harm. But perhaps no one had time to deal with this issue, maybe it is too complex or did not describe the problem comprehensibly.

But this issue is not the only one. There are thousands of issues on Drupal.org that have never been worked on or could not be processed. This means that we are building a wave that is unmanageable and just a problem for the Drupal project as a whole. Please help us keep the issue queue smaller and more manageable.

Please read again, "Making an issue report" and see if you can improve the issue. Test the problem with the current Core and modules. Maybe the problem doesn't exist anymore, is a duplicate or has even been solved within this issue but never closed.

Help can also be found for it on IRC and in the user groups.

In order to remove this issue, I have set this issue to "fixed"

If there is new information, please re-open the issue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.