I'm using Redmine 2.4.0. I need to make a standard field (Planned Start) as required. Is it possible?
This functionality was added in v2.1.0 allowing configuration of required fields from a tab in the workflow settings. Read more details on Redmine Issue 703
Field permissions are set up per "Role" and "Tracker". I set up field permissions all the time and I've never had any problems with them. Did you take care of these settings?
Related
I want to manage(such as Change the default language) the country region details of in my Django website. Does anyone have a best way to do that?
There is no built-in way in Django to achieve that. See adamcharnock/django-tz-detect. The project is maintained well, still active and has an easy-to-understand documentation.
I'm running into an issue with Hedgehog's TDS - I have some presentation details specified on my Base Page template. The presentation details reside in the __Renderings field of __Standard Values. I've set the item to "Deploy Once", but it appears that Sitecore ignores that setting on __Standard Values with the package deployment (UpdateInstallationWizard). If I update any of the presentation details on the production site, they are lost with my next deployment.
For now I've excluded the item from my production build - but it's kind of a pain.
I've opened a ticket with Hedgehog - they say it's a Sitecore problem. I opened a ticket with Sitecore - they say that UpdateInstallationWizard wasn't meant for use outside of sitecore.
Is there a good way to get around this? Should I not be specifying any presentation details in a base template?
I ran into the same issue just today. The only solution I can offer is to manually delete the previous __StandardValues and then rerun the update installation wizard.
I've been using django-auth-ldap for a while to auth against a single server (AUTH_LDAP_SERVER_URI in settings.py). There have been some changes in my organization recently, and I now need to be able to check against two different LDAP servers (actually: Active Directory, but I don't think that comes into play here). Unfortunately there is not a single location that has all of the user info I need.
Is there any way I can configure django-auth-ldap to check against more than 1 server? The documentation seems to assume a single server/URI. I'd also entertain ideas outside of django-auth-ldap, but I'd really like to stick with it if possible because it keeps things simple.
You would need to extend the custom auth handler to take an iterable for servers to check against and just step through them.
There is nothing stopping you from checking any number of directories for the information you need - there is no limitation in the underlying libraries.
django-auth-ldap 1.1 (just released) allows you to easily define multiple subclasses of the authentication backend that use different collections of settings. See http://packages.python.org/django-auth-ldap/#multiple-ldap-configs.
I'm creating CMS and now facing some issue I need your advice. I have few different modules (apps) I can define custom permission to them - in model i define custom permissions like "view_store", "edit_store", "delete_store" and so on. And then I have defined different user groups (I want to have group based user access control) - admin, editor, vip, user.
I'm creating these groups when running one time command to initialize CMS (manage.py initcms) and I want of course all the right permissions will be added to the group in the same time.
initcms action is running after the syncdb, so all the models are in DB (info about permissions also of course).
I have something in my mind... If this is good way to go or you have the better one? Let me describe mine: I want to give for example for vip user all the permission from all the models (which have this permission defined) to "view_*". It means vip can view everything. I have an idea when initializing database just grab all entries (all permissions) which fits pattern "LIKE view_%" and then add these all to group's permissions.
But then the problem if the new module will be added... I need to re-run this action and check if all the permissions are right... Maybe there is some dynamic way to deal with group permissions?
One possible solution is to use Django Signals, which can be triggered before or after a model's save mothod has been called or after or before any M2M action takes places, after syncdb etc... You may select a proper signal that fits you best and then call a function that checks related permissions and add or remove any if necessary...
When you create or modify an object instance in Django's admin, a changelog entry is created. This is really nice for fairly obvious reasons.
However my model's instances created by a normal user outside of the admin interface. No changelog is recorded to note its creation (not a huge issue) but I would like to track edits the user makes.
I also want to show the user this full log (user+admin edits) in the frontend so I need a way to pull the changelog out.
My question: how? Is there a one-line switch I can flick to enable full logging or do I have to dig in and do something on my user's edit form logic?
django-reversion is an app designed to help with that.