Completely unsure about the implementation of .plexignore and how it would affect search of a locked directory.
Completely unsure about the implementation of .plexignore and how it would affect search of a locked directory.
I'm pretty sure that using plexignore to "ignore" files in the private section would prevent them from being scanned and added to the library in the first place.
Completely unsure about the implementation of .plexignore and how it would affect search of a locked directory.
Doesn't affect search, only media scanning
Search is not filebased, but database related, and apparently targeted on the MetaData_Items table, so the only way to hide a movie from search, would be to move it to another table, which IMHO is not an option
/T
I agree. Moving an entire section's worth of entries into another table (and back again) seems ill-advised and likely not very quick.
Doesn't affect search, only media scanning
Search is not filebased, but database related, and apparently targeted on the MetaData_Items table, so the only way to hide a movie from search, would be to move it to another table, which IMHO is not an option
/T
Yeah, it is not file based. Was looking for a equivalent to stop the db from getting searched. Still unclear if search is directly of the db or some jquery/xml of the PMS cache.
I agree. Moving an entire section's worth of entries into another table (and back again) seems ill-advised and likely not very quick.
Yup, that would not be the best way, for sure. Not only would the data need to be moved to another table but also a refresh of the scanner so as to not break anything. Then there is the PMS cache.
A dirty fix to keep the movies/videos from showing up in search.
A lil explanation for dev’s who may be interested as to how I went abou trying. The real task was to change something trivial without crippling the functioning/system of PMS. Ok, so I noticed that the results of the search required a specific media_type container for xml to display results. Refered to as metadata_type in the metadata_items table.
First, to test, changed the metadata_type of a movie in the section I have locked from 1(movie type) to 8(music artist) forcing it to be displayed in the search result as a music artist container that could not be played. Once I confirmed that the search result required a metadata_type int value that corresponded to the media type. I just changed the metadata_type in the metadata_items table to 20(undefined). Now none of the videos in the locked section show up in search. Would appreciate it if others can test!
I don’t know how you will be able to manage this in your highly evolved code Mike, the one where your letting multiple section types to be locked, will be awesome though, each section will have their own queries, I guess.
Anyway, will update code on github with new queries for the .command in a bit to have a more consolidated query for metadata_items table after some more testing. For now just to share:
The below will be an addition to the lock.command
update metadata_items set metadata_type=20 where library_section_id=;
The below will be an addition to the unlock.command
update metadata_items set metadata_type=1 where library_section_id=;
Guess the show will go on... :D
A dirty fix to keep the movies/videos from showing up in search.
A lil explanation for dev’s who may be interested as to how I went abou trying. The real task was to change something trivial without crippling the functioning/system of PMS. Ok, so I noticed that the results of the search required a specific media_type container for xml to display results. Refered to as metadata_type in the metadata_items table.
First, to test, changed the metadata_type of a movie in the section I have locked from 1(movie type) to 8(music artist) forcing it to be displayed in the search result as a music artist container that could not be played. Once I confirmed that the search result required a metadata_type int value that corresponded to the media type. I just changed the metadata_type in the metadata_items table to 20(undefined). Now none of the videos in the locked section show up in search. Would appreciate it if others can test!
I don’t know how you will be able to manage this in your highly evolved code Mike, the one where your letting multiple section types to be locked, will be awesome though, each section will have their own queries, I guess.
Anyway, will update code on github with new queries for the .command in a bit to have a more consolidated query for metadata_items table after some more testing. For now just to share:
The below will be an addition to the lock.command
update metadata_items set metadata_type=20 where library_section_id=;The below will be an addition to the unlock.command
update metadata_items set metadata_type=1 where library_section_id=;Guess the show will go on... :D
Not sure here....What happens if you select search from the Homeview? Aka. no section selected
/T
Not sure here....What happens if you select search from the Homeview? Aka. no section selected
/T
Does not show up for me on PlexWeb!(Not from within any section) Unsure what exactly you mean, I presume the section wouldn't be there since it's locked, Appreciate your testing though!
Look forward to a way where the internal sqlite3.so of PMS can be used by the channel :)
Does not show up for me on PlexWeb!(Not from within any section) Unsure what exactly you mean, I presume the section wouldn't be there since it's locked, Appreciate your testing though!
Look forward to a way where the internal sqlite3.so of PMS can be used by the channel :)
Okay, and that is indeed cool.
Still I do see on issue though.....
I like lots of other people, have huge sections.....
Like my movie section contains of +1000 items, and my main TV section is +5000 items
When having to walk and update every item within such a section could be kinda time consuming!
But anyway......
I'll make the sections avail on my test PMS, currently only holds 5 sections with 5 items in each, so I can do some time testing here as well
/T
A dirty fix to keep the movies/videos from showing up in search.
A lil explanation for dev’s who may be interested as to how I went abou trying. The real task was to change something trivial without crippling the functioning/system of PMS. Ok, so I noticed that the results of the search required a specific media_type container for xml to display results. Refered to as metadata_type in the metadata_items table.
First, to test, changed the metadata_type of a movie in the section I have locked from 1(movie type) to 8(music artist) forcing it to be displayed in the search result as a music artist container that could not be played. Once I confirmed that the search result required a metadata_type int value that corresponded to the media type. I just changed the metadata_type in the metadata_items table to 20(undefined). Now none of the videos in the locked section show up in search. Would appreciate it if others can test!
I don’t know how you will be able to manage this in your highly evolved code Mike, the one where your letting multiple section types to be locked, will be awesome though, each section will have their own queries, I guess.
Anyway, will update code on github with new queries for the .command in a bit to have a more consolidated query for metadata_items table after some more testing. For now just to share:
The below will be an addition to the lock.command
update metadata_items set metadata_type=20 where library_section_id=;The below will be an addition to the unlock.command
update metadata_items set metadata_type=1 where library_section_id=;Guess the show will go on... :D
Nice detective work. I don't think it'll take much to tweak the code for this addition. I'll try to get it updated for testing within the next couple days.
The below will be an addition to the lock.command
update metadata_items set metadata_type=20 where library_section_id=;The below will be an addition to the unlock.command
update metadata_items set metadata_type=1 where library_section_id=;
Is there a (graceful) way to combine the "UPDATE metadata_items" commands with the ones already being used? My thought is that adding the extra command in sequence rather than parallel means that we're essentially traversing the database twice when locking or unlocking. For large sections that may make a noticeable difference. Or do I not have the concept quite right?
Nice detective work. I don't think it'll take much to tweak the code for this addition. I'll try to get it updated for testing within the next couple days.
Can I humbly suggest, that instead of setting the metadata type to 20, then instead add 666 to it.
That way, when unlocking, you substract 666 and get the origen type, thus making it universal for both movies, TV-Shows, and all other currently defined types.
/T
Can I humbly suggest, that instead of setting the metadata type to 20, then instead add 666 to it.
That way, when unlocking, you substract 666 and get the origen type, thus making it universal for both movies, TV-Shows, and all other currently defined types.
/T
You really like the mark of the beast :P
We can set it to any undefined type we like. I'm not partial. Since the type id for each section is stored with the rest of the details in the Dict, we don't need to execute any math to get back to the original type, just assign it from storage.
Is there a (graceful) way to combine the "UPDATE metadata_items" commands with the ones already being used? My thought is that adding the extra command in sequence rather than parallel means that we're essentially traversing the database twice when locking or unlocking. For large sections that may make a noticeable difference. Or do I not have the concept quite right?
After doing a little more sqlite reading, I think I have a grasp on the way to combine the statements for efficiency.
LOCK_COMMAND_1 = "UPDATE metadata_items SET added_at=?, metadata_type=20 WHERE library_section_id=?;" # section['section_created_at'], section['section_id']
and
UNLOCK_COMMAND_1 = "UPDATE metadata_items SET added_at=?, metadata_type=? WHERE library_section_id=?;" # section['section_created_at'], section['section_type'], section['section_id']
I've updated the GitHub repo with the new commands for testing.
I've updated the GitHub repo with the new commands for testing.
Hi Mike...Do you have a strong passion towards your setuo wizard?
I had a siml. situation in Plex2CSV, and moved parts to the prefs method, making it work on the WebAdmin interface as well?
If not, I already forked, and would look into that?
/T
SIGH....And disregard.....
Yes...I can put stuff elsewhere, but the inputdirectory method is plain broken on the webadmin interface
And pht isn't an option for me, since I'm on OpenSuse, and not in the mood to try and build it first
/T
Switched application type into video, in order to try it on my Sammy's, but no dice here
Still can't set a pwd properly.....SIGH...
Attached the log, that does contains errors
/T
Switched application type into video, in order to try it on my Sammy's, but no dice here
Still can't set a pwd properly.....SIGH...
Attached the log, that does contains errors
/T
Looks like it's throwing an error because it's trying to execute the lock command with no Sections selected. Most likely a by-product of the issues with the setup wizard.
I have 2 concerns with switching from the setup wizard to using prefs.
- There's no proper way to protect the prefs. All users have access to change passwords, change selected sections, etc.
- It's not possible to build a list of prefs dynamically. So allowing users to select which section(s) to lock is not possible via the prefs menu.
I suppose we could use a combination of prefs (for password) and setup wizard (for selecting sections) but that still leaves the gaping security hole associated with the ease of changing password.
@dane22: I think you'll need to manually delete the Dict file for your install to reset the First Run Wizard.
I know that the issue with Plex/Web's handling of multiple InputDirectoryObject's has been brought up before. I'll try to find out if a fix for that is on the horizon. I suspect that if we can't support Plex/Web, that there will be a lot of users getting very frustrated.
@dane22: I think you'll need to manually delete the Dict file for your install to reset the First Run Wizard.
The logs I provided, was with a fresh restart of PMS, and with lock.bundle directories nuked from both data and cache directories ;)
I know that the issue with Plex/Web's handling of multiple InputDirectoryObject's has been brought up before. I'll try to find out if a fix for that is on the horizon. I suspect that if we can't support Plex/Web, that there will be a lot of users getting very frustrated.
That would indeed be cool if so, cuz. I sure could use this elsewhere as well.
Alternative would be for Plex to provide the Admin Interface with a client identifier, that we could detect and exclude in the code, and usefull regardless, but yes...Plex should fix this, since having an API, that doesn't work with the build-in interface, could trigger a bad rep. :lol:
