🇷🇴Romania @vasike

vasike → created an issue.

Maybe it would be good to mention those 2 modules - Revision Manager → & Revision Delete Tools →
on project page at Similar Projects section

It seems there are new modules with such capabilities https://www.drupal.org/project/revision_manager → and https://www.drupal.org/project/revision_delete_tools →

Maybe focus there will help to get stable releases.

It seems components info files requires core_version_requirement at least trying to run drush command within latest D11 ...

created a MR with those updates ...

vasike → made their first commit to this issue’s fork.

vasike → changed the visibility of the branch 3086311-localized-content to active.

vasike → changed the visibility of the branch 3086311-localized-content to hidden.

@anybody thanks for the feedback ...
And yes, you're right ... to have new branch it's mandatory ...

about (Co-)maintaining ... I just needed to make a D11 upgrade in a project that use this module, so this was needed not to introduce "other things" in the upgrade.
But as for this module, I won't contribute more to, also, duplicate the cloning modules available.
.
probably if I'll need to start new project with cloning needs, probably an ECA model should be enough.

Little update and it seems it works on both D10 and D11 ... on the same project after a Drupal upgrade
So I think it could be considered RTBC

vasike → made their first commit to this issue’s fork.

vasike → changed the visibility of the branch 3552555-domain-3-x to hidden.

actually it's not that simple ... it seems Domain 3.x it's kind of refactor ... at least for what Domain language needs and uses.

So this will require a new version of this module compatible with Domain 3.x

rename and update the title

similar (not the updates, only the idea) Domain extention module issue https://www.drupal.org/project/domain_theme_switch/issues/3551634 📌 Create new 3.x version compatible with Domain 3.x Active

MR available ... I don't think the failures are from this update
so Needs review

MR available ... I don't think the failures are from this update
so Needs review

vasike → created an issue.

vasike → created an issue.

new MR created
also added a patch with the same changes.

vasike → changed the visibility of the branch 3086311-make-it-work to hidden.

vasike → made their first commit to this issue’s fork.

MR available for this as described in the description.

Probably it's on "Needs work" ... if tests are needed.

But for start I'll put on "Needs review"

vasike → created an issue.

I rebased the MR with latest - already "old and well known" updates about Allow wildcard path conditions
... sorry if it will mess-up with some not updated module usage ...

So definitely this should be committed ... it's too much to run clear cache ... even, actually, the edit has no updates...

vasike → made their first commit to this issue’s fork.

this could be also related with the nested paragraphs cloning https://www.drupal.org/project/quick_node_clone/issues/3183249 🐛 Nested paragraph support RTBC
the create duplicate also should be covered by Paragraphs recursively .

Also created a MR with the same change.

vasike → changed the visibility of the branch 3546997-createDuplicate-not-new-condition to active.

vasike → changed the visibility of the branch 3546997-createDuplicate-not-new-condition to hidden.

For now ... a quick ... patch ..

vasike → created an issue.

I meant this text

Note: This project is not yet stable. See #2887926: Make a stable release with security coverage

which was added by a maintainer and includes this issue link ....

And not the usual d.o text ... besides the versions/releases

This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.

And it's not case anymore as text is

Stable releases for this project are covered by the security advisory policy.
Look for the shield icon below.

p.s. sorry for the noise ... but it could drive away people that really need this module ... and thanks

As I said previously the project page should remove the the note about this issue

isn't this done?

I think the project page should updated by removing the note about this ...

Stable releases for this project are covered by the security advisory policy.
Look for the shield icon below.

applied all @alexpott's suggestions, as "they make sense" (at least and thanks) ... back to review

indeed, there were some small updates on the texts to be checked - different spaces/new line.
Updated the test and remove those extra spaces/newlines from checks.
back to review

MR updated with latest 11.x + some feedback for MR review.

Let's try again a review. thanks

Updated the MR with latest 11.x: solving conflicts and Fix test according with field ui API updates - issue #3386762 ✨ Use modal in add new field flow Active .

