Personal Video Database

I have just read it. My sincere condolences. I wish you a lot of strength in this difficult time.

You should be able to add custom fields with this code...

{#ConditionAddFirst <> '' '{#ConditionAdd <> '' '{%value=XYZ custom="true"}' '</p>'}' '
  <h2>XYZ</h2><p>'}
Put your custom field's name instead of XYZ (case sensitive, I think, but I'm not sure).
Feel free to play around with my template.

Kind regards,
svenne

Hi!
I only had the IDs implemented to keep references/links vivid (those links that can be generated within PVD in description or other fields and set to point to other movies in the list: right mouse-click on the part of the text you want to become a link and choose "Create Hyperlink").
The exported IDs are hidden via CSS.

If you want to see them edit
\HTML Frames\main.css
Search für pvdid (it only occurs once in line 158)
delete #list ul li a span.pvdid, within that line.

To put the ID in front of the title edit
HTML Frames (English).ptm
Find the long line starting with %HEAD% (should be line 51).
Find <span class="pvdid"> (ID: {%value=num})</span> and put that in front of <span class="mtitle"> within the same line. It should read now
...target="movie"><span class="pvdid"> (ID: {%value=num})</span><span class="mtitle">{%value=title}...
Feel free to change the ID portion as you like, perhaps
<span class="pvdid">No {%value=num} - </span>
or
<span class="pvdid">{%value=num}. </span>

Count the characters in front of {%value=num}. Originally there were 6 (including spaces: " (ID: "). To keep references/links working, edit
\HTML Frames\frame.js
and change line 68:
if (sl[i].firstChild && sl[i].className == "pvdid" && sl[i].firstChild.data.substring(6,(6+sx.length))==sx)As you see there is number 6 twice. Correct both. If you don't have any characters in front of {%value=num}, than it should be 0 here, of course:
if (sl[i].firstChild && sl[i].className == "pvdid" && sl[i].firstChild.data.substring(0,(0+sx.length))==sx)
Don't add {%value=num} to <h1 id="mtitle">...</h1> in file
\HTML Frames\movieiframe.ptm
It would break the javascript search function and certain filters.
You might add <h2 id="pvdid">{%value=num}</h2> to that line so it looks like...
  <h2 id="pvdid">{%value=num}</h2><h1 id="mtitle">{%value=title}</h1>{#StringReplace '{#ConditionAddFirst <> '' '{#ConditionAdd <> '' '{%value=origtitle}' '</p>'}' '
  <h2>Original Title</h2><p id="otitle">'}' '
  <h2>Original Title</h2><p id="otitle">{%value=title}</p>' ''}
Add the following code to \HTML Frames\frame.css and the ID will be inline and formatted the right way:
#pvdid
{
  float:left;
  padding-right:0.5em;
  margin:0px 0px 0.4em 0px;
  padding:0px 0.5em 0px 0px;
  font-size:1em;
}
#pvdid:after
{content:"";}

I think I will add this to the original scripts, too.

Apart from the error message... did you ever try one of Ivek's scripts to fix some of the broken imdb plugin features?
http://www.videodb.info/forum_en/index.php/topic,3282.0.html
I was very happy about his "Imdb Movie(cast) script". You can combine this with the imdb plug-in in a batch file. The batch file (a sample batch file is attached) should be copied to the plugins folder, the script to the script folder. You can try other scripts and modify the batch accordingly (with notepad or another text editor).
The newest (beta) version of the cast script (Ivek wrote, the original one would have some minor error) can be found here:
http://www.videodb.info/forum_en/index.php/topic,3991.msg19066.html#msg19066

Some PVD threads seem to crash. Whatever, after looking through this bug report it doesn't really help me, either. It just shows your system environment, PVD threads, and other programs running on your computer while the program crashs occured. It might help nostra, of course, who is the author of PVD. But for the time being you might want to delete it from your post. It doesn't show passwords or something but gives away a lot of information about your computer.

I'm not really sure what happens and how to solve this.

I would download the portable version of PVD (just put it in some folder on your desktop for testing purposes) and try to add a movie to a fresh database (without the old plugins and scripts installed). At first, try to add a movie "by hand", not by importing anything. Then try to add one from file or internet. Then try it on an imported database of yours. Then try it with old plugins and scripts added to the scripts/plugins directories. And so on. Just to narrow down the cause of the problem.

Another idea would be to backup and then optimize your imported database. You will find these functions in the "Administraton" or "Tools" submenu (after clicking the "Personal Video Database" button). For optimizing the database I would at least choose to delete all invisible movie and person orphans and also choose the garbage collection (you can check these options in the "Optimize database..." menu). Doing that should have the database rebuild. That might give a cure if there was something strange hidden in your database structure.

Since it was asked by rick some time ago...
http://www.videodb.info/forum_en/index.php/topic,2328.msg12254.html#msg12254

Dolphin browser (which became more or less the standard browser for android) now can handle iframes. So the HTML frames template works fine with that, now.

Hi!
First of all I would copy the files MOVIES.PVD and movies.pvd.bak to some safe place (and all other .pvd files that might be there). Did you try to open Movies.pvd (via fileopen menu in PVD)? Or is it already the active database? Did you check if you have reading/writing permissions to the .bak file? (If you can copy it you may ignore this question, I guess...). Does PVD have reading/writing permissions to these files? Are the files readable at all? Maybe your hard drive has an erratic sector or something.
If nothing helps, create a new database with a different filename, add a movie entry (just to see if that works). You could try to reopen your real database later. And if you copied all files with the ending .pvd to some backup folder nothing can get lost or messed up (that is not already messed up...).
I don't know if your database problems have anything to do with the black pane. I had some display problems when viewing PVD in full screen (while my database was fine). Try if switching to windowed view and resizing the PVD window makes a difference (also shut it down in windowed mode and restart it).
Try to reinstall a freshly downloaded PVD. Make sure that it doesn't default to your potentially corrupted database (move the file to some other place before reinstalling into an empty folder). If the left pane is fine then your databse file is the problem. But if it is still black, something else is causing the problem.
This is just a bunch of ideas, of course. Maybe someone else can help with better ones...

- added: search function
- bug fix: two coding issues handicapped speculative parsing by the browser

The search function does a full text search. It crawls through each and every movie page in the list (but only through visible entries), which means it is quite slow. Especially when running online (in that case it might take about 30 seconds for 100 movies). Do you like it nevertheless? What do you think? Should I take it out again or keep it?
I added a cache for this function. So if you search a second time (and it doesn't matter if it's for a different search phrase, of course) it will be a lot faster... The cache will persist unless you do a full reload in your browser.

Some kind of major update... :-)

"HTML Frames" now supports...

- "IMDB Rating" and "Rating"
- "Connections"
- "Tags"

"Further options..." button now also provides sort by "IMDB Rating" or "Rating"

Additional features generated by "pimpHTMLframesExport" (after export this tiny executable can be found in subfolder "(filname)_files\pimpHTMLframesExport\") don't result in thousands of small HTML files anymore. Now, all the additional links act as filters (altering the movie list instead of linking to seperate pages). You can always get back to the full list by selecting "show all entries" (near the "Further options..." button)

Some minor bugs were fixed (and maybe some new ones generated... so let me know if you notice strange behaviour).

Have fun