STV Import: MovieTimes Movie Listings Import v0.57 Beta

[mkanet]

Just a friendly reminder to fix the "theater order bug". Other than that, I'm a happy camper. Perhaps, it's possible to make a small patch for us?

[jensen18]

I am running Sage v5.0.4.92 and SageMC v6.13a. I have tried several times importing this STV (xml) but do not see anything change.

I import the XML and go to the My Menu config but the internal screen is not available. I have tried from Studio as well but no luck. I expect that the SageMC_169 xml file would increase in size and contain some of the entries from the MovieTimes_SageMC_060.xml file (once imported) but I don't see it. The timestamp of the xml changes but no size change. Any ideas?

I am able to import xmls as I loaded the DVD burning import and it worked with no issue. Not sure what to do now...

[dflachbart]

Originally Posted by jensen18

I am running Sage v5.0.4.92 and SageMC v6.13a. I have tried several times importing this STV (xml) but do not see anything change.

I import the XML and go to the My Menu config but the internal screen is not available. I have tried from Studio as well but no luck. I expect that the SageMC_169 xml file would increase in size and contain some of the entries from the MovieTimes_SageMC_060.xml file (once imported) but I don't see it. The timestamp of the xml changes but no size change. Any ideas?

I am able to import xmls as I loaded the DVD burning import and it worked with no issue. Not sure what to do now...

Please enable debug logging before the import and post the file here, this should tell us what's going on

Dirk

[jensen18]

I followed the instructions for enabling debugging. Is a log file always created? I tried in both Client and Standalone modes (updated both properties files) but neither case generated a log file. I don't get an error when I import the STV it just appears that nothing happens.

[dflachbart]

Originally Posted by jensen18

I followed the instructions for enabling debugging. Is a log file always created? I tried in both Client and Standalone modes (updated both properties files) but neither case generated a log file. I don't get an error when I import the STV it just appears that nothing happens.

Yes, a debug log file is always created (sagetvclient_0.txt in your SageTV folder). Did you completely shut down the client before adding the property to the SageClient.properties file ?

Dirk

[jensen18]

Yes, a debug log file is always created (sagetvclient_0.txt in your SageTV folder). Did you completely shut down the client before adding the property to the SageClient.properties file ?

Yes the client and the server service were both shut down. I added the 2 properties lines to both properties files (just in case). I reloaded the orig SageMC xml and tried to import the MovieTimes xml. System asks if I would like to merge with current xml. I click Yes - nothing happens. Screen returns to Advanced screen. No .txt file created from debug. I then go import the DVD create xml. Again system asks to merge, I say yes. This time the screen switches to the Main menu. Still no debug file created. Returning to the Advanced config screen I now see that I am using an "_1" version of the xml. Could anything in the properties file prevent me from loading or getting the debug file?

Is it possible for me to try someone elses merged xml? SageMC 6.13a with MovieTimes .6a imported? If so could someone post? Should there be any issue that I am on Sage version 5?

[Morgan111]

Originally Posted by jensen18

Is it possible for me to try someone elses merged xml? SageMC 6.13a with MovieTimes .6a imported? If so could someone post? Should there be any issue that I am on Sage version 5?

I have attached an xml file that is SageMC 6.13a and the SageMC Movietimes 0.60a import. Be sure to have the other support files from the full movie times installation installed.

For the debug line, debug_logging=TRUE, make sure the TRUE is all upper case.
Also the import will not success correctly if the df_sageutils.jar file is not in the JARs directory.

[jensen18]

For the debug line, debug_logging=TRUE, make sure the TRUE is all upper case.

That would do it. I typed the lines into the properties file and the TRUE is lower case. I'll change and try it tonight.

Thanks!

[petereader]

For what it's worth, I've been battling with the same problem attempting to import both v0.60 and 0.60a. I already had v0.55b imported. Same symptoms as Jenson 18.

Thanks Morgan111 for the merged xml. I will also make good use of it if you don't mind.

As a matter of fact, thanks to you and aperry for this phenomenal plug-in. It's turned me into a superstar at home.

I would also be more than happy to turn on my logging and post it here if it will help with troubleshooting. Otherwise, I'm happy with the xml you posted. Just let me know.

[geogecko]

It amazes me why it has to be TRUE versus true. I mean, Sage should really change this.

I spent at least a day or so trying to get it to work, before I realized that was the problem.

I'm not sure that 0.55b supported applying an import over an import, did it?

I think you had to start fresh again, with an STV without the MT import.