Updated the MR with latest 11.x: solving conflicts and Fix test according with field ui API updates - issue #3386762 ✨ Use modal in add new field flow Active .

no feedback ... consider fixed .... closing

@g4mbini

the documentation is wrong there ... actually the content ... it's about the drawer content - as Open Drawer text, please check the examples
It's not about the page content

<div class="drawer">
  <input id="my-drawer" type="checkbox" class="drawer-toggle" />
  <div class="drawer-content">
    <!-- Page content here -->
    <label for="my-drawer" class="btn btn-primary drawer-button">Open drawer</label>
  </div>
  <div class="drawer-side">
    <label for="my-drawer" aria-label="close sidebar" class="drawer-overlay"></label>
    <ul class="menu bg-base-200 text-base-content min-h-full w-80 p-4">
      <!-- Sidebar content here -->
      <li><a>Sidebar Item 1</a></li>
      <li><a>Sidebar Item 2</a></li>
    </ul>
  </div>
</div>

Here is an example I tried for a project.
Using an hamburger svg for the drawer and the entire header region.
Without duplicate the "menus" code for responsive ...

<div class="navbar-end gap-4">

      <div class="drawer lg:drawer-open w-auto">
        <input id="nav-drawer" type="checkbox" class="drawer-toggle" />
        <div class="drawer-content flex-none lg:hidden">
          <label for="nav-drawer" aria-label="open sidebar" class="btn btn-ghost">
            <svg
              xmlns="http://www.w3.org/2000/svg"
              fill="none"
              viewBox="0 0 24 24"
              class="inline-block h-6 w-6 stroke-current">
              <path
                stroke-linecap="round"
                stroke-linejoin="round"
                stroke-width="2"
                d="M4 6h16M4 12h16M4 18h16"></path>
            </svg>
          </label>
        </div>
        <div class="drawer-side lg:relative lg:h-auto z-1500">
          <label for="nav-drawer" aria-label="close sidebar" class="drawer-overlay"></label>
          <div class="bg-base-200 min-h-full w-full md:w-auto md:min-w-1/3  p-4 flex flex-col items-center justify-center">
            <label for="nav-drawer" aria-label="close sidebar" class="lg:hidden p-5 p-t-20 p-r-20 w-full text-center bold cursor-pointer">x</label>
            {% block header %}
              {{ header }}
            {% endblock %}
          </div>
        </div>
      </div>

    </div>

So, imho, this could be a good candidate for better navbar component also for this theme/project...

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

p.s.2. I know it's a S issue ... but ...

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

p.s. if this still an issue on the latest 2.x version, please feel free to re-open and update the version accordingly.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

As Drupal 7.x and also modules 7.x versions "ended their lives", closing the 7.x issues.

And thanks for participating and using the module.

sorry to re-open this issue, but I totally agree with @anybody, so @pdureau, please update the project page with this very useful comparison
info.

and thanks a lot.

This feature looks covered by another module - https://www.drupal.org/project/colorbox_media_video →
But I agree it would be nice to have it here ... So maybe a combination of existing MR solution with the module solution would be best.

MR threads addressed ... so back to review.

MR threads addressed/closed + CR Draft created ... so back to review.

This is not only for AI, nor only for ECA, nor only for VBO, nor only with Action UI
It's just an action/config that could be used for various Multilingual cases using the Core Recipes approach.
Let's say for Drupal CMS Multilingual CMS.
Or For a Multilingual recipe, that does not need any of other contrib modules, as maybe there are other specific custom modules to help with this action.
If we move this to any of AI, ECA, VBO or other ... then the need of such Action/Config will require extra dependencies and this is not specific to these modules.
For me, it's just Drupal Core ... but maybe I'm too "subjective".

@szantog thanks for the issue and the proposal MR

I'm not sure about this issue is really a bug.
So first thing: did you try your View(s) with autocomplete_contextual (Allow Contextual filters to apply to this filter label) option selected for your Autocomplete filters?
This option is disabled by the default, as it was introduced at the later stage, when this kind of issues needed to be covered.

