STV Import: MovieTimes Movie Listings Import v0.57 Beta

[jensen18]

Originally Posted by petereader

In case it could still be of use, here is my debug file. I went ahead and uninstalled my client, reinstalled, turned on logging, added sagemc, then attempted to import MT with the same result as Jensen. I'm using Java 1.4.2_11 but will see if there is a newer version. I'll try the reg edit if all else fails.

Were you able to use the merged XML posted by Morgan111?

[petereader]

Originally Posted by jensen18

Were you able to use the merged XML posted by Moran111?

No luck. Same thing. Nothing happens when I select it. I just updated to Java 1.4.2_13 but that had no impact.

[petereader]

I'll tell you what though, the old MovieTimes is working just fine for me. I just reimported it and got it working (v0.55b-I never downloaded v0.57). I should say, I'm using all of the components of v0.60 with the xml of version .55b.

[dflachbart]

Originally Posted by petereader

I'll tell you what though, the old MovieTimes is working just fine for me. I just reimported it and got it working (v0.55b-I never downloaded v0.57). I should say, I'm using all of the components of v0.60 with the xml of version .55b.

Mhhh, this got me thinking ...

Maybe Morgan saved the v0.60 STV accidently with SageTV 6.0 ? The STV format is *not* compatible with SageTV 5.x, so maybe this is causing the XML parser exceptions...


Dirk

[jensen18]

Originally Posted by petereader

I'll tell you what though, the old MovieTimes is working just fine for me. I just reimported it and got it working (v0.55b-I never downloaded v0.57). I should say, I'm using all of the components of v0.60 with the xml of version .55b.

could you post the v.55b xml? - I would like to see if I can import that successfully and I'm not sure it is available anywhere else.

[Morgan111]

Originally Posted by petereader

I'll tell you what though, the old MovieTimes is working just fine for me. I just reimported it and got it working (v0.55b-I never downloaded v0.57). I should say, I'm using all of the components of v0.60 with the xml of version .55b.

The debug log doesn't have anything that is obvious to me (from what I can understand). Could you capture a debug log with the base STV loaded and wheile trying to load the new MovieTimes 0.60a import?

[jensen18]

Originally Posted by flachbar

Mhhh, this got me thinking ...

Maybe Morgan saved the v0.60 STV accidently with SageTV 6.0 ? The STV format is *not* compatible with SageTV 5.x, so maybe this is causing the XML parser exceptions...

If only I had seen the message that the upgrade key was $30 through 11/1 I would probably be running v6 right now.

[dflachbart]

Originally Posted by jensen18

If only I had seen the message that the upgrade key was $30 through 11/1 I would probably be running v6 right now.

I can confirm that the STV is in v6.0 format. You can try the attached version, but I'm not sure if it will fix it ...

Dirk

[Morgan111]

Originally Posted by flachbar

Mhhh, this got me thinking ...

Maybe Morgan saved the v0.60 STV accidently with SageTV 6.0 ? The STV format is *not* compatible with SageTV 5.x, so maybe this is causing the XML parser exceptions...


Dirk

Dirk, Are you saying that if I create/save an import with Studio from SageTV 6.0 that it will be incompatible with SageTV 5??

[jensen18]

Originally Posted by Morgan111

The debug log doesn't have anything that is obvious to me (from what I can understand). Could you capture a debug log with the base STV loaded and wheile trying to load the new MovieTimes 0.60a import?

If you mean the base SageMC STV loaded then see my first debug log post:
http://forums.sagetv.com/forums/show...&postcount=479

If you mean the base Sage stv being SageTV3.xml then I'm not sure I follow as I don't believe it allows you to import XML files but instead needs a stvi which the .60a download did not include.

[Morgan111]

I meant the SageMC STV as the baseline. But it sounds like there may be a format incompatability with the MT .60a import...

[dflachbart]

Originally Posted by Morgan111

Dirk, Are you saying that if I create/save an import with Studio from SageTV 6.0 that it will be incompatible with SageTV 5??

Yeah, unfortunately this is true ...

You can read more about it here . It's now a PITA to support both 6.0 as well as older 5.x STVi's ...


Dirk

[jensen18]

Originally Posted by flachbar

