Closed (duplicate)
Project:
H5P - Create and Share Rich Content and Applications
Version:
8.x-1.0-rc17
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Apr 2020 at 16:17 UTC
Updated:
11 Jun 2021 at 09:06 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
dakala@alasda: This is an issue in the vendor package not in the Drupal module itself. It's been reported in the H5P issue queue here: https://github.com/h5p/h5p-php-library/issues/84. Interestingly enough, there's already a fix in the master branch:
https://github.com/h5p/h5p-php-library/blob/743147698f56b0433fe3bcb755d7...
https://github.com/h5p/h5p-php-library/blob/743147698f56b0433fe3bcb755d7...
It's a straightforward fix you can implement manually until there's an H5P release pulled into Drupal from the module.
Comment #3
daniel kulbeOnce those libraries get updated, the module itself needs to be updated as well.
Comment #4
somersoft commentedUntil the change makes it way through, I have attached a patch file created from this commit PHP 7.4 fix, don't use curly braces for array/string offset
Example code for composer.json.
Comment #5
catchIt might be useful for the Drupal h5p module to loosen the requirement slightly in composer.json - so that project can update to a dev version, or a new tag when one is released.
Comment #6
firstlut commentedHey, guys!
I had trouble with the patch at #4, so I ran composer in verbose mode, and it couldn't find the files to patch. Turns out the file references were missing the folder structure:
a/h5p-development.class.phpinstead ofa/vendor/h5p/h5p-core/h5p-development.class.phpI don't know why this didn't turn up when I tried to make my own yesterday, but anyway.
Hope this helps.
Comment #7
vm commentedPatch in #6 works as expected. I applied it manually so I can't state if there are any issues with composer patch or patch in general.
Moving to needs review.
Comment #8
kwiechmann commentedSuccessfully applied patch #6 via composer. The patch itself works for me.
Comment #9
pjotr.savitski commentedYou should probably close the issue as the version rc18 solves this issue.
Comment #10
paalj commentedThis is already fixed in the vendor library