Feature #6479
Export to .ini file
| Status: | Rejected | Start date: | 2010-02-16 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 2.0.0 | |||
| Votes: | 0 |
Description
Hi,
One of our clients would like to see the possibility in Powermail to export to an .ini file format. So that would look like:
[id429] <fieldname>=... <fieldname>=... ... [id435] <fieldname>=... <fieldname>=... ...
Of course one could argue that this is pretty easy if you'd transform the .csv file into this using an external PHP script, but I guess it would be a nicer solution to add it to Powermail by default. If anyone else is interested in this too.
Thanks!
Associated revisions
Fixed bug #6479: wrong field names for localization
History
Updated by Bart Laarhoven over 3 years ago
By the way, a big advantage of this method is that it doesn't matter whether fields are added or removed while the form is online. When that happens, the .csv-file gets incorrect (for half of the .csv file, the columns shift aside) and in this .ini format, that doesn't matter.
On the other hand, a correct .csv file (including the dynamic titles) would do the trick too.
Updated by Ingo Renner over 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset r13808.
Updated by Alex Kellner over 2 years ago
- Target version set to Waiting for Sponsoring
Updated by Alex Kellner about 1 year ago
- Target version changed from Waiting for Sponsoring to 2.0.0
Updated by Alex Kellner about 1 year ago
- Status changed from New to Rejected