I'm working on a large Symfony2 app that has the following bundles (all under the same vendor name): Login, Register, Blog, Forum. The official docs say that forum related entities belong in the Forum bundle, and Blog related entities belong in the Blog bundle. But what about my User and Account entities? Both are created during the registration process, and User is used during the login process. I consider those entities to be global to the app b/c their use isn't limited to one feature (again, per Symfony docs, one 'feature' per bundle.) I'm wondering what the best practice for this would be.
You can create UsersBundle and in future store other code, related to users in this bundle.
Related
We are evaluating Drupal as an enterprise CMS and need some help/recommendations for the following features.
Multi Step Approval Workflows with reassignments
PDF files in the media library requires authentication to view/download - Does drupal have any security features that does not allow anonymous access to media files?
Does Drupal support Roles, User Groups and security groups? We are looking to restrict users from certain areas of the website and CMS based on group and role permissions.
I understand that Drupal is modular by design so there are lots of modules available that does similar things or these functions available in Core?
Appreciate any advise/experience that members can share.
Thank you.
Drupal can do all these things.
Multi Step Approval Workflows with reassignments
There is the Workbench moderation module, but also now in Drupal core as of 8.4, the Content moderation system is available. You might need to do some research on how content review might be assigned to a specific user.
PDF files in the media library requires authentication to view/download - Does drupal have any security features that does not allow anonymous access to media files?
Yes, Drupal has a private file system available in core. You need to set this up when you are setting up the file fields initially, because converting from a public to private file system is a bit of a messy process (I literally just did it a couple months ago for a project). It you can store files in a directory outside of your webroot, and the user will request a path like /file/system/1234, and all appropriate access checks are made. You might need to set up some additional permissions to have these access checks respect things like "groups" or any other access rules that you want to implement.
Does Drupal support Roles, User Groups and security groups? We are looking to restrict users from certain areas of the website and CMS based on group and role permissions.
Yes! "Roles" are available out of the box in Drupal. You can define as many roles as you like, and apply permissions to each role.
There is a module called "Organic Groups" which provides the group functionality. You can restrict content access to group members as well. You can even define roles within a group, so different users can manage the group.
I am trying to evaluate the possibility of creating a plugin for Parent/Child functionality in Wordpress user creation.
What we need to achieve is to allow a Parent to create a sub-user account for his children. This accounts will have limited access but that can be done later with other Wordpress plugins.
What does not exist right now or what I was unable to find, is a plugin which gives the possibility to an existent standard user, to create sub-accounts related to him.
I do not want anything particular except the association between the accounts. The main user should have the possibility of adding or removing his child accounts.
Do you think this is something that is ok to do? Does it open us to any hacking possibility or vulnerability or create problems in the future?
If not, what would be in your opinion the best way to proceed and do this? What would be the best, fastest and most secure flow of operations?
Looking forward to your opinions.
Thanks in advance.
Regards
I know this is an old post but here's an option for anyone searching for this in the future.
First, you need to register a new user role. When you register the role, you are free to assign any capability you want. In this case, give the new role the capability to add users.
Then you can create a one-to-many relationship between the new user role and the standard subscriber role. So the new user role can have many subscribers but a subscriber can only belong to one new user role.
This will do what you want. There are several plugins that can do this if you are not comfortable with coding which seems the case per the OP's question. You can try PODS which is free and available in the Wordpress Plugin Directory - https://wordpress.org/plugins/pods/.
I used sonataadmin and really like some features, like creating an entity and its related entity in the same page. I want to use it for frontend user also. Is it possable to use sonamaadmin for both backend and frontend users? Or is there another bundle allowing me to create an entity and its related entity in the same page?
Those are just form types, provided by the SonataAdminBundle. You can use them in any form.
You probably looking for the sonata_type_model or sonata_type_collection. See the documentation for more information.
Of course you can use Sonata Admin in both, although will be like only having a backend and made the correct security configuration for two kind of users. About entity and its related entities in the same page, that has nothing to do with Sonata, this can be achieved with symfony simple and embed forms.
There are any number of membership plugins for Wordpress that exist to monetize website content. People pay a subscription and have access to pages and posts. This makes it difficult to locate what I am looking for.
Is there a plugin that is specifically for managing the membership in an organization?
WHAT IT SHOULD DO
Have the ability to import existing
membership details and create WP
users from those details.
Automate and manage the
collection of annual dues.
Facilitate mass e-mails to members.
Restrict access to some of the Web site pages
perhaps by linking membership to WP
roles.
Perhaps manage payments for conferences.
Have the ability to export membership details.
SOME THINGS IT SHOULD NOT DO
Have pay per post functionality.
Sell value added pages.
Have different levels of accounts based on content.
TIA
I was looking for a similar plugin for a non-profit organization client of mine, and finally found MemberMouse. I was particularly concerned about being able to setup annual dues at a certain time of the year with pro-rating for new members during the rest of the year. While this is not in their base plugin, they can custom program that for a small fee.
The only parts of your request that plugin may not cover is facilitating mass emails (you could manage that through something like Constant Contact) and taking payments for conferences (which you could setup on your site anyway pretty easily using PayPal or your merchant account provider and a cart).
Hope this helps. I would suggest contacting MemberMouse with your questions to see if it will work for you.
I am building a DMS for our intranet and use a taxonomy hierarchy because we need access control that way. All company locations manage (upload,edit) their own documents but should be able to access all. This is inherited to the child terms and works fine.
Additionally we want simple 3-step workflow (draft,published,archived). So i introduced roles for editor, publisher and docadmin and set permissions for the transitions. Also triggers to effectivly (un)publish documents.
But (of course) a user of role publisher can do the transition for ALL documents. But we want publisher for each company location (top taxonomy level, see above).
Could this be achieved? Do i have to set it up by myself (i guess "rules" is appropriate to do this) or is there another module helping.
role inheritance was a guess, but that is only about roles (naturally).
"module grants" i use and checked first option. That way my thoughts are going. I hope you get my idea resp. problem.
drupal 6.16 current
edit:
I reread the docs and found ie. http://drupal.org/node/408018 Revisioning for categorized content. Will reread that.
It seems you're running into a know issue in Drupal 6's node access api. Grants only work as an approval, so if any access module says a user can perform an action no other module can take it away. The only other solution I can think of would be a mash of the modules to calculate based on both criteria, obviously a potentially complex task.
Certainly not recommended, but you could apply your own logic to scan the grants tables to remove entries for users that don't match up with both criteria. You would have to find the right hook to have it perform its work after both other modules have calculated their values and saved them to the database.
Good news: this is fixed in D7. Bad news: D7 will be a while.
Drupal 7 will allow modules to approve, deny, or abstain from node access decisions. As such, your taxonomy module could say the users are approved for these terms, denied for others. As well, workflow could approve for some stages and deny for others. A user would require at least one approval and no denials.