View Issue Details

IDProjectCategoryView StatusLast Update
0000611OXID eShop (all versions)2. ----- eShop backend (admin) -----public2012-12-10 14:22
Reportermkr Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionunable to reproduce 
Summary0000611: Error on showing User List after generic import
DescriptionAfter import of 2496 Usrs over the Generic Import tool, the 'Benutzer Verwalten' --> Liste section failed.
Following screen is instead popup for downloading the index.php, see Attachment.
After deleting the added users from the oxuser table, the problem disappears.

Normally i expected 2500 Users to import, but only get 2496.
I try also a generic export to determine the CSV Format, but it does not fit the import format (' as enclosed char e.g.).
Additional Informationupload_max_filesize = 64M is set in the php.ini
Following Charset was used: Windows-1252, ISO-8859-1 and UTF-8
TagsExport, Import
Attached Files
Theme
BrowserAll
PHP Version5.2.6
Database Version5.0.33

Relationships

related to 0000624 resolvedrimvydas_paskevicius Display more information about Import formats and process 

Activities

dainius.bigelis

2009-02-23 15:24

reporter   ~0000462

More Information at the import action will be more useful to detect errors.
More information of the CSV format are recommend. The online help does not fit this.
==> entered as separate bug entries.

mkr

2009-02-23 18:57

reporter   ~0000467

I will try to generate a csv file with obfuscated user details, that produce the same error. I will try to deliver the file this week...

mkr

2009-02-24 11:09

reporter   ~0000472

Obfuscated import file added. Import of all users now successfully, but popup screen in 'Benutzer Verwalten' --> Liste section appears again.

rimvydas_paskevicius

2009-02-26 12:52

reporter   ~0000492

We tried to import all users from given csv file and no errors occured. All 2500 users were successfully imported and no popup screen apiers in 'Benutzer Verwalten' --> Liste - it shows all users list. So we were unable to reproduce this bug.