VideoDB

After updating my web server computer software to Ubuntu 16.04 (which includes PHP 7 and updating VideoDB software to the latest available with some PHP 7 fixes I noticed the Borrow feature fails. The Error I get is: Database Problem ... [More] Expression #4 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'videodb.videodata.subtitle' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by SELECT who, DATE_FORMAT(dt,'%d.%m.%Y') as dt, lent.diskid, CASE WHEN subtitle = '' THEN title ELSE CONCAT(title,' - ',subtitle) END AS title, videodata.id, COUNT(lent.diskid) AS count, users.name AS owner FROM lent, videodata LEFT JOIN users ON owner_id = users.id WHERE lent.diskid = videodata.diskid GROUP BY lent.diskid ORDER BY who, lent.diskid I presume this is another issue with compatibility with PHP 7. Has anyone come up with a fix for this? I would appreciate a fix for this because we do use that feature. Thanks ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z_______________________________________________ videodb-devel mailing list videodb-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org https://lists.sourceforge.net/lists/listinfo/videodb-devel [Less]

I have one entry in my VideoDB (version v4.0.0) that on the Browse and View (Edit) pages shows the wrong Cover image. Clicking the magnifier glass icon on the View page for the cover image opens the expanded view and shows the correct image. I ... [More] tried clearing browser cache, updating the movie entry and everything (except deleting the entry and adding a new entry for this video) I could think of, but the image shown remains the wrong cover art. Viewing the file in the Cover URL field for the affected video entry (cache/img/1024.jpg) it is the correct image. Why would the Browse and View pages show the wrong image for this video entry? But more importantly how can I get the correct image to show on those pages? Thanks, Jim ------------------------------------------------------------------------------ [Less]

Just a note for some future change to videodb - This is not very important. Not a bug, but an improvement. It appears the removeArticles() function in videodb/core/core.php is not sensitive to language settings. It would be nice if it used an ... [More] array that only included articles appropriate for the user's selected language. I am using v4.0.0. While cleaning up my video collection my "Die Hard" movies Titles got changed due to "die " being treated as an article. So I went searching and discovered the $articles array is not sensitive to the language in use. Of course I could edit my local copy for the only language I will ever use, but I suggest a more permanent solution be included in videodb. So, please add this to the list of things to do in future updates. Thanks, Jim ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ [Less]

You should not need more than a web server (e.g. Apache) and MySql or MariaDB as database. Cheers, Andreas ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go ... [More] Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ [Less]

I currently run videodb on a desktop with LAMP stack but would like to move it to a Network Attached Storage (NAS) device which also seems to have a LAMP stack working. Has anyone done that? Many PHP MySQL applications are available to be ... [More] installed on the NAS (see http://apps.readynas.com/pages/ for info). I have no clue what would be required to get videodb to run on the NAS, but suspect it should only require configuration and installation being compatible with the NAS hosted software. Any ideas, suggestions? Thanks! ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ [Less]

Jim, I haven't looked at the VideoDB code in quite some time, but here are a few answers. You can keep the column type the same and simply extend the length of the varchar column from 255 characters all the way up to 65535. The only way I can ... [More] see this introducing problems in future releases (if there are any) is if the "official" column length for the comment field is extended beyond 255 characters to something less than the maximum number of characters you have entered for a single comment. Also, a quick look at the code indicates that the imdbID field (e.g. the "External ID" field) will assume it's an IMDB ID if it cannot detect another prefix. So no prefix or "imdb:" prefix means it's an IMDB ID. I don't think anything should have a tt prefix in the database. I've never looked at the PDF code much, but I see this in ./core/pdf.php on line 328 $result = iconv_array('utf-8', 'iso-8859-1', exportData($WHERE)); This call tries to convert the data for a particular movie from UTF-8 into ISO-8859-1. If the conversion fails for any reason, it display that message. Off the top of my head, I'd say a particular movie has either corrupt UTF-8 characters (I would hope it's not possible to get that data into the DB) or a UTF-8 character that cannot be represented in the ISO-8859-1 encoding. I'm also not entirely sure why the conversion is necessary (I assume PDF files support UTF-8 just fine). As a shot-in-the-dark workaround, you could try changing the line to this to effectively disable the conversion. $result = iconv_array('utf-8', 'utf-8', exportData($WHERE)); Justin Pasher On 11/6/2014 8:44 PM, Jim Irving wrote: ------------------------------------------------------------------------------ [Less]

Thanks Anthony, I was considering modifying the database field definition like you suggest, and may try that. A problem is that having a custom field definition would present problems with compatibility with subsequent updates from VideoDB. I ... [More] don't think I want to diverge from the official source. I appreciate your suggestion and might try this. Thanks again, Jim On 11/06/2014 07:12 PM, Anthony Baker wrote: ------------------------------------------------------------------------------ _______________________________________________ videodb-devel mailing list videodb-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org https://lists.sourceforge.net/lists/listinfo/videodb-devel [Less]

I think I can answer question #1. Numbers 2 and 3 are probably best left to someone with more knowledge of the software than myself. **MAKE SURE YOU BACKUP YOUR SITE BEFORE MAKING ANY DATABASE CHANGES!!!** I'm giving the instructions for how I just ... [More] enlarged the comment field on my test server using phpMyAdmin 4.2, although it should be similar using other programs/versions. Open up the videodb_videodata table, and click on the "Structure" tab at the top. Find the "comment" field, and click on the "Change" link on the same line. Change "VARCHAR" to "MEDIUMTEXT" and click save. You should be able to store larger comments now. Note that this does not change the size of the comment box on the edit screen, only the size of the data that can be stored. I'm not very familiar with the particulars of the VideoDB source code, so it's possible that this solution may cause issues somewhere else, but I after doing this I switched to the modern/elegant template that you mentioned and was able to edit/view a longer comment with no issues. - Anthony Date: Thu, 6 Nov 2014 16:00:22 -0700 From: jirv898-uAjRD0nVeow< at >public.gmane.org To: videodb-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org Subject: [videodb-devel] V4.0.0 Questions I downloaded v4.0.0 from GitHub site and updated my old VideoDB installation. VideoDB seems to be working fine but I have some questions. 1. Can the size of the Comment field be increased? Probably an enhancement for later, but I would like the field to permit a longer comment. 2. Some of my entries have the External Id field set to include the IMDB ID with the leading "tt" characters and some do not and it seems that field now includes "imdb:" as a prefix for the IMDB ID in some of my newer entries. What should that field contain (I am in the USA if that matters)? Should include the imdb: prefix with just the seven digit number (no "tt") or does it matter to the logic? Just curious. 3. My PDF Export button; bottom of elegant (modern) template, gives an error message: Character set conversion error Error converting from utf-8 to iso-8859-1. Is that error due to some setting I can control or is this a bug in VideoDB? If that is due to some setting I have control over where & how do I correct that. I remember converting my videodb database to utf-8 a few years back. It might be good if someone added some instructions for using the GitHub website. I notice there is another Release (4.1) but the 4.0 is the one in the Download on the GitHub page. Should I have gotten version 4.1 instead of 4.0? Thanks for this wonderful application and continued support. Jim ------------------------------------------------------------------------------ _______________________________________________ videodb-devel mailing list videodb-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org https://lists.sourceforge.net/lists/listinfo/videodb-devel ------------------------------------------------------------------------------ _______________________________________________ videodb-devel mailing list videodb-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org https://lists.sourceforge.net/lists/listinfo/videodb-devel [Less]

I downloaded v4.0.0 from GitHub site and updated my old VideoDB installation. VideoDB seems to be working fine but I have some questions. 1. Can the size of the Comment field be increased? Probably an enhancement for later, but I would like the ... [More] field to permit a longer comment. 2. Some of my entries have the External Id field set to include the IMDB ID with the leading "tt" characters and some do not and it seems that field now includes "imdb:" as a prefix for the IMDB ID in some of my newer entries. What should that field contain (I am in the USA if that matters)? Should include the imdb: prefix with just the seven digit number (no "tt") or does it matter to the logic? Just curious. 3. My PDF Export button; bottom of elegant (modern) template, gives an error message: Character set conversion error Error converting from utf-8 to iso-8859-1. Is that error due to some setting I can control or is this a bug in VideoDB? If that is due to some setting I have control over where & how do I correct that. I remember converting my videodb database to utf-8 a few years back. It might be good if someone added some instructions for using the GitHub website. I notice there is another Release (4.1) but the 4.0 is the one in the Download on the GitHub page. Should I have gotten version 4.1 instead of 4.0? Thanks for this wonderful application and continued support. Jim ------------------------------------------------------------------------------ _______________________________________________ videodb-devel mailing list videodb-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f< at >public.gmane.org https://lists.sourceforge.net/lists/listinfo/videodb-devel [Less]

Jim, I haven't looked at the VideoDB code in quite some time, but here are a few answers. You can keep the column type the same and simply extend the length of the varchar column from 255 characters all the way up to 65535. The only way I can ... [More] see this introducing problems in future releases (if there are any) is if the "official" column length for the comment field is extended beyond 255 characters to something less than the maximum number of characters you have entered for a single comment. Also, a quick look at the code indicates that the imdbID field (e.g. the "External ID" field) will assume it's an IMDB ID if it cannot detect another prefix. So no prefix or "imdb:" prefix means it's an IMDB ID. I don't think anything should have a tt prefix in the database. I've never looked at the PDF code much, but I see this in ./core/pdf.php on line 328 $result = iconv_array('utf-8', 'iso-8859-1', exportData($WHERE)); This call tries to convert the data for a particular movie from UTF-8 into ISO-8859-1. If the conversion fails for any reason, it display that message. Off the top of my head, I'd say a particular movie has either corrupt UTF-8 characters (I would hope it's not possible to get that data into the DB) or a UTF-8 character that cannot be represented in the ISO-8859-1 encoding. I'm also not entirely sure why the conversion is necessary (I assume PDF files support UTF-8 just fine). As a shot-in-the-dark workaround, you could try changing the line to this to effectively disable the conversion. $result = iconv_array('utf-8', 'utf-8', exportData($WHERE)); Justin Pasher On 11/6/2014 8:44 PM, Jim Irving wrote: ------------------------------------------------------------------------------ [Less]