Are you using the latest beta of V6? (.13). If so, it does not save the STV after an import, and you have to do it manually, using Studio (CTRL+SHIFT+F12), and Save As... SageMC_169-1.xml (or whatever you want).

[Morgan111]

Originally Posted by geogecko

It amazes me why it has to be TRUE versus true. I mean, Sage should really change this.

I spent at least a day or so trying to get it to work, before I realized that was the problem.

I don't understand that either. lower case is used everywhere else. That caught me more than once.

Originally Posted by geogecko

I'm not sure that 0.55b supported applying an import over an import, did it?

I think you had to start fresh again, with an STV without the MT import.

0.55b and before could not be imported over a previous version. SageMC MT imports after that can be imported over any previous version.

Originally Posted by geogecko

Are you using the latest beta of V6? (.13). If so, it does not save the STV after an import, and you have to do it manually, using Studio (CTRL+SHIFT+F12), and Save As... SageMC_169-1.xml (or whatever you want).

Could be an issue for others. He is using 5.04.

[Morgan111]

Originally Posted by petereader

I would also be more than happy to turn on my logging and post it here if it will help with troubleshooting. Otherwise, I'm happy with the xml you posted. Just let me know.

Please do.

[petereader]

Morgan111,
I'll turn on logging (TRUE) tonight when I get home from work and post it here once I try to import it again.

geogecko,
I also attempted importing a copy of v0.60 to a fresh SageMC install (on a 2 clients and a server, all with the same result). All three of these had the MovieTimes plugin installed before I reverted to a pre-MovieTimes sagemc.xml. Perhaps I didn't completely flush out all of the MT files. I will try again with a brand spanking new install on one of my clients and see how it goes.

I also thought I should mention, in case it's relevant, that I have a rather odd setup for MT. My server is holding all the files with mapped drives for the SageClient.properties file, while the config file has UNCs. The clients, of course just have the mapped drives indicated in their respective SageClient.properties files and the imported movietimes.xml file (along with the accompanying jars).

Thanks to both of you for your responses.

[jensen18]

Originally Posted by Morgan111

I have attached an xml file that is SageMC 6.13a and the SageMC Movietimes 0.60a import. Be sure to have the other support files from the full movie times installation installed.

For the debug line, debug_logging=TRUE, make sure the TRUE is all upper case.
Also the import will not success correctly if the df_sageutils.jar file is not in the JARs directory.

OK - I was able to get the debug file to generate. I was not able, however, to use the merged xml file that you posted. When I load the merged file as my app package Sage keeps reverting back to the SageTV3.xml. Here is the debug file generate when trying to add the MovieTimes import to SageMC 6.13a:

[jensen18]

Here is the debug file I get trying to load the merged xml file from Moran111. Not sure if this will help any more than the file above but both appear to be linked. Could my java version (1.5.0_05) have anything to do with this?

[dflachbart]

Originally Posted by jensen18

Here is the debug file I get trying to load the merged xml file from Moran111. Not sure if this will help any more than the file above but both appear to be linked. Could my java version (1.5.0_05) have anything to do with this?

Do you have a "xerces.jar" in "H:\Program Files\SageTV\SageTV" by any chance ? Try to move it somewhere else (or rename its .jar extension), restart Sage, and see if it makes a difference

Dirk

[jensen18]

Originally Posted by flachbar

Do you have a "xerces.jar" in "H:\Program Files\SageTV\SageTV" by any chance ? Try to move it somewhere else (or rename its .jar extension), restart Sage, and see if it makes a difference

Dirk

No - I searched the entire SageTV tree but no "xerces.jar"

[dflachbart]

Originally Posted by jensen18

No - I searched the entire SageTV tree but no "xerces.jar"

I would try to download the latest java 1.4 JRE and see if it makes a difference ... If you alreay have Java 1.4 installed, then you can make a simple change in the window registry to tell Sage to use this one:

Set "My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\CurrentVersion" to "1.4" and restart Sage


Dirk

[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.

Even though I know the suggestions were not directly aimed at me, thanks flachbar. I'm also fighting the same problem.

[jensen18]

Originally Posted by flachbar

I would try to download the latest java 1.4 JRE and see if it makes a difference ... If you alreay have Java 1.4 installed, then you can make a simple change in the window registry to tell Sage to use this one:

Set "My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\CurrentVersion" to "1.4" and restart Sage

Closed everything down. Made the registry change and restarted sage. Same symptoms still exist.