-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add project view in admin field issue #458
Comments
Using the TimestampsAdminDisplayMixin add the display of timestamp fields to Organisation, Project, ProjectUpdate and PartnerSite model admins. Change where the fields are displayed to kill bug #458 that happened when the timestamp fields had their own fieldset that was only shown when there was any timestamp data.
The organisation/change_form.html had some code still from when it showed internal organisation IDs thata was removed.
Tested on UAT and issue has been fixed. Just awaiting code review before closing. |
Looks fine - with the code check I'm wondering if we should keep all the lines we're commenting out here: 8cb18c6#diff-37323ecbc3845b8a85c15f7b09483ab1R1202 or if we should just remove this. @zzgvh is it useful to have this there for reference? |
There used to be two fieldset definitions, one that was used for Akvo staff users and one for partner users. But with the addition of the timestamp fields the mechanics for how those fields and the notes field are shown/hidden has been changed and generalized to all use the get_fieldsets() method I don't think the old way needs to be there any more. The core fieldset is still there of course: Line 1181 in 8cb18c6
|
However I see there's a commented old version of get_fieldsets() that should have been removed too 😛 |
Thanks - closing |
I suspect this is to do with the new Timestamp field. A few of the fields have been messed up slightly in the latest release - for example add project location now tacked on to the photo section and then the budget section has the location header:
The text was updated successfully, but these errors were encountered: