LogoManager 1.0.0.3 [27-11-2022] (10 Viewers)

[Entdecker]

Dear Jasmeet_181,

Thank you for your answert!

Unfortunately the LogoManager still does not work :-( I use now the attached "logomanager.config".

Do you know were I can find the "log" file from LogoManager?

When I undstand you correct your LogoManager still working?


Entdecker

 

[Jasmeet_181]

Yes LogoManager is working for me, it writes to MediaPortal.log and MediaPortal-Error.log in C:\ProgramData\Team MediaPortal\MediaPortal\log, could you attach them please?

 

[Edalex]

Yes, please, post logs. Nothing has changed for many years.

Отправлено с моего Redmi 3S через Tapatalk

 

[Entdecker]

Thank you for your answer! Here are my log files

 

[Jasmeet_181]

There is a 404 error while updating the package settings but the logs don't show a grab attempt. I did spot one problem, can you change the selected design and then try to run a grab? Simple Black Glow was a test template I used and not included with the LogoManager installer.

 

[steven123]

Just run the logo manager. It is working for me as well.
It's not something to do with the skin you are using is it? I run Streamed MP, but have to change it to Titan to run logo manager in plugins

 

[Jasmeet_181]

I run Streamed MP, but have to change it to Titan to run logo manager in plugins

Here are the skin files for StreamedMP, put them in C:\ProgramData\Team MediaPortal\MediaPortal\skin\StreamedMP\
https://github.com/Jasmeet181/LogoManager-updates/blob/master/Skin/StreamedMP/StreamedMP LogoManager skin files.zip?raw=true

 

[Entdecker]

Hello ,
Thanks again for the help. I have now found the problem through your hint, your answer and the answer from a friend has brought the solution.

The problem was that the file stored under:

C:\ProgramData\Team MediaPortal\MediaPortal

was defective.

Normally the file is located under

C:\Program 86\TemMediaPortal\mediaPortal\windows\Plugins\LogoManager.config

this file is apparently placed in the directory

"C:\ProgramData\Team MediaPortal\MediaPortal" after a logomanager search.

I had placed the new "logomanager.config" under
"C:\Program 86\TemMediaPortal\mediaPortal\windows\Plugins\LogoManager.config".

for some reason, however, the file was the file was stored under

"C:\ProgramData\Team MediaPortal\MediaPortal\logomanager.config" was not overwritten.

The reason for this was probably that I used the same configuration in the Logomanager for a search as the file that was already there, so the defective file was probably not overwritten. (incorrect assumption)

After I had delete the old "logomanager.config" or saved the new file under

"C:\ProgramData\Team MediaPortal\MediaPortal\logomanager.config"

the Logomanger delivered imediately "Logos" without any problems. Both the latest downloaded "logomanager.config" and a old file from a Backup worked again.

Thanks again for trying it out.

cu,

Entdecker

 

[Edalex]

Ahh, I've had so many theories :-( Also I've prepared many tests for you which are not needed now :-(
Config should be placed in Mediaportal folder, I'm almost sure we didn't hardcode any folders

Отправлено с моего Redmi 3S через Tapatalk

 

[Entdecker]

Hi Edalex,
ok then it was my mistake I had the new "logomanager.config" first copyed under

C:\Program 86\TemMediaPortal\mediaPortal\windows\Plugins\

Only after I had deleted the old "logomanager.config" under

"C:\ProgramData\Team MediaPortal\MediaPortal\logomanager.config"

the logomanager work again. Do I understand correctly that the logomanager plugin downloads a missing "logomanager.config" automatically?

I ask because I had always copied the new "logomanager.config" to the wrong directory at first and yet after deleting the file under "C:\ProgramData\Team MediaPortal\MediaPortal\logomanager.config", a new "logomanager.config" was created from the Logomanager Plugin.

Entdecker