🇷🇴Romania @gge

Just tried 50df7a51 and no errors. The filter is changed with the token value. Everything work as expected.

Thank you!

I tried and it doesn't work but there are no errors. Also [new:value] is not replaced when displaying a message.

gge → created an issue.

Understood, thank you very much!

When commenting out $form_object = clone $form_object; all the values are displayed on node add, the issue seems to be solved, but are there any side effects if that line is removed?

Thanks!

Back with additional information:

All the values are correctly displayed when the node is created if the field is not unlimited.

Now the question is how can we get all the values if the field is unlimited?

Thank you!

gge → created an issue.

Thank you!

For me the error is gone by adding use Drupal\Core\Config\TypedConfigManagerInterface; to the use statements and changing the constructor from:

  public function __construct(ConfigFactoryInterface $config_factory) {
    parent::__construct($config_factory);

to

  public function __construct(ConfigFactoryInterface $config_factory, TypedConfigManagerInterface $typed_config_manager) {
    parent::__construct($config_factory, $typed_config_manager);

gge → created an issue.

Another use case where this patch is useful: https://www.drupal.org/project/calendar_view/issues/3403103 💬 Stay on same month/week after exposed filtering Needs review

Hello,

I can confirm that in my context the message disappear. I'm gonna stress the inline entity form build event for a while and will report of there will be any problems. For now everything seems to work very good!

Thank you very much!

gge → created an issue.

Webforms are not using Drupal's form API, that's why the form events in eca_form are never dispatched when working with a webform.

My initial thought was the same but ECA 2 works very well with webforms, just like with entity forms. All form events (build, processing, afterbuild), conditions, actions (defaut values, access to fields, requiring fields etc.), tokens, rendering views, adding ajax handlers to fields and manipulate them, changing submit button label, etc... It can even manipulate address → fields inside webforms.
It's a wonderful and unexpected combination for those who want/need to use something else instead of nodes.

The only thing (untill now) that doesn't work for me is to manipulate the default value of Date field type. A workaround could be the Date/Time field that come with webform. ECA manipulate this type of field very well so I decided to use it instead of date (and hide the time input).

Thank you very much for this integration!

gge → created an issue.

Thank you very much for the detailed answers, impressive as always!
I'm gonna try your advice from #9 and will hide the "Add another item" button. Since the form will be used internally, this trick is enough.

Thanks again for all your work ~

In /var/log/apache2/error.log is nothing recoreded and Drupal logs only this:

gge → created an issue.

gge → created an issue.

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

Just wanted to mention that #31 doesn't work with Drupal Symfony Mailer 1.4.1 but it does with 1.3.2.

Sorry, my mistake...

gge → created an issue.

You could try #2681953-45: Allow exposed form to preserve URL query parameters → and if using B.E.F you also need 🐛 Allow exposed form to preserve URL query parameters Needs work . Then go to the settings of the "Exposed form style" and fill out the "Preserve query parameters from URL".

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

$defaults = $field_config?->getDefaultValueLiteral()[0]; fix the error but I'm also interested to see why $rrule data can't be retrieved. Where should we start?

Thank you~

When commenting out $defaults = $field_config->getDefaultValueLiteral()[0]; everything works as expected, the instance can be overwritten / rescheduled (of course there's an warning Undefined variable $defaults). However probably there are some side effects when doing this...

My setup is pretty standard... It's an attached Smart date field to a node, attached are the settings.

Anyway, I placed var_dump($field_config); inside SmartDateOverrideForm.php just before $defaults = $field_config->getDefaultValueLiteral()[0]; and it returns NULL, probably that's why I'm getting the error.

Btw in your tests did you use php 8? I'm using php 8.1.18...

I also tested on simplytest.me, there's no error when trying to override a date but they are using php 7.

Thanks.

Just tried downgrading to Smart Date 3.7.2 and the same thing... Can't override (reschedule) instances.

gge → created an issue.

Hello,

Just tried #2 and for me is working in case of batch processing.

Thank you~

@omkar_yewale your fix does the trick, thanks~

@robotjox you're welcome but not sure if the right solution is to comment out that line. As @matthieuscarset mentioned here 🐛 Calendar doesn't show results when using pagination "Calender by month" Fixed , "Sort order is always ASC inside calendar days (e.g. in order to keep multiday events always at the top)"

Hello,

Applied the patch manually against version 2.1.1 and got this:
Got error 'PHP message: PHP Fatal error: Nesting level too deep - recursive dependency? in /var/www/public_html/web/modules/contrib/calendar_view/calendar_view.module on line 137'

Line 137 is:
array_multisort($array, SORT_ASC, $list);

The server is running php 8.1.18 (memory limit 2304M) and drupal 9.5.3.

Thanks~

gge → created an issue.