Sitecore user accounts have an out-the-box field added to asp membership user profiles called 'Full name'. This field is not searchable from the user manager in Sitecore (See pic).
How do we make this field searchable?
Related
I'm using apex to create an application that has a database backend.
The application allows the users to search for institutions according to specific criteria, once the criteria are specified, a report is displayed to the user including the institution name and the logo of the institution. The name column is linked to a page that displays the details of a chosen institution.
I want to create a link from the details page that takes the user to the 'Contact US' page which should have some prepopulated form fields like the institution name and email etc. However, I'm not sure how to pass the institution id so that the fields can be prepopulated.
In your report, have the institution id as a column of type link next to name and logo. Make the target page your contact us page and populate the institution id page item with #INSTITUTION_ID# (or whatever your institution_id column is called.
I have an django site for new articles , in which multiple user write articles.
I want to make an action for selecting a user , so that If I choose a particular user , I can only see its updation/insertion in admin site.
If updation/insertion is part of a model that has an foreign key to USER model, then just write an admin-inlline to show a list of them in the user page below all other fields
Hey guys I have created a messanging app in django in which i have User.auth,Profile and message app which works fine. Now i need is to add contact category in every user accounts. So they can add contacts like email with there firstname and last name?
You should be able to update your Profile model to include a many-to-many relationship with other Users. Then you can access the related user models for a given profile's contacts through that profile. In the profile model:
contacts = models.ManyToManyField(User)
Set blank/null as is appropriate.
I just got the requirement to show data on Django admin panel in a certain way.
Actually I have log table in which I have userid and action it took.
class AuditTrail(models.Model):
id = models.AutoField(primary_key=True)
userid = models.ForeignKey('User', null=True, db_column='UserId')
action = models.CharField(max_length=200L, db_column='Action')
timestamp = models.DateTimeField(null=True, db_column='Timestamp', blank=True)
When I add it on the admin panel it just give me all the entries in AuditTrail table.
I have created filters on timestamp, search on userid and default ordering. But what actually is needed is on the main page where all the entries are shown I need to group rows on userid. and on clicking userid I need to implement expand/collapse logic.
In short on the main page of the model I get list of all users and I can collapse and expand all the rows for that user. Can I achieve this somehow in django admin panel. Does django give the functionality of grouping model objects on some field?
Thanks in advance.
Edit 1:
If it is not achievable in Django? What i have done now is i have created a link for each user's audit trail and i created a custom field and added in User's table.
You need to customise the default template and add asset definitions.
For grouping you might need regroup builtin tag.
Use case:"
I have a the standard user model that have a Userprofile model that contains among others the field region that is a ForeignKey to the Region model.
Users can be in permission groups that are standard for Django.
In django-admin user model page the user kalle in the site-admin group can see all users. The user pelle is in the regionA1-admin group can see all users who have their userprofile region set to regionA1."
What is the best practice in django to handle this use case in a secure way?
And it could be other models than User. Regions can be added and deleted. Region is used in this case but could be one or more fields that form the criteria. This shall only apply to the django-admin interface and not when interacting with the database on the regular site.