I only see 'Webform' here:
admin/config/regional/content-language

But I don't see Webform submissions..
I have all core multlingual modules installed.
I have the following webform modules installed:
Webform
Webform Bootstrap
Webform Node
Webform Scheduled Email Handler
Webform Templates
Webform UI
Webform views

Any idea?

Thanks

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Sarahphp1 created an issue. See original summary.

jrockowitz’s picture

I have no idea why submissions are not appearing... and contact message are appearing under Content languages (/admin/config/regional/content-language)

jrockowitz’s picture

Status: Active » Needs review
FileSize
538 bytes

Attached patch enables translating webform submissions. This is completely untested concept/feature. Setting to 'Needs review' to run the automated tests.

0Sarah0Al’s picture

Thank you so much.

The patch is working.

I got all my forms submission under 'Translation is not supported' (see pic) , but they are actually translated.

I remembered when I first installed this version of drupal 8, ( the one I am working on right now), I installed a module called rename_admin_paths first, then the rest of the other contrib modules including webform. Now, I suspecting that it has to do with all the problems I am encountering with webform and probably other modules.

I don't recommend that module at all..
I wish I could remove all traces of it in the database.

Thanks again for all your help.
Awesome module and awesome developer.

jrockowitz’s picture

The attached patch add translatable: TRUE to the WebformSubmission annotation, this removes 'Translation is not supported' but then causes everything to break.

Why would you need submissions to be translatable? and I am not sure I am able to support this.

Status: Needs review » Needs work

The last submitted patch, 5: webform_submissions_not-2910080-5.patch, failed testing. View results
- codesniffer_fixes.patch Interdiff of automated coding standards fixes only.

0Sarah0Al’s picture

Hi Jackob

Let me explain.

I have two drupal installations. one is for test and the other is my actual website I am building right now.

My actual website is bi-lingual (English, arabic). And there is webform that collects customer information, name, age, gender, phone and location.

I created a views (page) that lists submission information to the user with an 'edit' button so that they can go back to the webform (same webform 'customer information' webform) and edit thier information. (see first image, This is the english version just to show you the view)
(I hope this is the correct way to do it, by the way)

When I am viewing this views page in Arabic, then hit the 'edit' button, I am reverted to the English version of the webform.

I checked my test website and I saw this (see second image).
You see in the image the check boxes are unchecked but they actually checked.. I had to uncheck them in order to collapse the lines in order to show you that I have webform and webform submissions showing under 'content language' in admin/config/regional/content-language in the test website.

Now, in my other website, i only see webform but no 'webform submission'.
When I applied the first patch you provided above, I was able to view my "customer information" in Arabic when I hit the 'edit' button. So, the first patch fixed the issue.

I could be doing something wrong that led to the issue of the language, I don't know. your advice is apprecited!

I actually don't know if I need to apply the second patch because the first one was all I needed to get the 'edit' button problem fixed (that is take me to the correct language version).

jrockowitz’s picture

@Sarahphp1 Thanks for the explanation.

For now, I think we just need to apply the patch from #3.

I also confirmed that the new langcode entity_key does not require that a new index to be added to the 'webform_submission' table.

  • jrockowitz committed 277a4b5 on 8.x-5.x
    Issue #2910080 by jrockowitz, Sarahphp1: Webform submissions not in '...
jrockowitz’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.