Encounter an error, or something which isn't working correctly? Please, let us know
spacefloh
Posts: 25
2567 Ratings
Your TCI: na
Joined: Sun Nov 04, 2007 6:33 pm
Post
by spacefloh » Fri May 11, 2018 7:52 am
Hi dear critickers,
i recognized that for my recent offline backup of the ranked movielist via:
Export Download this set of your rankings in a variety of formats XML - HTML - TXT - CSV
that wrong character did appear in the HTML and CSV files. (However, TXT and XML seem to be untouched.)
Special characters like "ä" seem to be exchanged by "ä". I hope that helps to fix the bug.
best regards and thank for your efforts,
spacefloh
mpowell
Posts: 3894
1201 Ratings
Your TCI: na
Joined: Fri Sep 09, 2005 10:22 am
Post
by mpowell » Fri May 11, 2018 3:32 pm
Thanks for reporting this! That's certainly incorrect... we'll look at this soon, and let you know when we have it solved.
mpowell
Posts: 3894
1201 Ratings
Your TCI: na
Joined: Fri Sep 09, 2005 10:22 am
Post
by mpowell » Wed Jun 13, 2018 7:52 am
I think this should be fixed up now, but please let us know if it's not. Sorry it's taken awhile to respond!
spacefloh
Posts: 25
2567 Ratings
Your TCI: na
Joined: Sun Nov 04, 2007 6:33 pm
Post
by spacefloh » Sat Nov 16, 2019 5:56 pm
Hi mpowell and team,
thanks, seems to be fixed for my personal reviews now.
However, for the download of
https://www.criticker.com/resource/rati ... ?type=html the display of gerneral summary
(i.e. on movie
https://www.criticker.com/film/Cruel-Intentions/ ) has still some errors (i.e. the character $'$ ). Same for xml, txt and csv files.
Code: Select all
Set in modern-day Manhattan, this is an adaptation of "Les Liaisons Dangereuses," the classic and scandalous Pierre Laclos novel of sexual manipulation and romantic war games first published in 1782. (Columbia TriStar)
Are you able to replicate that, or is it my personal browser error?
regards,
spacefloh
mpowell
Posts: 3894
1201 Ratings
Your TCI: na
Joined: Fri Sep 09, 2005 10:22 am
Post
by mpowell » Mon Nov 18, 2019 10:28 am
Thanks for letting us know! We'll take a look, and update here once we've had a chance to fix that up