Linux soft link trick. Client caching of results.

A couple channel development questions.  I'm developing on linux and testing with plexweb.

Both of my q's involve the need to restart the server all the time.

 


To keep my dev bundle from disappearing, I have it somewhere other than

/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-ins/

with a soft link to same.

 

I thought that PMS was supposed to reread/restart my plugin whenever I wrote one of the source files to the disk.

Did I dream this?  Or does this not work through the soft link?   The "Update" button works partially (see below).

 

 

The client behaves as if it's caching the results from me.  Even if I hit the "Update" button on the channels page,

which does run Start() again, navigating into the channel doesn't trigger a call to my handler.

I have to restart the server to have my handler called again.  Is there anyway to stop this caching behavior?

Maybe a plist setting?

 

 

Basically, is there a shorter cycle than:

  1. Edit file
  2. Restart server
  3. Navigate plex web
  4. Check logs

 

Thanks,

-tlc

The only code that generally requires a restart is plist files. Anything in the python files should be reloaded when changes are made. However, some clients do cache plugin menu content. For pure testing purposes, working directly with the XML (in a browser or via curl) works best IMO.

Start by hitting 

http://pms-ip-address:32400/video/plugin_identifier

Then you can grab the keys from the returned XML and follow the directory structure in that way. Need to make a fix, go ahead then just hit reload in your web browser to see if the returned XML changes the way you wanted it to.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.