@nojj

I just don't get how to do that with the example modules...

got it. Thank you!

just tried it with beta-2 and now the link /admin/config/workflow/eca-condition is completely missing in menu and the site is not found.

nojj → created an issue.

but only for D7

I have the same question.
maybe this could be a solution:
https://www.drupal.org/project/commerce_license_access_control →

did you find a solution for this?
I am struggling at the same problem...

nojj → created an issue.

@jsacksick: just wanted to help testing the patch.
I did run cron manual and noticed that the license is still active for the first time, as normally we use only unlimited licenses.

right now, I am running a test with rolling intervall of 2 minutes.
but the license stays active as the 2 minutes went by...

thank you for the patch. fixes the use for me!

Hello @renotag,

thank you for your fast clarification.

the added Matrix should help other with the same question.

just upgraded successfully to v4.0

nojj → created an issue.

nojj → created an issue.

Hi,

i have the same problem. Any progress here?

nojj → created an issue.

Thank you for your detailed answer.

just tried to update corresponding modules in a DEV.
tried to update the modules one after another and always got blocking errors from composer.
the only command that seems to work, is requiring all modules at one:

composer require drupal/slick_extras:^2.0 drupal/slick:^3 drupal/slick_views:^3 drupal/blazy:^3 -W

nojj → created an issue.

nojj → created an issue.

running IEF 3, installing the latest release of ANU still gives me the composer error:

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/anu_lms[2.10.0, ..., 2.10.2] require drupal/inline_entity_form ^1@RC -> found drupal/inline_entity_form[1.0.0-rc1, ..., 1.0.0-rc17] but it conflicts with your root composer.json require (^3.0@RC).
    - drupal/anu_lms[2.10.3, ..., 2.10.6] require drupal/inline_entity_form ^1.0@RC -> found drupal/inline_entity_form[1.0.0-rc1, ..., 1.0.0-rc17] but it conflicts with your root composer.json require (^3.0@RC).
    - drupal/anu_lms 2.10.7 requires drupal/inline_entity_form ^1.0@RC||3.0@RC -> found drupal/inline_entity_form[1.0.0-rc1, ..., 1.0.0-rc17] but it conflicts with your root composer.json require (^3.0@RC).
    - Root composer.json requires drupal/anu_lms ^2.10 -> satisfiable by drupal/anu_lms[2.10.0, ..., 2.10.7].

i am on Drupal core 10.2.2 and Mail Login 3.0.
and I get warnings that Mail Login is unsupported.

are there any security concerns with V3.0?
what is the reason for declaring it as unsupported ?

nojj → created an issue.

thanks for the patch!
strange thing: I did not get this entries anymore without doing anything.

I would love to have that feature.
is there any progress?

