- January 4, 2009
- 8
- 0
- Home Country
-
Germany
Hi there,
i was quite surprised finding an error message screaming at me after i restored my Mediaportal with the Plugin Backup Settings. However i dont think this plugin is responsible for it.
Basicly Im getting error messages when i start the MP Configuration and then go into Moving Pictures Config or TitanEditor (yes the same applies when i call these config tools directly). In case of the TitanEditor i can only click ok and by this close the entire MP Configuration. For the Moving Picture error it makes me choose: Clickin on quite exits MP Config, clicking on continue actually starts the MovingPictures Plugin. Now everything seems to be working fine. The importer starts as usual and does its thing. But when i go to the movie manager tab it just gets caught in an endless loop ("loading movies...") and never returns.
Besides the crashes in the configuration everything else works fine. I already tried to replace the movingpictures.db3 with an old one but the behaviour stays the same.
Does anybody have an idea what could be wrong?
Regards,
niutachy
i was quite surprised finding an error message screaming at me after i restored my Mediaportal with the Plugin Backup Settings. However i dont think this plugin is responsible for it.
Basicly Im getting error messages when i start the MP Configuration and then go into Moving Pictures Config or TitanEditor (yes the same applies when i call these config tools directly). In case of the TitanEditor i can only click ok and by this close the entire MP Configuration. For the Moving Picture error it makes me choose: Clickin on quite exits MP Config, clicking on continue actually starts the MovingPictures Plugin. Now everything seems to be working fine. The importer starts as usual and does its thing. But when i go to the movie manager tab it just gets caught in an endless loop ("loading movies...") and never returns.
Besides the crashes in the configuration everything else works fine. I already tried to replace the movingpictures.db3 with an old one but the behaviour stays the same.
Does anybody have an idea what could be wrong?
Regards,
niutachy