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

Entdecker

Portal Pro
May 28, 2014
152
61
Home Country
Germany Germany
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
 

Attachments

  • LogoManager-config.zip
    2.1 KB

Jasmeet_181

Portal Pro
September 5, 2007
421
344
Home Country
United Kingdom United Kingdom
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

Community Plugin Dev
  • Premium Supporter
  • January 3, 2008
    2,955
    1,264
    Saratov
    Home Country
    Russian Federation Russian Federation
    Yes, please, post logs. Nothing has changed for many years.

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

    Jasmeet_181

    Portal Pro
    September 5, 2007
    421
    344
    Home Country
    United Kingdom United Kingdom
    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

    Portal Member
    January 1, 2014
    17
    8
    48
    Home Country
    United Kingdom United Kingdom
    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
     

    Entdecker

    Portal Pro
    May 28, 2014
    152
    61
    Home Country
    Germany Germany
    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
     
    Last edited:

    Edalex

    Community Plugin Dev
  • Premium Supporter
  • January 3, 2008
    2,955
    1,264
    Saratov
    Home Country
    Russian Federation Russian Federation
    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

    Portal Pro
    May 28, 2014
    152
    61
    Home Country
    Germany Germany
    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
     

    Users who are viewing this thread

    Top Bottom