Summary:
If you have a Webform configured to use Localization by string translation and have a markup component, refreshing the webform localization strings creates error messages in the watchdog.
Steps to reproduce:
On a clean install of D7.42:
drush -y dl webform_localization-7.x-4.x-dev i18n
drush en -y webform webform_localization
Add a new webform.
Add a markup field.
Go to form settings, tick " Expose webform component strings suitable for translation." under "Localization by string translation"
Go to admin/config/regional/translate/i18n_string
Check 'webform localization' and press Refresh Strings
Go to admin/reports/dblog
Actual Result:
Two errors are logged:
* WebformConditionals::componentMarkup called prior to evaluating a submission.
* Undefined index: page_num in _webform_display_markup() (line 156 of /Volumes/www/DevDesktopSites/d7419/drupal-7.42/sites/all/modules/webform/components/markup.inc).
Expected Result:
No errors should be in the watchdog.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2671042-02.patch | 1.4 KB | nicrodgers |
Comments
Comment #2
nicrodgersThis patch is based on the one in 2542796, but updated to work within _webform_display_component/_webform_display_markup.
Comment #3
nicrodgersSelected wrong status.
Comment #4
nicrodgersComment #5
danchadwick commentedThis don't seem like the right place to fix this. The root problem is the caching. I'm not sure how localization fits into this, but can't it handle this case?
Comment #6
RAWDESK commentedHi, just to confirm this patch also fixed the error from occurring on a drush fra in post deploy commands.
Our webform was featured with webform_feature module and gathered some additional translation settings during deploy :
Comment #7
giupenni commented#2 works for me
Comment #8
abaier commented#2 solved this problem for us too. Thanks!
Comment #9
liam morlandDrupal 7 is no longer supported. If this applies to a supported version, please re-open.