Description

After following all the migration steps (as in MauricioHernandez/HowToSurviveMigration), my Moin seems OK. But when I try to access one particular page I got the following error message:

UnicodeDecodeError'utf8' codec can't decode bytes in position 11-14: invalid data

At the end of the error report it says:

UnicodeDecodeError: 'utf8' codec can't decode bytes in position 11-14: invalid data
      __doc__ = 'Unicode decoding error.'
      __getitem__ = <bound method UnicodeDecodeError.__getitem__ of <exceptions.UnicodeDecodeError instance>>
      __init__ = <bound method UnicodeDecodeError.__init__ of <exceptions.UnicodeDecodeError instance>>
      __module__ = 'exceptions'
      __str__ = <bound method UnicodeDecodeError.__str__ of <exceptions.UnicodeDecodeError instance>>
      args = ('utf8', 'Visualizaci\xf3nEnOpenWare.html', 11, 15, 'invalid data')
      encoding = 'utf8'
      end = 15
      object = 'Visualizaci\xf3nEnOpenWare.html'
      reason = 'invalid data'
      start = 11

That page was the only onw with an attachment with accented chars in the name that was linked from the text of the page.

Steps to reproduce

1. Given any Moin 1.2.x (pre 1.3)
2. Upload any file with accented chars in their name ("migración.html", as an example).
3. Create a link from the page to it's attachment (this probably is not required, but this is how it happened to me).

4. Do the Moin 1.3 installation and data migration like explained in MauricioHernandez/HowToSurviveMigration (thanks Mauricio!).

5. Try to go to the page with the attachment reference and you'll see the errors reported above.

Details

Workaround

• Reupload the files.

• Convert them using the script found on this page: DavidLinke/FixingAttachmentNamesAfterMigration

Discussion

This change in the attachment name (and their corresponding links if they exists) should be included in the migration scripts.

Plan

• Priority: high

• Assigned to: ThomasWaldmann

• Status: fixed in patch-641/642 (mig10 script)

CategoryMoinMoinBugFixed