Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm building a multilingual site (with i18n module and entity translation). I've added a field collection on user profile type (with profile2 module ). How can user translate the content of the field collection of here profile ?
knowing that I have this error message with entity translation
The entities of type Field collection item do not define a valid base path: it will not be possible to translate them.
The entities of type Node registration do not define a valid base path: it will not be possible to translate them.
The entities of type Profil do not define a valid base path: it will not be possible to translate them.
I have activate "Users may translate this field".
thank you
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Say I have a site with two types of user
contentCreator
and
contentUser
What I want to do is :
contentCreator has to pay to have an account, and once logged in, has feature set X.
contentUser can register for free, and once logged in, has feature set Y.
All I need is a pointer in the right direction to get me started.
This can be achieved using a membership plugin where you have a free and a paid membership structure and limit the content access based on the user membership plan.
You can use plugins like Simple Membership and configure it to have both paid and free memberships.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
My use case scenario is as follows.
I have a taxonomy vocabulary called "Company" with unique terms "Company 1", Company 2" and so on. Each node in my setup has a term reference for this as mandatory. Similarly, every user is associated with one term with a custom field.
What I want is to restrict a user to only see/edit the nodes that are attached to the same term ID. e.g. If user A is associated with "Company 1", he/she can only view the nodes that are associated with "Company 1".
I am using "TAC" module to achieve this. But it only allows for the taxonomy based access control based on hard coded values whereas I am looking for dynamic reference to the tid in userfield.
PS: I am relatively new to Drupal
Do it on your own. Use hook_node_access and write your own logic there:
https://api.drupal.org/api/drupal/modules%21node%21node.api.php/function/hook_node_access/7.x
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm modeling a permission strategy for a site.
I have this type of user:
Superadmin: the initial user and he can create others admins
Admin
Customer
For Admin and Customer i used a role assignment. But for SuperAdmin i don't know if i should use a role or a simple flag (boolean "IsSuperAdmin")
What is your opinion? thanks.
One method is you can create a new table user_roles for adding roles.
Fields,
id role_name
Then create a field user_role_id in your users table for storing the role id.
We can check the roles in session to access their methods.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
If I don't use the accounts-ui package, Meteor.userId() is null.
How can I get the equivalent of Meteor.userId()?
The Meteor.userId() is supplied by the accounts package itself.
Just as the name implies, the accounts packages provide you a base, authentication managers and user interface components to manage your Meteor application's user-bound requirements.
So you either have to use at least accounts-base, or if you don't you need to implement your own solution to get a reference to a user object (that you create).
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I want to customize default registration process in Drupal 7. The registration process includes 3 steps:
Show some account types (in a page or form?). For example "personal", "business", "organization"... And users will choose their own account type.
Fill information into registration form. Each account type which users choose in step 1 has some corresponding fields.
Finish registration with an confirmation email or something else.
The registration process is similar to https://secure.payza.com/signup
Thank you for helping.