ok I ran a clear cache (clear all cache ) but I am still seeing the two problems listed in upgrade status. Did I misunderstand you request? let me know if there is anything I can do/info to provide to help resolve this.
Thanks,
GF
wow thanks for the quick response. I updated but upgrade status shows 2 problems
File name Line Error
PHPStan failed 0
PHPStan command failed:
/usr/bin/php /var/www/html/drupal/vendor/bin/phpstan analyse --memory-limit=1500M --error-format=json --configuration=/tmp/upgrade_status/deprecation_testing.neon /var/www/html/drupal/modules/views_cumulative_field
Command output:
Empty.
Command error:
PHP Deprecated: Return type of DrushBatchContext::offsetSet($name, $value) should either be compatible with ArrayObject::offsetSet(mixed $key, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/drupal/vendor/drush/drush/includes/batch.inc on line 41 Deprecated: Return type of DrushBatchContext::offsetSet($name, $value) should either be compatible with ArrayObject::offsetSet(mixed $key, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /var/www/html/drupal/vendor/drush/drush/includes/batch.inc on line 41 RuntimeException thrown in /var/www/html/drupal/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/ClassWriter.php on line 113 while loading bootstrap file /var/www/html/drupal/vendor/mglaman/phpstan-drupal/drupal-autoloader.php: Unable to create directory: /var/www/html/drupal/core/tests/Drupal/TestTools/PhpUnitCompatibility/PhpUnit8/../../../../../../sites/simpletest
modules/views_cumulative_field/views_cumulative_field.info.yml 0 Value of core_version_requirement: ^8 || ^9 is not compatible with the next major version of Drupal core. See https://drupal.org/node/3070687.
genfoch01 → created an issue.
genfoch01 → created an issue.
genfoch01 → created an issue.
I updated drupal core to 9.5.10 saw your responses so I updated security review to 2.0.1 and it is working.
the other installation I followed the same process but still get the error.
unfortunately I have to talk to the admin to get the Apache error logs( the access logs I do have access to do not give me the error details ).
I will update once I have them
genfoch01 → created an issue.
genfoch01 → created an issue.
just FYI gisle was correct. The security team is working on this.
https://www.drupal.org/project/drupal/issues/3356283 📌 Fork laminas/laminas-diactoros Fixed
Hi and thanks for your response. I was not aware of the security link you provided ( I realize this is due to my laziness )
I will check there and try to find out if its already been reported.
I completely understand that patches especially to an underlying module frequently need a longer turnaround time because of the need to do full unit testing and the like.
GF
first, Thank you for the quick responses I really do appreciate your time.
I might be able to attempt to upgrade laminas-diactoros to 2.18.1 but would not have any way to fully test it to know if something important broke. so I don't think that's really an option for me.
My site ( one of them anyway) has dependencies on modules that have not yet been updated to include Drupal 10 support so removing them is not really an option for me either.
in terms of scope, every Drupal 9 installation has this same vulnerability since laminas-diactoros is a core file and the version used by Drupal 9.5.x is listed as being vulnerable to it.
at least that's how it appears to me.
This bug is listed as severity 7.5/10 according to the NIST. Are you saying Drupal is not doing security patches on 9.5.x?
I thought Drupal 9.x was getting security updates still. Also some of the modules I use do not yet support Drupal 10.
I have this issue on two different installations. Is this a known thing of which I'm ignorant? Does available updates aways show your contrib modules as up to date?
I uninstalled the module and then deleted the module directory. Then I reinstalled it but I am getting the same result.
I have deleted it from my production system because I can't seem to update with out it breaking.
I have two different installations with the same issue.
sorry for the late response. I fixed my issue via database update.
here is how i did it:
note: I do not advocate messing with the drupal db, so use at your own risk. I am not a Drupal expert, I would say this solution is a hack.
My case was easy I needed to change all comments owned by one user to another.
I got the user list with
select uid,name from notesusers_field_data;from there i found the uids I needed to change.
the comment uid field is stored in table notescomment_field_data
update notescomment_field_data set uid=replace(uid,1,2);this query changed all comments owned by admin(1) to user 2
note: you should have your site in maintenance mode before trying this
always have a backup because things go wrong (I have a virtual machine so i took a snapshot )
once the change is complete, you will need to clear your cache.
my drupal cache is set to "no caching" but I did not see the results of my change until I cleared it.
I tested this twice, so "no caching" really means mostly no caching.
I hope this helps,
GF