If this "hint" still do not solve this issue case, this mean we need a new feature to cover ...

For now i'll change the issue type and status ... to get the "new results" first.

Second: this module has tests (Gitlab CI/CD pipeline) for while, so this means whatever MR is proposed, it needs to be Green all Gitlab CI/CD pipelines should pass - before "Needs review" status.
Other wise, it means the solution/isssue "Needs work".

I confirm this an issue not from this module ... but custom twig template issue

Besides the Views case ... it seems there could be also a case for Fields templates.
maybe it helps other people.

So, similar with #20 solution, for fields, please check the items usage

    {% for item in items %}
      <div{{ item.attributes.addClass('whatever-class') }}>{{ item.content }}</div>
    {% endfor %}

instead of

    {% for item in items %}
      <div>{{ item }}</div>
    {% endfor %}

@shelane I think you could close this as won't fix or works as designed ... as it's not about this module.
however I put it on Needs Review for now, just for ... action ... closing.

MR created, so Needs Review

question: Could the _utilities.scss be emptied?

is this used anywhere?

    ("columns": (property: columns,
        class: columns,
        responsive: true,
        values: (2: 2,
          3: 3,
          4: 4,
          5: 5,
          auto: auto,
        ),
      ),

what should it do/solve?

vasike → created an issue.

new MR available
https://git.drupalcode.org/project/ui_suite_daisyui/-/merge_requests/140

Which updates the previous one:
- Use the daisyUI logo/icon
- Delete the extra files that "needed renaming" - not actually needed
- Fix the Regions and libraries
- Remove not needed files ... empty or inherited from the base theme.
- Emptied generated CSS file.
- Update README file - simplify the process + remove older Drupal info.

I could generate an working theme just with

php core/scripts/drupal generate-theme my_daisyui_theme --starterkit ui_suite_daisyui_starterkit --path themes/custom
npm install
npm run build or npm run dev

commands

vasike → made their first commit to this issue’s fork.

solving bot patching issue ... MR updated with latest 11.x

Created a MR with new uid option for import only using the account_switcher service.

I tested within a project doing Migrate Source CSV dependant migration imports, using ECA Models to control different entities data.
And it worked as expected.
Needs review ... for now ... to get some feedback.
Do we need also for other "commands"?

Note: For ECA models "alteration" this could also achieved, but currently the option is to have the user set for all models ...

Also it seems the issue was previously for an older version, so initially I created a "bad" branch
which seems I can't delete it
https://git.drupalcode.org/issue/migrate_tools-3134245/-/tree/3134245-ru...

vasike → changed the visibility of the branch 3134245-run-drush-imports-uid-option to hidden.

vasike → made their first commit to this issue’s fork.

@daniele.chiminelli Could you please, make sure you have also the relationship set for the Title field to be displayed.
Maybe you need to Add new Title field just for this relationship ...

This module it uses its own fields set.

it should work ... imho.

This could achieved with the "proposal" from https://www.drupal.org/project/drupal/issues/3506152 ✨ Translate Action for Content Translation module Active

@jurgenhaas already checked ... but more tests and feedback could help.

Added as related issue.

This could achieved with the "proposal" from https://www.drupal.org/project/drupal/issues/3509597 ✨ Image Style Action plugin for image files Active

Of course make sure the Image Style uses imageapi_optimize ... properly.

Added as related issue.

This could achieved with the "proposal" from https://www.drupal.org/project/drupal/issues/3509597 ✨ Image Style Action plugin for image files Active

Added as related issue.

Updates on the MR and issue summary ... support for generate Derivatives ...

p.s. there could be issues for action access because of file access issues like
https://www.drupal.org/project/drupal/issues/3450005 🐛 File entity update is allowed only for user who has uploaded the file Active

MR available - first attempt

For start:
- What's not clear?
- What's missing?
- Naming (for classes/action) - this big one topic
- What's next