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
Merge staging into production - 2022-12-14 edition #474
Conversation
Bumps [lxml](https://github.com/lxml/lxml) from 4.8.0 to 4.9.1. - [Release notes](https://github.com/lxml/lxml/releases) - [Changelog](https://github.com/lxml/lxml/blob/master/CHANGES.txt) - [Commits](lxml/lxml@lxml-4.8.0...lxml-4.9.1) --- updated-dependencies: - dependency-name: lxml dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Improve proofread page
remove genre column from genre-detail page
Make dropdown menus in header opaque
Add lists of sources to user detail page
on chant detail page, increase volpiano font size
fix logic to check whether gregorien.info page is valid
Ensure unpublished sources do not appear in user detail sources list
Filter sources by published status in view instead of in template
…ecessary code for rendering the new contact page
Merge my staging into DDMAL's staging, to hopefully resolve merge conflicts
Required fields on chant create/edit/proofread pages
Add title attributes in useful places, fix Chant-by-Cantus-ID page formatting
Merge develop into staging - 2023-01-09 edition
we need to fix #494 before we merge this EDIT: fixed! |
full-index page: ensure `s_sequence` is displayed if chant/sequence has no `c_sequence`
Merge develop into staging - 2023/01/10 edition
On staging, I'm still seeing column headers on the Chant Search and Chant Search Manuscript pages, which confuses me... http://206.12.88.113/chant-search-ms/699578?op=contains&keyword=est&office=&genre=&cantus_id=&mode=&feast=&position=&melodies= |
I'm done my testing! At last! @annamorphism, are there any things you've noticed in your investigations that must be addressed before we update the production server to run the code that's running on staging? |
The new code is now running on production! All tests are passing, and I interacted with a few pages and everything appears to be running as it should! 🎉 |
It's time, soon, to update our production server with the new features and bug fixes, which have been in testing for a little while on staging.
The following changes are included in this merge:
test_func
checking whether user has permission to modify chants in a given source (commit)0
, it is displayed (commit)test_func
checking whether user has permission to modify chants in a given source (commit)0
,0
is displayed in the "Sequence" column (commit)folio
andc_sequence
fields are required (commit)office
andgenre
are ModelChoiceFields, rather than text input widgets (commit)title
(i.e. mouseover) attributes to several column headers (commit), then move some of them from column headers to the cells in the table rows (commit)cao_concordances
column from CSV (commit)siglum
of each chant's source, rather than the chant'ssiglum
(sometimes chants' sigla are out-of-date) (commit)folio
and then byc_sequence
(olimsequence_number
) (or in the case of sequences,folio
thens_sequence
(olimsequence
) (commit)s_sequence
is displayed in the "Seq" column when there is noc_sequence
(commit)test_func
checking whether user has permission to modify chants in the source (commit)sequence_number
field withc_sequence
, and replacesequence
withs_sequence
(lots of commits).get_next_chant()
more robust, accounting for more edge cases (commit, commit, commit).get_next_chant()
(commit, commit, commit, commit, commit, commit, commit)The above pages have been interacted with on the following devices/browsers: