Bug #338
URLdecode data from tmdb, such as description.
| Status: | Closed | Start date: | 30 May 2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Hammel | % Done: | 100% | |
| Category: | UI | |||
| Target version: | PiBox - 0.9.0 | |||
| Severity: | 03 - Medium |
Description
The description for Toy Story includes non-printing characters that can probably be removed by using urldecode on the data.
Associated revisions
RM #334, RM #336, RM #338: Add disclaimer and tmbd logo. Move code that fills details frame from video data to its own method so it can be called from multiple places. Move code that scans for a video to its own method so it can be called from multiple places. Add rebuildDB button. Add event handling for clicking on video name in the list. Add URL decoding.
Add disclaimer and tmbd logo.
Move code that fills details frame from video data to its own method so it can be called from
multiple places.
Move code that scans for a video to its own method so it can be called from multiple places.
Add rebuildDB button.
Add event handling for clicking on video name in the list.
RM #334, RM #336, RM #338: Add disclaimer and tmbd logo. Move code that fills details frame from video data to its own method so it can be called from multiple places. Move code that scans for a video to its own method so it can be called from multiple places. Add rebuildDB button. Add event handling for clicking on video name in the list. Add URL decoding.
Add disclaimer and tmbd logo.
Move code that fills details frame from video data to its own method so it can be called from
multiple places.
Move code that scans for a video to its own method so it can be called from multiple places.
Add rebuildDB button.
Add event handling for clicking on video name in the list.
History
#1
Updated by Hammel almost 4 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
This is implemented in the display though the database retains the URLencoding. This doesn't seem to clear some strange data returned from tmdb. But it's implemented so this issue can be closed. Whatever those strange characters are will have to be dealt with in a different issue (probably a UTF encoding problem).