CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Bug #6052

Non-mandatory radio buttons export bug

Added by Bart Laarhoven over 3 years ago. Updated about 1 year ago.

Status:Resolved Start date:2010-01-16
Priority:Should have Due date:
Assignee:- % Done:

0%

Category:Backend Modul
Target version:Powermail 1.6.0
Votes: 0

Description

When exporting a form containing non-mandatory radio buttons, the export (csv or excel) contains a very annoying bug.

Reproduce:
- Create a form containing several fields, but at least one non-mandatory radio button field
- Fill in the form NOT SELECTING any of the radio buttons; send it
- Fill in the form selecting one of the radio buttons; send it
- Export
- Look at the csv or Excel file

You'll see that the export doesn't contain the specific radio button field for the entry where you didn't click anything. At all. And so, all other columns are moved to the left, which makes it impossible to use the data exported in a useful way. We have used Powermail for the subscriptions to an event, and it's very annoying to see that exporting over 300 subscriptions still doesn't give you an useful list of names and email addresses.
I'd say this should be fixed by explicitly adding ALL fields to the database after sending a form, and not just the filled in ones. I can't exactly find in which file this should be fixed, so I can't give an example bug fix right now. But I think it's an important bug to keep the export function a useful feature.

powermailDivideByForm.patch (9.8 kB) Lina Wolf, 2012-06-07 16:26

History

Updated by Benjamin Mack almost 3 years ago

Hey.

yes, very annoying. I don't like that at all, needs to be fixed as soon as possible, otherwise the current export is quite unusable.

Updated by Andy Grunwald over 2 years ago

  • Target version set to Powermail 1.5.6

Updated by Andy Grunwald over 2 years ago

This fix could only be for new mails.

But you are right.
All fields of the form must be inserted to database.

I will fix it.

Updated by Andy Grunwald over 2 years ago

  • Target version changed from Powermail 1.5.6 to Powermail 1.6.0

Sorry, we move this ticket to the next Powermail Version 1.6.0.

Updated by Alex Kellner over 2 years ago

  • Priority changed from Must have to Should have
  • Target version deleted (Powermail 1.6.0)

Updated by Alex Kellner over 2 years ago

  • Status changed from New to Resolved
  • Target version set to Powermail 1.6.0

Updated by Lina Wolf about 1 year ago

Problem prevails in powermail 1.6.4
This patch solves the problem for me, please note you have to aktivate ist via TSconfig

Also available in: Atom PDF