[confirm] Settings screen fails to open, if a single ConfigSetting fails (1 Viewer)

chefkoch

Retired Team Member
  • Premium Supporter
  • October 5, 2004
    3,129
    1,634
    Dresden / Munich / Maastricht
    Home Country
    Germany Germany
    Today I created a new setting within the shutdown manager and registered it at '/Configuration/Settings/General/System'.

    I still have done something wrong, but the problem is that if one registration fails, the settings screen is not being opened at all.
    Do we really want stop opening the settings screen, even if only one registration fails?
    Would it be possible to ignore the failing registration and continue loading the others and display them at least?

    Attached is full log and plugin.xml.
    Code:
    [2012-12-18 13:51:32,817] [31677  ] [InputMgr ] [DEBUG] - ConfigurationNode: Loading configuration item '/Configuration/Settings/General/System/ApplicationSuspendLevel'
    [2012-12-18 13:51:32,844] [31704  ] [InputMgr ] [ERROR] - PluginManager: Error building plugin item 'ShutdownDialog' at location '/Configuration/Settings/General/System'
    System.ArgumentException: 'ConfigSetting' builder doesn't define an attribute 'AdditionalData'
      bei MediaPortal.Configuration.Builders.ConfigBuilder.BuildSetting(PluginItemMetadata itemData, PluginRuntime plugin)
      bei MediaPortal.Configuration.Builders.ConfigBuilder.BuildItem(PluginItemMetadata itemData, PluginRuntime plugin)
      bei MediaPortal.Common.Services.PluginManager.PluginManager.RequestItem(PluginItemRegistration itemRegistration, Type type, IPluginItemStateTracker stateTracker) in D:\MediaPortal\MP2\MediaPortal-2\MediaPortal\Source\Core\MediaPortal.Common\Services\PluginManager\PluginManager.cs:Zeile 413.
    [2012-12-18 13:51:33,039] [31899  ] [InputMgr ] [ERROR] - WorkflowManager: Error updating menu actions in workflow model '545674f1-d92a-4383-b6c1-d758cecdbdf5' for workflow state 'e7422bb8-2779-49ab-bc99-e3f56138061b'
    System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
      bei MediaPortal.Configuration.ConfigurationManagement.ConfigurationNode.Instantiate(ConfigBaseMetadata metadata, PluginRuntime pluginRuntime)
      bei MediaPortal.Configuration.ConfigurationManagement.ConfigurationNode.LoadChildren()
      bei MediaPortal.Configuration.ConfigurationManagement.ConfigurationNode.CheckChildrenLoaded()
      bei MediaPortal.Configuration.ConfigurationManagement.ConfigurationNode.get_ChildNodes()
      bei MediaPortal.UiComponents.Configuration.ConfigurationModel.NumSettingsSupported(IConfigurationNode sectionOrGroupNode)
      bei MediaPortal.UiComponents.Configuration.ConfigurationModel.NumSettingsSupported(IConfigurationNode sectionOrGroupNode)
      bei MediaPortal.UiComponents.Configuration.ConfigurationModel.UpdateMenuActions(NavigationContext context, IDictionary`2 actions)
      bei MediaPortal.UI.Services.Workflow.WorkflowManager.DoPushNavigationContext(WorkflowState state, NavigationContextConfig config) in D:\MediaPortal\MP2\MediaPortal-2\MediaPortal\Source\Core\MediaPortal.UI\Services\Workflow\WorkflowManager.cs:Zeile 518.
    [2012-12-18 13:51:33,237] [32097  ] [InputMgr ] [DEBUG] - WorkflowManager: Tidying up...
    [2012-12-18 13:51:33,238] [32098  ] [InputMgr ] [ERROR] - WorkflowManager.NavigatePushInternal: Error in workflow model or screen
    System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
      bei MediaPortal.UI.Services.Workflow.WorkflowManager.DoPushNavigationContext(WorkflowState state, NavigationContextConfig config) in D:\MediaPortal\MP2\MediaPortal-2\MediaPortal\Source\Core\MediaPortal.UI\Services\Workflow\WorkflowManager.cs:Zeile 529.
      bei MediaPortal.UI.Services.Workflow.WorkflowManager.NavigatePushInternal(Guid stateId, NavigationContextConfig config) in D:\MediaPortal\MP2\MediaPortal-2\MediaPortal\Source\Core\MediaPortal.UI\Services\Workflow\WorkflowManager.cs:Zeile 790.
    [2012-12-18 13:51:33,409] [32269  ] [InputMgr ] [INFO ] - WorkflowManager: Trying to remove 1 workflow states from navigation stack...
    [2012-12-18 13:51:33,410] [32270  ] [InputMgr ] [DEBUG] - WorkflowManager: Exiting predecessor workflow model '545674f1-d92a-4383-b6c1-d758cecdbdf5'
    [2012-12-18 13:51:33,413] [32273  ] [InputMgr ] [DEBUG] - WorkflowManager: Tidying up...
    [2012-12-18 13:51:33,415] [32275  ] [InputMgr ] [INFO ] - WorkflowManager: Trying to show screen 'home'...
    [2012-12-18 13:51:33,609] [32469  ] [InputMgr ] [DEBUG] - ScreenManager: Preparing to show screen 'home'...
    [2012-12-18 13:51:33,610] [32470  ] [InputMgr ] [DEBUG] - ScreenManager: Loading screen from file path 'D:\MediaPortal\MP2\MediaPortal-2\MediaPortal\Bin\MP2-Client\bin\x86\Debug\Plugins\Reflexion\Skin\Reflexion\screens\home.xaml'...
    [2012-12-18 13:51:33,837] [32697  ] [AMQ 'ScreenManager'] [DEBUG] - ScreenManager: Showing screen 'home'
    [2012-12-18 13:51:33,837] [32697  ] [InputMgr ] [INFO ] - WorkflowManager: Screen 'home' successfully shown
    [2012-12-18 13:51:33,838] [32698  ] [AMQ 'ScreenManager'] [WARN ] - Image: Image source '' is not supported
    [2012-12-18 13:51:33,841] [32701  ] [DX Render] [DEBUG] - ScreenManager: Closing screen 'home'
    [2012-12-18 13:51:40,139] [39000  ] [DX Render] [DEBUG] - ContentManager: 0 resources deallocated, next cleanup in 10 seconds. 72.681640625/100 MB


    EDIT: I had to change:
    <Register Location="/Configuration/Settings/General/System">
    <ConfigSetting
    Id="ShutdownDialog"​
    Text="[Settings.General.System.ShutdownDialog]"​
    HelpText="[Settings.General.System.ShutdownDialog.Help]"​
    ClassName="MediaPortal.Plugins.ShutdownManager.Settings.Configuration.General.ShutdownDialogSetting"​
    AdditionalData="WorkflowState=F499DC76-2BCE-4126-AF4E-7FEB9DB88E80,ConfAppPanel=..."/>​
    </Register>
    to
    <Register Location="/Configuration/Settings/General/System">
    <CustomConfigSetting
    Id="ShutdownDialog"​
    Text="[Settings.General.System.ShutdownDialog]"​
    HelpText="[Settings.General.System.ShutdownDialog.Help]"​
    ClassName="MediaPortal.Plugins.ShutdownManager.Settings.Configuration.General.ShutdownDialogSetting"​
    AdditionalData="WorkflowState=F499DC76-2BCE-4126-AF4E-7FEB9DB88E80,ConfAppPanel=..."/>​
    </Register>
    Nevertheless, imo, we should prevent breaking the system by an incorrect plugin.xml.
     

    Attachments

    • plugin.xml
      4 KB
    Last edited:

    morpheus_xx

    Retired Team Member
  • Team MediaPortal
  • March 24, 2007
    12,073
    7,459
    Home Country
    Germany Germany
    Thanks for reporting, I will look into this part
     

    chefkoch

    Retired Team Member
  • Premium Supporter
  • October 5, 2004
    3,129
    1,634
    Dresden / Munich / Maastricht
    Home Country
    Germany Germany
    Not sure if the attached log file of this post, is a similar case.
    This time MP2 is not starting because I define wrongs namespace in the styles.xaml.

    I expect that we can not ignore every stupid errors done in skin files.
    So this issue might not be an issue at all, since fixing the skin file solved the problem.
     

    Users who are viewing this thread

    Top Bottom