PDA

View Full Version : No "PLUGINS" as source option bug since "-p' default changed.


djdafreund
2009-02-23, 05:28
I need to verify this before making a ticket. I found this out when recruiting a new friend to install XBMC. When you install XBMC, by the new "default" it doesn't use "-p" anymore, which means everything of course is in \username\XBMC\etc., instead of \program files\XBMC\etc.

This is the problem with current behavior. You don't get any add plugins options anymore due to the fact that since xbmc is looking in \program files\XBMC\Plugins directory instead of \username\XBMC\plugin\ directory, which of course is going to be blank. The normal person won't think to make this change and copy all there plugins into the windows \username\ directory, and even the Wiki doesn't mention any of this other then showing \program file\XBMC\plugin\ directory.

Edit- It seems that Scripts are working fine this way, but not plugins, so this prove's a glitch. When you add "-p" so that it now see's the plugins (acting backwards), you won't see any scripts anymore. I think when the devp'rs changed the '-p' behavior, the might have forgot to switch the behavior of Plugins, since it seems to be working oposite.

jmarshall
2009-02-23, 05:39
You've got it around the wrong way, as of r17948

By default, XBMC will look in the APPDATA\XBMC\plugin directory. (C:\Documents and Settings\<username>\Application Data\XBMC\plugins on XP).

With -p (portable) on win32, it will look in the XBMC directory. See the FAQ for win32.

Thus, you should copy all user data of any kind to the APPDATA\XBMC folder. Note that any plugins or scripts that are distributed with a build will currently NOT show up, as they're not in that folder.

We will be changing things so that plugins and scripts show up no matter what directory they're in (eg so that we can distribute plugins and ensure the user has the up to date one).

Cheers
Jonathan

djdafreund
2009-02-23, 06:00
Yeah, I know that, i've been using the new "\Docs etc.\App..\XBMC\plugins\" for my user stuff since then. But what i was saying, by default (not using -p) xbmc looks in the \Docs etc.\App..\XBMC\plugins\ with the recent flip, BUT XBMC is currently looking in \program files\xbmc\plugins\ when not using "-p", and looks at "\Docs etc.\App..\XBMC\plugins\" when using "-p" (New correct way), however, Script's directory it finds fine when not using "-p", but just not Plugins.

So basically, this is what i am saying.
Scripts without '-p' it's looking at the Program Files\XBMC\Scripts directory, and WITH '-p' it's looking in the "\Docs etc.\App..\XBMC\scripts\" directory.
Plugins without '-p' it's looking at the "\Docs etc.\App..\XBMC\plugins\", and WITH '-p' it's looking in the program files\xbmc\plugins\ directory.

So basically the plugins is working oposite as scripts. I know it's now looking at the "\Docs etc.\App..\XBMC\plugins\" with recent xbmc changes, but it seems like if you flipped the behavior of plugins (like how scripts is already working now), it would work the right way. The 2 above are currently working exactly the oposite with where they are looking as far as directory locations. I hope i am being clear with my explanation. I understand how it's supposed to work now with '-p' (portable, using XBMC\ and not Username\XBMC\) but one of the 2 are currently working backwards with the "-p" behavior. Please try it and see before saying i am wrong. I just confirmed this with 2 people. So either way since this isn't going to work until you guys (as you mentioned) change it to look no matter which directory, Scripts is currently working backwards and you still need to know that.\

Edit2- So until then, plugin's can't be used at all for now. AMT gives an error, Hulu (yes i know it can't connect since they blocked) error's, and Home Theater plugin can't load because it's looking for database in \program files\xbmc\scripts\Apple Movie Trails\ directory, no matter if using "-p" or not.

Edit3- Just got e-mail explaining what needs to be done ("special://home/") instead of using (Q:,E:,U:,etc.) for all the traces in scripts and plugins. I can wait til those are updated. That's more then i want to do with being limited knowledge of python myself. LOL

jmarshall
2009-02-23, 07:23
Which revision are you using? If it's not r17948 or later, then you don't have the changes.

Everything as it is now should be using special://home/ (which without -p is in Documents and Settings) first and foremost.

I've just tried, and sure enough, without -p, scripts and plugins are looking in special://home/.

With -p, they're both looking in special://xbmc/ as designed.

Cheers,
Jonathan

djdafreund
2009-02-23, 08:33
I'm using XBMCSetup-Rev17994. Now it's showing scripts with "-p" and not without. I don't know what happened earlier then. I swear scripts was reversed and plugins worked the right way. But now, it see's both when "-p" enabled. Well, either way i guess i will have to wait till all the plugins are updated to use them again, since they are throwing error's until the dir stuff is fixed.

jmarshall
2009-02-23, 08:39
Anything that you installed under the old system might not work. Anything installed fresh should work still just fine (assuming they worked before r17948).

AMT and it's plugins for instance should work without a problem.

djdafreund
2009-02-23, 17:43
Well, the Home Theater Plugin is throwing a prompt saying no database has been found and i want to run the script, which i just did, and prompts every time i go ahead and run it just to test. The AMT Plugin is throwing an error-
"Scripts
Error.
Python Script Failed.
Special://home/plugins/video/Apple Movie Trailer/default.py"

And my friend who builds svn's daily also is getting the same error. That was how i found it honestly since i don't use the Plugin's as much and just mostly use the AMT script, which works fine. Sorry to be a pain, just trying to figure out what's causing this.

jmarshall
2009-02-23, 22:02
Run through the various .py files in the plugin (in amtAPI) and wrap the amt_data_db with a xbmc.translatePath() and it'll work just fine.

Problem is the settings path is being saved untranslated. I'll drop Nuka a line.

Cheers,
Jonathan