You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Making one issue to put all the issues I have found from testing era-app-prd.
1
resolved
Clamby dependencies are not installed. (will be able to test deposit process once this is done)
2
resolved
On deletion of an item through the UI I get this notification:
It looks like the item successfully deletes however.
Note: this doesn't appear to be reproducible locally, I get the message 'Item was successfully deleted!'... This may have to do with clamav acting up
3
resolved
The supervisor and department facets do not appear on the left sidebar. When either a supervisor or department is clicked from an item it appears to just return all items in the search.
Here is the sidebar on current prod:
4
resolved
It appears that I cannot remove logo from a community. When clicking the 'Remove logo' checkbox and then 'Update Community' the old logo appears to persist. I would assume it would show the standard ERA logo. Setting a new logo with a file works as expected.
Note: this is reproducible locally. The error I get is 'found unpermitted parameter: :remove_logo' and was able to fix it by making it a permitted param. Now to find the best way to do this.
5
resolved
When sorting items by date (either oldest first or newest first) from results you get an error when you switch to either the collections or communities tab:
F, [2020-12-08T11:45:43.220514 #653] FATAL -- : [50d6ad2b-cb3b-429e-8b50-300311d5df4e]
[50d6ad2b-cb3b-429e-8b50-300311d5df4e] NameError (uninitialized constant JupiterCore::SolrServices::DeferredFacetedSolrQuery::NameManglingError
Did you mean? JupiterCore::SolrServices::NameManglingError
JupiterCore::SolrNameManglingError
JupiterCore::SolrServices::NameMangling):
Looks like this is due to the param 'sort' being 'sort_year' where communities and collections expect it to be 'record_created_at'? It looks to rescue an error that doesn't exist as well.
Notice: This bug exists on current production as well.
It turns out that this is the expected functionality, you need to select from the list and not hit enter. I am going to put up a ticket to improve this functionality to make it more functional/user friendly
7
resolved
When faceting by date range you can set the lower range to be above the upper range and get a 500.. It looks like this isn't an issue on current prod, we have an alert on current prod that says '2222 to 2020 is not a valid range' when this occurs
The text was updated successfully, but these errors were encountered:
FYI the Clamby issue is resolved (it was still happening after Henry's fix until I restarted the Rails processes), but the deletion issue is still happening. Can you drop the OAI stuff and switch back to investigating this on Monday?
Making one issue to put all the issues I have found from testing era-app-prd.
1
Clamby dependencies are not installed. (will be able to test deposit process once this is done)
2
On deletion of an item through the UI I get this notification:
It looks like the item successfully deletes however.
Note: this doesn't appear to be reproducible locally, I get the message 'Item was successfully deleted!'... This may have to do with clamav acting up
3
The supervisor and department facets do not appear on the left sidebar. When either a supervisor or department is clicked from an item it appears to just return all items in the search.
Here is the sidebar on current prod:
4
It appears that I cannot remove logo from a community. When clicking the 'Remove logo' checkbox and then 'Update Community' the old logo appears to persist. I would assume it would show the standard ERA logo. Setting a new logo with a file works as expected.
Note: this is reproducible locally. The error I get is 'found unpermitted parameter: :remove_logo' and was able to fix it by making it a permitted param. Now to find the best way to do this.
5
When sorting items by date (either oldest first or newest first) from results you get an error when you switch to either the collections or communities tab:
F, [2020-12-08T11:45:43.220514 #653] FATAL -- : [50d6ad2b-cb3b-429e-8b50-300311d5df4e]
[50d6ad2b-cb3b-429e-8b50-300311d5df4e] NameError (uninitialized constant JupiterCore::SolrServices::DeferredFacetedSolrQuery::NameManglingError
Did you mean? JupiterCore::SolrServices::NameManglingError
JupiterCore::SolrNameManglingError
JupiterCore::SolrServices::NameMangling):
Looks like this is due to the param 'sort' being 'sort_year' where communities and collections expect it to be 'record_created_at'? It looks to rescue an error that doesn't exist as well.
6
Searching on this page (https://era-app-prd.library.ualberta.ca/admin/communities OR https://era-app-prd.library.ualberta.ca/communities) appears to not even make a search, all results are always returned.
Notice: This bug exists on current production as well.
It turns out that this is the expected functionality, you need to select from the list and not hit enter. I am going to put up a ticket to improve this functionality to make it more functional/user friendly
7
When faceting by date range you can set the lower range to be above the upper range and get a 500.. It looks like this isn't an issue on current prod, we have an alert on current prod that says '2222 to 2020 is not a valid range' when this occurs
The text was updated successfully, but these errors were encountered: