@fabianfiorotto

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

#25 worked for me but take into account that you need to use the raw filter when you are printing the output string otherwise a lot of characters may be escaped.

  $variables['entity_print_css'] = [
    '#type' => 'inline_template',
    '#template' => '<style>{{ output | raw}}</style>',
    '#context' => [
      'output' => implode(PHP_EOL, array_filter($css)),
    ],
  ];

fabianfiorotto → created an issue.

This also happened to me. It is caused because the module "content_moderation" and "worbench_moderation" are enabled simultaneously. The solution is to disable workbench_moderation since it's deprecated.

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

The solution of the Merge request only works for the "Dropdown" widget. I added another solution for the "Nice Dropdown with Flags" widget. We will probably need a different solution for each widget type.

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

fabianfiorotto → created an issue.

I have a problem similar to this one in Drupal 10. If you add a parameter with a numeric key in a view with a full pager.
eg:
https://www.domain.com/my-view?0=

and then you start to use the pager to change the current page you will see that the URL fills with a lot of numbers exponentially.
I think that is messing with my site's SEO because the spiders start navigating the site and spending a lot of resources on those useless URLs.

I updated the module description and placed the image. Let me know if you have more ideas to improve the module description.

fabianfiorotto → created an issue.

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

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

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

fabianfiorotto → created an issue.

I think this is a duplicate of
https://www.drupal.org/project/commerce_mercadopago/issues/3367764 📌 Improve the code Fixed

The bug was reported in 2.0.1. It's an entirely different bug.

I'm trying to run the javascript tests but they start to fail as soon as I change the pager id to something different than zero in the createView method. Is this pager suppose to work along with other pagers on the same page?

I tried changing that value in the code and it seems like Mercado Pago ignores that parameter. I'd consider deleting it from the code.

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

This is ridiculous. I already have trouble convincing front-end developers to use the context parameter in our custom modules (most of them just ignore it since don't understand its logic). Now I have to convince them to use jQuery once. When the rest of the javascript world is moving away from jQuery we are forcing people to use it. It doesn't make any sense. I will disable this module on any site I have to work on.

#214 is working for me on 8.9.x but only for unlimited fields. I added a condition to hide the button when the amount of values is limited.