- Issue created by @dcam
- Open on Drupal.org โCore: 10.1.4 + Environment: PHP 8.1 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - ๐บ๐ธUnited States dcam
The image resolution constraint description should be broken too, but I don't have the ability to test that in my current environment.
- Status changed to Needs work
about 1 year ago 8:57pm 2 January 2024 - ๐บ๐ธUnited States dcam
It's still NW due to #3, but I tested the MR on a 10.2.0 site and a 10.1.x site. The constraint text appeared correctly on both sites. So the BC code works and you shouldn't have to release a new major version.
- Open on Drupal.org โCore: 10.1.4 + Environment: PHP 8.1 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Open on Drupal.org โCore: 10.1.4 + Environment: PHP 8.1 & MySQL 5.7last update
about 1 year ago Waiting for branch to pass - Status changed to Needs review
about 1 year ago 2:02am 3 January 2024 - ๐บ๐ธUnited States dcam
I added the image size keys. Unless I'm mistaken, this should take care of all the issues.
- ๐ฎ๐ณIndia pooja saraah Chennai
pooja saraah โ made their first commit to this issueโs fork.
- last update
about 1 year ago Build Successful - ๐บ๐ธUnited States dcam
@pooja-saraah can you explain why you made these changes? This was a simple big fix. But it looks like you've introduced a bunch of code formatting changes just because. Now the MR is more difficult to review and less likely to be applied. The Drupal community has a long-standing practice of keeping unrelated changes out of patches. Unrelated changes are confusing and make it more likely to cause merge conflicts for other pending patches. Unless you were fixing an additional problem with the code, then please do not go around editing existing MRs. Open follow-up issues to make your edits. And if you were fixing something, then please explain what that problem was.
- Open on Drupal.org โCore: 10.2.1 + Environment: PHP 8.1 & MySQL 5.7last update
11 months ago Waiting for branch to pass - ๐บ๐ธUnited States dcam
The changes introduced by @pooja-saraah resulted in a WSoD with the following error:
The website encountered an unexpected error. Try again later.
Error: Call to undefined method Drupal\bootstrap\Plugin\Preprocess\FileUploadHelp::getRenderer() in Drupal\bootstrap\Plugin\Preprocess\FileUploadHelp->preprocessVariables() (line 133 of themes/contrib/bootstrap/src/Plugin/Preprocess/FileUploadHelp.php).
@pooja-saraah never responded with an explanation of why their changes were made. So I reverted their changes as being both unnecessary and harmful. As a module maintainer myself, I would remove their credit on this issue for those reasons.
- First commit to issue fork.
-
shelane โ
committed d3b65aa1 on 8.x-3.x authored by
dcam โ
Issue #3411962 by dcam: FileUploadHelp preprocessor was broken by Core's...
-
shelane โ
committed d3b65aa1 on 8.x-3.x authored by
dcam โ
- Status changed to Fixed
8 months ago 6:01pm 21 June 2024 Automatically closed - issue fixed for 2 weeks with no activity.