I can confirm that the STV is in v6.0 format. You can try the attached version, but I'm not sure if it will fix it ...

That did it! I finally got a new xml file generated and the internal screen is now available. Now I have to get the rest of the config completed for it to work but it appears that the technical issue is resolved.

Thanks to all for the help esp Dirk.

[petereader]

Jensen18,
Here is MT0.55b. I'm sorry I have nothing newer but it should work. Perhaps we could persuade Morgan to post a v0.57 , but at least this version works for me. Just don't forget that you still want to use the mtsa that came with v0.60.

Morgan,
If you still think thedebug file with the base sagemc will be useful, I could try that tomorrow. I've got a few shhows I need to catch up on in the meantime before the evening ends

[Morgan111]

Ah! One silly line causes all this problem! I'll update the downloads. Thanks for the help Dirk.

By the way, if there are any further issues with the SageMC version of the MT import they can be brought up in the forum thread for the import here

[petereader]

Oops,
Looks like Jensen beat me to the punch. Glad to here this file works though. I may go ahead and try it tomorrow myself, even though everything is working just fine with ver.055b...oh how I love to tempt fate.

Thanks flachbar and everyone else who helped. Stay tuned, I may be back tomorrow.

[jensen18]

Originally Posted by flachbar

I can confirm that the STV is in v6.0 format. You can try the attached version, but I'm not sure if it will fix it ...

It appears that I spoke too soon. I am able to load the import but unable to complete configuration. I'm not sure if the config and locations xml files have to be v5 as well or if the file you provided imports ok but doesn't work 100% correctly. At this point I think we agree that it is due to the v5 vs v6 xml differences.

Morgan - is there anyway you could generate a version of your import for Sage v5?

EDIT - Sorry Morgan - just saw your post about the updated version - could you check that the config and locations xml files are correct as well

[Morgan111]

The support files created by aperry, other than the MTSA.exe, program haven't changed for a long time and should not need any update. Getting the configuration setup, especially on a client, take a little care. Make sure you have .NET installed on your server system and check carefully in the installation pdf file for setting it up. It really does not specify differences for when running on a client. You may want to review some of the installation issues starting around page 3 of this thread.

[jensen18]

Originally Posted by Morgan111

The support files created by aperry, other than the MTSA.exe, program haven't changed for a long time and should not need any update. Getting the configuration setup, especially on a client, take a little care. Make sure you have .NET installed on your server system and check carefully in the installation pdf file for setting it up. It really does not specify differences for when running on a client. You may want to review some of the installation issues starting around page 3 of this thread.

I started with the base SageMC and added your new v.60b MT. I do have .NET v1.1 installed. My issue is that when I go into the Config screen all the options on the left hand menu: Back, Load Config File, ... (can't see them all) are all on top of one another and Back and Load Config are the only two selectable as all the others are shorter than load config. Thus why I questioned if those files had to be v5 as well. I now see they have nothing to do with the screen UI. The current config screen menu looks like this:

Back config file
(all on one line with a bunch of extra characters underneath from the other menus)

The default screen is the General config but the many of those options don't work so well. I am able to configure the Config settings via the XML file but I am lost when it comes to the location settings. I don't know if this is also a result of the version differences as well, but right now the config screen is unusable.

[Morgan111]

Originally Posted by jensen18

I started with the base SageMC and added your new v.60b MT. I do have .NET v1.1 installed. My issue is that when I go into the Config screen all the options on the left hand menu: Back, Load Config File, ... (can't see them all) are all on top of one another and Back and Load Config are the only two selectable as all the others are shorter than load config. Thus why I questioned if those files had to be v5 as well. I now see they have nothing to do with the screen UI. The current config screen menu looks like this:

Back config file
(all on one line with a bunch of extra characters underneath from the other menus)

The default screen is the General config but the many of those options don't work so well. I am able to configure the Config settings via the XML file but I am lost when it comes to the location settings. I don't know if this is also a result of the version differences as well, but right now the config screen is unusable.

Does it look like the screen shot in post 454? That somehow was fixed after reloading the SageMC STV and then importing the MT file. You can try that, but you shuld have debug turned on and post the debug log if it still appears incorrectly.