Personal Video Database

Hi

Try deleting [RIPPER,] and  ['{%value=Ripper custom="true"}',] in the pk_sql.ptm file.
RIPPER is a custom field in my database.

Hi,

About you first post, I'm unsure whether you think I'm the original author of the PK template - I'm not. Just this modified version and one earlier version for AMC (of course you could be referring to the latter as the one you've been using).

1) I've never had to deal with asian characters, but I have no trouble with special characters from e.g. Turkish or Icelandic. Just make sure the exported sql file is saved as unicode, and that the database is also unicode.
Or are you referring to text in the template itself, like headers?

2) I've only recently noticed this as a problem, I don't think it used to be like that. Maybe something changed at imdb lately? It is certainly annoying, and I will try to dig up the fix from the AMC thread.

3) I currently use only one custom field, "Ripper". Refers to the ripper tag of course. All the fields actually used by the template are listed in the "Fields.sql" file in one of the zip files.


About the people pages suggestion, would that be something similar to people view in pvd?
I should say that I actually suck at php coding too. I'm not alienated by it though so I can usually make minor changes or fixes. Not sure I will be able to code new functionality from scratch though.

Can't import more than 9 imdb records at at time without a "http bad request" error. Is anyone else having this problem? Is it the website blocking batch requests or is something wrong with the plugin? Using version 0.9.9.10

Since we have a release now I have some updated files. Also made some changes, like bigger posters.
Link to my site based on these files is in my sig.


Needed files:
http://www.mediafire.com/file/mdmzyztym4n/pkdb for 0.9.9.8 - website files.zip
http://www.mediafire.com/file/z2dmwgmmhjg/templates -  sql scripts.zip

The files are just proof of concept and will have to be adapted for other databases. Ask me if you decide to try.


EDIT: Updated first post with a step-by-step description and the new files

I can't see any pattern, and maybe it doesn't even have to do with ratings. I was guessing as much because the rating field is not updated for those entries which show this error.

Hi,
you'll need an updated export template for the beta version, since there are many changes.
I have one working already for my own site, I'll try to tidy it up and upload it tomorrow.

Hi,
The sql query does not appear to close each statement properly - each line of the query should close with [);] whereas yours close with [,'] . This will cause malfunction. Maybe you could post the sql export script you're using?

Hi,
The template available for download (on page 2 of this thread) is up to date except for tags and allmovie rating/link. Unless these are very important to you I'd rather wait until I can make a working template for 0.9.9.X before uploading more files (the sql export template works for version 0.9.8.20 only).

Seems you already figured out how to enable/disable the side panels in mdb_confic.inc. The files that contain the html code reside in the templates/default folder. 
detail_view.tpl is the main view and details.tpl is the detailed view. If you know a little html you shouldn't have any problems with these. Not sure if they will open in a wysiwyg editor though.

The colors are all defined in the stylesheet style.css with the single exception of the main background color which is defined in index.php. I think the easiest way to edit the colors is to make a screencap of the web page and open it uncompressed in photoshop or similar software. Using the eydropper tool you can identify the various colors in the stylesheet, this is easier than trying to interpret the various pointers in the stylesheet directly. Then just tweak colors as you wish using replace color in photoshop, identify the new color value and search-replace those values in the stylesheet.
There are some gif files in templates/default/images which naturally aren't tweaked using the stylesheet, you will need to edit these manually. The logo also resides here, I suspect you don't want to keep my walking egg.

The problem is your database entries aren't numbered. The ID number (the first value) is assigned as the "primary key" in the database, which probably means it has to be unique. I wasn't even aware that PVD would allow duplicate IDs.
Fortunately the internal PVD database has an internal ID you can use as a replacement value. Make the change shown with red to the sql.ptm file before exporting, this should assign the internal ID number instead:

%OPTIONS%
filter="SQL Files|*.sql"
encoding="UTF8"
replace=";<->,"
replace="'<->''"
replace=""<->"
replace="#13#10<-> "
replace="#13<-> "
replace="#10<-> "
imagepath="images\"
%OPTIONS%INSERT INTO movies (NUM, CHECKED, MEDIA, MEDIATYPE, SOURCE, DATEADD, BORROWER, RATING, ORIGINALTITLE, TRANSLATEDTITLE, FORMATTEDTITLE, DIRECTOR, PRODUCER, COUNTRY, CATEGORY, YEAR, LENGTH, ACTORS, URL, DESCRIPTION, COMMENTS, VIDEOFORMAT, VIDEOBITRATE, AUDIOFORMAT, AUDIOBITRATE, RESOLUTION, FRAMERATE, LANGUAGES, SUBTITLES, FILESIZE, DISKS, VIEWDATE, PICTURENAME) VALUES ('{%value=0}', '', '{%value=47}', '', '', '{%value=17}', '', '{%value=9}', '{%value=3}', '{%value=2}', '', '{%value=53}', '{%value=56}', '{%value=45}', '{%value=44}', '{%value=5}', '{%value=19}', '{%value=52}', '{%value=8}', '{%value=15}', '{%value=16}', '{%value=23}', '{%value=24}', '{%value=43}', '{%value=25}', '{%value=21}', '{%value=22}', '{%value=48}', '{%value=49}', '{%value=26}', '{%value=29}', '{%value=33}', '{%value=63}');

I suspect the date values formatted like "21st July 1979" will end up as "0000-00-00" in the mysql database. It should be possible to fix this using regular expressions, let me know if it becomes a problem.

EDIT: forget the last part, seems the alternative date formatting I spotted is part of a descripton text and not a date field.