🇪🇨Ecuador @dmezquia

Initially the queries are set correctly by URL, but when changing the select an error appears. The MR 9 (patch #2) does not work!

+1

+1

+1

Hi, I just uploaded a new release with a fix for the issue with Drupal 11.

Hi, the MR !33 worked OK for me!

Hi, right now I really don't have a solution for this problem, maybe I can review it soon depending on the available time I have, I would start by looking at what I mentioned in comment #2.

Maybe if you think of any solution, comment it or upload an MR, patch.

What the MR does is to initially set the extra fields of the source entity in the destination entity, maintaining the same order of the source and the same location.

Patch: https://git.drupalcode.org/project/entity_type_clone/-/merge_requests/10...

dmezquia → changed the visibility of the branch 3452646-the-extra-fields to active.

dmezquia → changed the visibility of the branch 3452646-the-extra-fields to hidden.

dmezquia → created an issue.

Tested with Drupal 10.2.2 and default Claro admin theme. MR8, patch 8

Tested in Drupal 10.2.2 with default Claro admin theme.

Fix in new release 2.0.4. Thank to all!.

dmezquia → created an issue.

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

@Juc1 Many entrepreneurs and companies, rather than starting to develop a full application with "Drupal", prefer to launch an MVP and that is where Drupal does not fit, they want to create websites quickly, pages, sections... like no-code apps do.

I think that Drupal has not put as much effort into this part because it has been selling itself for more advanced solutions, not to launch quick MVPs.

I think that if a solution could be reached between (Recipes + Single Directory Component SDC + Better and fast pages builder) Drupal would be used much more in other communities that only want to launch Web/MPV quickly to the market.

To reach clients into Drupal to create a quick MVP and then stay in Drupal for a more personalized solution.

I think you can create a custom token and use it for that.

I will review it as soon as I can, thank you very much.

Hi @Arno2Mars,

Are you on the latest version 2.0.3? clean caches too?

For this I uploaded a adjust previously. https://www.drupal.org/project/pcr/issues/3384074#comment-15483319 ✨ Does not appear in views exposed filter block Fixed

If your problem continues, specify versions, screenshot and how to reproduce it.

Another quick and better way, which will be added to the module in the future, is to add the "Save" function for the "Next Step" button.

'#submit' => ['simple_multistep_register_next_step', '::save'],

I am upload a patch for this while it is validated by the community and added to a future release.

Debugging a little I saw that if the "clone" function is removed from here, it works.

It is not clear to me if it is really due to cloning the entity or something else.

For now we would have to continue reviewing.

It should now work ok in the new releases 2.0.2!

Done in 2.0.2 release!

Thank! Done in release 2.0.2

New release added with some adjustments: https://www.drupal.org/project/simple_multistep/releases/2.0.2 →

Hi, this was added backwards in release 2.0.1, I'm reopening it to adjust.

Instead of type: text it became text: label

Perfect! Thank!

There is a new releases 2.0.3 with an adjust, this issue should work fine.

Maybe you are using some custom theme that is overwriting the module CSS?

Hi, could you give more details about this? I have tried it with D10.2.2 and better_exposed_filters 6.0.3 and it works fine, with Claro admin theme and with Olivero.

I can't reproduce it.

Thanks @bircher.

I update the module as soon as I can. Thank you very much.

Hi @andrei.vesterli, thank!

This error also happens when calling a function of a disabled module, patch #2 solves it, since it first validates if the function exists.

Or is there another way to check this so that it doesn't call a function of a non-installed module?

Everything already seems to be going well in the new version 1.6, please @BigDave91 if you have a chance try to testing it too, and if everything is going well, close this issue. Thank you.

I am also getting similar warnings in the .module.

dmezquia → created an issue.

Hi @Grabby, I'll check this as soon as I can. Thank you very much for the feedback.

#129 works for 9.5.9 and 9.5.10, but it only works for a first request, from the second request/change select it doesn't work, it always shows me the same values of the first request, even with clean caches.

@coaston It is a simple patch just to apply an HTML ID to the each container step div. You can inspect the html of each step and you will see an ID like

<div id="step-label-1">
<div id="step-label-2">
<div id="step-label-3">

etc, depending the steps you have.

I'm having the same issue.

dmezquia → created an issue.

Hi maintainers 👋, any update on this ? please if you don't have the time, can you add another maintainer to take over, any developer that you propose as a new maintainer would be great, so that can review the currently open issues and release a new one release.

Or maybe you suggest something else different for this module to go ahead? 🚀

You can do this by overriding or adding a new function to NextStep, example:

In CustomNextStep function add the new logic for updating entity.

/**
 * Implements hook_field_group_form_process().
 */
function my_module_field_group_form_process(array &$element, &$group, &$complete_form): void {
  // Change the submit function of the "next" step.
  if ($next_btn = &$complete_form['actions']['next']) {
    $next_btn['#submit'][0] = [CustomMultiStepManager::class, 'CustomNextStep'];
  }
}

dmezquia → created an issue.

dmezquia → created an issue.

dmezquia → created an issue.

Tested ok with:

Field group Details
- Field group Fieldset

dmezquia → created an issue.

I think that it is not possible (in the current logic) to use the #states for the fields that are not in the same step (check) (for those that are in the same step if it works well), the fields that are not in the same step are not shown and therefore it cannot be done check with the #states.

I think you should look for another alternative like:

- Save the content entity (node, etc) in each step and thus be able to validate with the fields saved from the previous step.
- Find another way to save the previous step temporarily etc, to be able to validate in a next step.

PS: I uploaded a Merge Request ✨ Allow Alter MultistepController Fixed that allows changing the MultiStepController, this gives greater flexibility when adding or modifying custom requirements.

dmezquia → created an issue.

dmezquia → created an issue.

The hook hook_field_group_form_process works ok for me too.

dmezquia → created an issue. See original summary → .

Hi, I have just pushed an MR for review, with these new adjusment the error that I was presenting in the form display and uuid works well for me.

This problem still appears in version 3 and it is impossible to create cloned content.

The fields are cloned but when you go to create a new content /node/add/content_type the fields do not appear, the problem seems to be in the form display that is not being created correctly.

dmezquia → created an issue. See original summary → .

dmezquia → created an issue.

Added!, Thank for reporting.

Added support in new release for Drupal 10!

Added in new release 1.5.