Submission tokens disappeared and stopped working

You found a post from someone else with the same issue posted a month ago. Would you please share a link to that?

Hi, thank you for your comment. I edited the issue with the link to the post → .

Up, anyone?

Any chance you also have webform_rules and/or Commerce (and/or commerce_webform?) -- I started having issues with missing submission IDs, but I have all of these modules ^^

And, do you see anything in "Recent log messages" when you submit the form?

I recently updated webform 7.x-4.25 => 7.x-4.26, and webform_rules 7.x-1.6 => 7.x-1.7. After these updates, my rules that add products to the shopping cart don't work, *and* watchdog/dblog/"Recent log messages" shows notices and a warning that indicate that the submission ID is missing. (I have no recent updates to Commerce or Commerce Webform.)

I tried downgrading webform to 7.x-4.25, and it didn't help, my shopping cart was still broken.
I tried downgrading webform_rules to 7.x-1.6, and (after clearing cache), the problems went away, my shopping cart works again (phew).

So, I'm leaving it at that -- idk if this will help, but, sharing just in case!

-------

P.S. The dblog messages I got:

Notice: Undefined index: components in commerce_webform_get_products_from_webform_submission() (line 283 of /path/to/mysite/sites/all/modules/commerce_webform/commerce_webform.module).

Warning: Invalid argument supplied for foreach() in commerce_webform_get_products_from_webform_submission() (line 285 of /path/to/mysite/sites/all/modules/commerce_webform/commerce_webform.module).

Notice: Undefined index: sid in commerce_webform_order_create() (line 166 of /path/to/mysite/sites/all/modules/commerce_webform/commerce_webform.rules.inc).

P.P.S. I'm cross-posting this update on 🐛 Webform data tokens appear to only work on first reaction Active

Hi,

Thank you very much for sharing your experience.

Sadly, I don't have any module related to webform, other than webform telephone, that haven't been updated since 2017. So there's no way this could be related.

Thanks anyway and glad you found a workaround in your case.