Jean-Paul Vosmeer → credited yustinTR → .
I have updated the host URL in the configuration, which successfully changed the host in both the head and the noscript sections of the body.
There are no additional syntax options specifically for 0 in CSS. To handle a check on '0px' and make it functional.
yustinTR → created an issue.
yustinTR → created an issue.
this works for me
@seanb in my project we check the content like this content.field_YOUR_PARAGRAPH[0]['contents']['#view'].result, but when i debug its breaks on the ['contents'] part because the lazy_load steps comes in front of it. Maybe this helps to fix the issue
Made it cleaner by not removing it but specify it
forgot to run a build
yustinTR → created an issue.
I created the change records and updated the issues summary.
I'm going to work on the change record.
thnx @TR. The upgrade status module suggested that i needed to change that accescheck before, because the original issue was for the alpha-6 branche. but i have fixed the things you said in this patch
added some once annotations
Fix some spacing issues & created a interdiff
I edited the patch so it works for the 8.x-1.x-dev version, the previous patch was ment for the alpha-6 version. For the interdiff the changes are to big so i got a error while create a interdif.
the getpath functions also needs to be changed in drupal 10, i edited it and tested it and for me its works
yustinTR → created an issue.
The solution stefan.butura suggested worked fine for our project
yustinTR → created an issue.
Sorry for another typo
@diqidoq the execute() function also needs te be changes to accessCheck->execute()
I have tested the automated patch and add a couples thins so i works fine now for me.
And again sorry for the typo in my last patch
Sorry i forgot to edit the info.yml in my last patch
Hi @omkar_yewale
Thanks for the advice.
yustinTR → created an issue.
The core: 8.x in the info.yml file also need to be removed
yustinTR → made their first commit to this issue’s fork.
@Ranjit1032002 Your patch inapplicable as the $variable question might be undefined in a certain situation. this can lead to exceptions. I think my patch might be it. I suggest to put mine in review
yustinTR → created an issue.
If I do not want this functionality on my website (because I really want this visitor to wait a couple of weeks before he can login in again), there is now a way to disable it. And removed the code style fixes.
yustinTR → made their first commit to this issue’s fork.
yustinTR → created an issue.
yustinTR → created an issue.