When a sub-theme is carrying a plug-in, its base theme should not have access to it. Activating the plug-in for the base theme then deactivating the child will cut off any access to the plug-in.

CommentFileSizeAuthor
#1 patch_commit_839f1fa4ae6c.patch13.63 KBdvessel

Comments

dvessel’s picture

Status: Active » Fixed
StatusFileSize
new13.63 KB

This patch solves a lot of dependency issues.

  • Prevent a base theme plug-in from enabling a sub-theme plug-in. (original issue)
  • Prevent a base theme plug-in from setting a sub-theme plug-in as its dependency.
  • Slight change to the settings form so each plug-in host has its own field set. This makes it clear on where each plug-in is hosted.
  • Disable checkboxes when required plug-ins are not enabled. I tried using form api #states but it's useless. If you have dependent plug-ins, expect to save the form multiple times because of the forced disabled state.
  • Also solves #1148624: .info enabled plug-in's show the wrong state in the theme settings form. since that was a symptom of how wrong it was handled in code.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.