sst/storage_templates #3
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mhu/shimatta-kenkyusho#3
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "sst/storage_templates"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I was trying to add kind of a templating system when adding storages - so sub-storage structure is automatically copied from the template.
...to e.g. generate the same kind of assortment box.
...had to change the way you added a user search in this form to get it done - now the user is found using the same mechanism as all the rest. I even added a method to add the @ back in...
I changed the pull request to be merged into develop.
If we really start to work on that together, I guess it makes sense to have some sort of separation between develop and actually stable versions on master.
Another test comment to test whether emails are actually sent. @sst
@ -6,3 +7,2 @@
class Meta:
model = User
fields = ['username', 'email', 'first_name', 'last_name', 'groups']
model = get_user_model()
Mh. According to https://stackoverflow.com/a/24630589/5761843
another way of retreiving the user model should be used.
Ah. shit. Nevermind. Very old post. They changed that way back in django 1.xxx
@ -593,6 +598,8 @@ class StockViewDetail(LoginRequiredMixin, BaseTemplateMixin, DetailView):
if 'submit-add-storage' in request.POST:
return self.handle_add_storage_post(request, **kwargs)
if 'submit-change-storage' in request.POST:
Any reason, that is not an elif? @sst