jacobwb / hashover-next

This branch will be HashOver 2.0
GNU Affero General Public License v3.0
420 stars 87 forks source link

Migrating comments from V1.0 to next version? #261

Open ominty opened 5 years ago

ominty commented 5 years ago

I did some tests of hashover-next last weekend and copied the old pages-folder to the new comments-folder and expected the old comments to show up. They don't. Is there anything to observe or do they have to be converted in some way?

ominty commented 3 years ago

Meanwhile I found that there seems to be an issue with the datetime format within the xml files.

Hashover tells me HashOver: DateTime::__construct(): Failed to parse time string (04/10/2017 - 7:35pm) at position 11 (-): Unexpected character

and this is the difference V1: <date>12/05/2016 - 12:15pm</date> V2: <date>02/18/2018T11:57+0100</date>

Anyone any idea how to fix this with masses of comments?

ominty commented 3 years ago

After fixing some of the xml by hand the error message has gone (which showed up in the admin panel as well as on the actual page of the post). I can see the posts in the admin panel now.

When I try to edit one of these "fixed comments" in the admin panel and save there is a red banner telling me Invalid Character Error

?