Closed (fixed)
Project:
Lazy-load
Version:
8.x-3.8
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 May 2021 at 08:15 UTC
Updated:
30 May 2021 at 17:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
thirstysix commentedComment #3
henry.odiete commentedlooks like the issue has been solved in 3.8 see https://www.drupal.org/project/lazy/issues/3212294
Comment #4
osmanHi @ThirstySix
I was able to reproduce the same error while upgrading from 3.6 to 3.7 (3.8 returns some other error).
But only if I don't run the updates (
/updates.phpordrush updb) after the upgrade.After running the updates, the Lazy settings page refreshes without an error.
Could you check whether the updates ran successfully?
Comment #5
sunil.yadav commentedHi @Osman,
I am getting same issue on version 3.8
ypeError: Argument 1 passed to Drupal\Core\Condition\ConditionPluginBase::setConfiguration() must be of the type array, null given, called in /app/web/modules/contrib/lazy/src/Form/LazyForm.php on line 324 in Drupal\Core\Condition\ConditionPluginBase->setConfiguration() (line 99 of /app/web/core/lib/Drupal/Core/Condition/ConditionPluginBase.php)
When i am reinstalling It is working.
The issue is array
// Set the default condition configuration.
$this->condition->setConfiguration($lazy_settings->get('visibility'));
is having empty value.
Kindly suggest me.
Comment #6
keithdoyle9 commentedI get the same error on 3.8 (after upgrading from 3.6) when trying to access
/admin/config/content/lazy.When looking at the site itself, I get the following error:
Comment #7
stevenpatzChiming in that I am also seeing these errors. drush updb was run. drush cim was run. On the status page I see this
But the lazysizes library does exist.
I can't get to the lazy settings.
Comment #9
keithdoyle9 commented@StevenPatz - Same here even though it's required and installed in the exact place it was previously.
Comment #10
keithdoyle9 commentedJust tried the dev branch with the latest commit
0c50076from above and I am able to get to the config settings page , but the error is still there in the status page.Comment #11
keithdoyle9 commentedThis seems to have worked for me on the dev branch:
After that, the warning is gone on the Status Report.
Comment #12
thirstysix commentedComment #13
thirstysix commentedYes @keithdoyle9, It works well with 8.x-3.x-dev.
Here is the Patch for 8.x-3.8 version only,
Comment #14
osmanHi, thank you all for feedback. I understand the dev release fixes the issue for all. This will be included in upcoming 3.9 release.