SleepyP Wrote:DejaVu, thank you for your input but I believe you are incorrect on this point. As I posted earlier, I was able to get things working by creating a brand new MySQL database and then populating it using the "stable" 10.1 version of XBMC. The test database was created exactly the same way as the original and was given the same permissions.

Clearly some changes have taken place on the database side during development. The stable builds of XBMC use database version 42, while the nightlies are up to database version 51. This means that if you run the nightly build, it "updates" the database and then it will no longer work with the stable build. I'm gonna ask the devs what else has changed, because this more than likely means the JSONRPC parts of MediaFrontPage may need some tweaks to work on the newer XBMC builds with MySQL.

On a different note, how do you go about adding a widget?

hernandito Wrote:I think I can come up with something to do with what you have... Would you mind sharing how you did it?

Thanks!

gugahoi Wrote:I will upload it later today.... Probably merging the imdb and master branches, what do you reckon?

SleepyP Wrote:Hey guys, here's my config.php:

For the MySQL stuff I have tried a bunch of variations, like 127.0.0.1, localhost, and 192.168.1.1:3601. I guess I should roll my client XBMC back to 10.1 with IP addresses in the settings and see if that helps?

HarryRosen Wrote:I have read through the whole thread but unable to find a how to guide on setting this up, I am a total linux noob, Is there a guide on how to run this on either a WHS or xbmc live? Thanks

SleepyP Wrote:I can think of three solutions for this:
1-pack in two files and have the user rename the appropriate one during installation time

2-if its possible to query XBMC and get either the interface version or the program's version number, then it would be possible to make the JSON code check the version and then fork to either the old or new methods as needed

3-A much lighter way of accomplishing 2 would be to have a variable set in config.php that specifies which JSON-RPC behavior should be used when talking to XBMC client(s). This seems like the best way to do it since it wouldn't adversely effect current setups and would make updating to the new setup trouble-free for the end-user.

Quote:When I get home from work I will have a look at the source, though its been over a year since I did any PHP work.

DejaVu Wrote:Now, from what I read about the JSON queries being played with, would I be right in saying that the thing thats messed up is -

xbmcjsonlib.php

Code:

        'VideoLibrary.GetRecentlyAddedMovies' => array(
            'call' => '{"jsonrpc": "2.0", "method": "VideoLibrary.GetRecentlyAddedMovies", "params" : { "start" : 0 , "end" : %d , "fields": [ "genre", "director", "trailer", "tagline", "plot", "plotoutline", "title", "originaltitle", "lastplayed", "showtitle", "firstaired", "duration", "season", "episode", "runtime", "year", "playcount", "rating", "writer", "studio", "mpaa", "premiered", "album" ] }, "id" : 1 }',
            'sql' => array(
                'db' => 'video',
                'query' => 'select * from movieview order by idMovie desc limit %d',
                'resultwrapper' => 'movies'
            ),
            'args' => 50
        ),

--EDIT--
Well, seek and ye shall find!
http://localhost/xbmcjsonlib.php?tester=y

This looks completely different and just by looking at it - I know I'll break it!

Quote: # "start" and "end" parameters for methods returning an array of items have been moved into a "limits" object. So now you have to use "params": { "limits": { "start": 5, "end": 15 }, ...}

DejaVu Wrote:Installation instructions for XBMCLive are on git in the Readme.md file (which displays on the Repo splash - here.