is eher an option to use the wildcards for a "section global password"
we would like to use one global password for all URL beginning with
/xxx/*
but have different passwords for individual urls with a more specific url like
/xxx/abc

at the moment if the password for /xxx/* is not accepted for urls like
/xxx/abc

if a different password is set to this urls

any ideas to solve this?

for my intention, I am not missing anything right now.

"maybe" was meant more as a possible improvement - I haven't checked this. the thought just came to my mind. if the two hooks are more or or less the same, then so be it.

Thanks @mxh
there is a litte typo typo in the filename: tar_.gz
but it is a great help and indeed, it is possibly to show/hide blocks with eca_access.

maybe using hook_block_access would be a little bit more flexible, as eca_access can only react on ECA Access events.
https://ecaguide.org/plugins/eca/access/actions/eca_access_set_result/

patch #12 does not apply to V2.3.0 of this module.
but the bug seems to be fixed without the patch. Maybe a notice in the release note would be good.

nojj → created an issue.

sounds good to me.
willing to test ;-)

what is the current state of this patch? would be nice, to have this future in the stable version of the module.

nojj → created an issue.

nojj → created an issue.

for us the patch#21 seems to solve the problem too.
would be nice, to have an update of the module.

thanks. you are right. markup gets removed if using ckeditor.
so maybe it shouldn't possible to select creditor for "plain text"

thanks for your answer.
I can confirm this works as fallback option with ck4

nojj → created an issue.

same here after update to 10.2.0

I can confirm the problem of @jrb that there is a problem with activating "Limit allowed HTML tags and correct faulty HTML" filter.

is there any progress in this?
needing title and alt tag as well

I did the upgrade to D10.1.6 and the module is shown as Facebook Page Plugin 8.x-2.3

Works for me. Thank you!

in my Case: Drupal core 10.1.6 and Cookie Content Blocker 2.2.5

I tried to make a patch.
seems to work in my local dev.

I just tested this with a new D10 installation.

if using the Cookie Content Blocker - Media module, the video is not displayed after giving consent.

just displays

// //]]>

nojj → created an issue.

nojj → created an issue.

I need to override some menu links in a current project.
what is the current state of this?
how can I help with a test coverage?

nojj → created an issue.

nojj → created an issue.

after updating to V1.3.2 I seem to have the same issue.
Tokens are not replaced.
Even [site:name] is not replaced.
Any ideas?

this patch seems to fix the issue for me even in V 1.16:
https://www.drupal.org/project/we_megamenu/issues/3164302 →

nojj → created an issue.

I just added a MIT license URL for testing:

license:
     name: MIT
     url: https://opensource.org/license/mit/
     gpl-compatible: true

nojj → created an issue.

thanks.
what about security coverage for the new D10 release ?

Hello,

Thanks for your reply. Looking forward to V3.
will the updrade be complex? I am asking, because I am still on V2.04 and and have to do editing to update to V2.0.5. So maybe it's better to wait for V3, if release ist soon.

nojj → created an issue.

1.4-rc1 seems to support D10, but has no security coverage.
what is missing for a stable release?

Thank you very much!

nojj → created an issue.

did you find a solution for this?

as written above. sorry, I was still in 2.0.0. no problem with 2.1.0

sorry, was still on V2.0.0 with V2.1.0 the warning is gone

nojj → created an issue.

I have this issue with the regular release of this module. the patch applies for this version too, but I am wondering when a new version will be released...

problem was on provider side.

nojj → created an issue.

nojj → created an issue.

why is this closed?
it doesn't seem to be D10 ready.

I got this error running drush updb with PHP 8.1 and Drupal 9.5.8.
ParseError: syntax error, unexpected '->' (T_OBJECT_OPERATOR) in Composer\Autoload\{closure}() (Zeile 41 in /kunden/443737_88138/webseiten/erza-dev5/d9/web/modules/contrib/cookie_content_blocker/modules/cookie_content_blocker_media/src/Form/MediaSettingsForm.php)

after that, I updated to 2.1.1 and didn't get the error again while drush updb.

do I still need the patch?

@mxwright did another test. coming from V1.4 with patch #24, I could successfully update to V1.6 (stable version) and then apply patch #39. And wildcards seem to work.
that would be nice, because DEV-versions of modules are not listed in Drupal for pending updates.

@mxwright thank you very much for the detailed explanation!
curious if this makes it into the stable release...

so you are are using the latest dev with patch #39 in your current projects?
and is the security-fix what you describe in #34 or something else?

@mxwright, thanks for your response.
in a local test with V1.6 it seems with wildcard * the protection is not applied.
regarding latest dev and patches: is the security issue fixed in V1.6 included in the latest dev?

a quick look into the module code, it seems the patch mostly made it to V1.6, only the descriptions for wildcard usage seem to be missing.
can someone confirm this is the case?

it seems to work with wildcards e.g. * and version 1.6, but the description hints from patch #24 are missing.
Please enter the relative path and its corresponding password. When user opens this url, they will asked to enter password to view this page. For example, "/node/5", "/new-events" etc.
I thought, that indicates that patch did not make it to the release...
Can someone confirm wildcards are supported with V. 1.6 ?

I used patch #24 with version 1.4 of this module.
Now I updated the module to 1.6 but the patch can not be applied.

Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2020-05-19/2890122-24.patch

an suggestions ?

sounds to me, that for now, you get D10 compatibility, until CKEditor4 is EOL...
but you are right, maybe focusing on https://www.drupal.org/project/ckeditor_div_manager/issues/3322722 ✨ CKEditor 5 Compatibility Fixed would be nice.

ckeditor module is no longer maintained because of EOL of ckeditor4
https://www.drupal.org/project/ckeditor →
shouldn't this module be compatible with ckeditor5 to be Drupal 10 ready?

nojj → created an issue.

nojj → created an issue.