bug #10012
closedFix failing SpecimensTreeViewTest for dataportals after debian11 migration
100%
Description
copied from #9972
First check if there is any strange behavior for specimen trees (and maybe others) due to the debian11 upgrade
- Ignore on SpecimensTreeViewTest due to problem with "squeeze" (Unable to locate element: {"method":"id","selector":"squeeze"})
*** Element info: {Using=id, value=squeeze} at sun.reflect.GeneratedConstructorAccessor13.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:206) at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:158) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:678) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:363) at org.openqa.selenium.remote.RemoteWebDriver.findElementById(RemoteWebDriver.java:413) at org.openqa.selenium.By$ById.findElement(By.java:218) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:355) at eu.etaxonomy.dataportal.pages.PortalPage.getDataPortalContent(PortalPage.java:443) at eu.etaxonomy.dataportal.selenium.tests.reference.SpecimensTreeViewTest.loadPage(SpecimensTreeViewTest.java:62) at eu.etaxonomy.dataportal.selenium.tests.reference.SpecimensTreeViewTest.switchToView(SpecimensTreeViewTest.java:56)
Files
Related issues
Updated by Andreas Müller about 1 year ago
- Copied from task #9972: Upgrade edit-integration added
Updated by Katja Luther about 1 year ago
Tested the tree view with local portal installation connected to the same cdm instance (https://int.e-taxonomy.eu/cdmserver/integration_reference/) -> works
Tested other taxa in reference portal, for example https://int.e-taxonomy.eu/dataportal/integration/reference/cdm_dataportal/taxon/58dfe85b-74d6-4bcd-bf75-a3be54d11fb9/specimens -> works
But opening https://int.e-taxonomy.eu/dataportal/integration/reference/cdm_dataportal/taxon/d245083e-3bda-435f-9bb3-bdc2249ff23c/specimens results in '500 Internal Server Error'
Inspecting the cdm_server.log does not show any problems. Only "HHH000179: Narrowing proxy to class eu.etaxonomy.cdm.model.occurrence.MediaSpecimen - this operation breaks ==" and "HHH000179: Narrowing proxy to class eu.etaxonomy.cdm.model.taxon.Taxon - this operation breaks ==" but this should not result in an Internal Server Error
Updated by Katja Luther about 1 year ago
- Status changed from New to In Progress
The problem is caused by the Specimen CEDiT 2017E68. If this is used as SpecimenTypedesignation or the taxon is used as determined taxon, then the Server Error appears. Removing this specimen everything works fine.
The url https://plants.jstor.org/stable/viewer/10.5555/al.ap.specimen.linn-hs1310-54 causes the problems.
adding the JSTOR image viewer link to a specimen in a production database works, so this problem seems related to the debian11 update, because it does not appear on any other system.
error is: PHP Fatal error: Call to undefined function curl_init() in /var/www/drupal-7-cdm-dataportal/modules/cdm_da taportal/lib/FaviconDownloader.php on line 261, referer: https://int.e-taxonomy.eu/dataportal/integration/reference/cdm_dataportal/taxon/d245083e-3bda-435f-9bb3-bdc2249ff23c
report page of the portal says the php version is php5.6, but composer diagnose says php 7.4
Updated by Andreas Müller about 1 year ago
- Due date changed from 04/08/2022 to 05/06/2022
- Start date changed from 04/06/2022 to 05/02/2022
Updated by Katja Luther about 1 year ago
Updated by Katja Luther about 1 year ago
Updated by Katja Luther about 1 year ago
- % Done changed from 0 to 80
php5 needed to be disabled and php7.4 enabled. This is done and pages with jstor image viewer as url are displayed correctly now. Reenabled the tests again.
Updated by Katja Luther about 1 year ago
- Status changed from In Progress to Closed
- % Done changed from 80 to 100
Tests are ok again, so we can close this ticket.
Updated by Andreas Müller about 1 year ago
- Related to task #10008: Cleanup after server upgrades added