How can I determine which plugin might be causing me an issue

Isolating performance issues and/or rendering or plugin interaction issues can be a challenge. The obvious but very time consuming method is to use configure to disable plugins one at a time or in small groups, and repeatedly recreate the issue. While this is effective, there is a much easier way, the URL Parameter: debugenableplugins. When this parameter is provided, all plugins except the plugins listed in the parameter are disabled.

Example: To view this topic with all plugins except for the default plugins disabled, use:

Faq68

After clicking the link, this link to Item000 will no longer be active because ControlWikiWordPlugin has been disabled.

Remove extensions from the list to disable them, and add extensions to enable them. Here is parameter, listing all default extensions in Foswiki 1.1, for cut/paste purposes.

?debugenableplugins=AutoViewTemplatePlugin,CommentPlugin,CompareRevisionsAddOnPlugin,EditTablePlugin,HistoryPlugin,InterwikiPlugin,JQueryPlugin,PreferencesPlugin,RenderListPlugin,SlideShowPlugin,SmiliesPlugin,SpreadSheetPlugin,TablePlugin,TinyMCEPlugin,TwistyPlugin,WysiwygPlugin

If you are having unexplained issues:

• Add the above debugenableplugins to fall back to the default set of plugins to the URL of a topic with issues
• Determine if the problem still exists
  • If not, begin adding extensions to the list unit the problem returns
  • If the issue still exists
    • Try disabling all plugins. Use ?debugenableplugins=EmptyPlugin to disable all extensions
• At this point you will hopefully have determined whether or not the issue is caused by an extension.

-- GeorgeClark - 27 Feb 2012 -- Main.GeorgeClark - 18 May 2017 - 22:53