Help Center

Core Improvements to Hook Injection System:

•  Prevented theme switching on action
  Injection, uninject, and delete actions no longer force the UI to jump to the target theme. The system now preserves the user's current theme view using hook_theme.

• Injection now creates only one backup per file
  Replaced timestamped .bak.YYYYMMDD_HHMMSS logic with a single backup per template:

  • template.tpl.backByPluginSys → for inject

  • template.tpl.uninject.bak → for uninject

• Prevented duplicate hook injection attempts
  Added logic to detect if the hook is already present before re-injecting. Shows a proper message and skips file overwrite.

• Debug logs for injection diagnosis
  Temporarily added debug logging to trace file path, marker presence, and write status. Helped identify silent failures during hook insertion.

• Hook marker matching made more reliable
  Improved internal handling and matching of marker_text with strpos, now tightly controlled and consistent across themes.

• Fixed DB schema for plugin_hook_injections
  Added AUTO_INCREMENT and PRIMARY KEY to the id column to prevent all rows from being created with id = 0.

• Cleaned up logic for perform_injection and uninject
  Refactored redirect behavior, injection confirmation, and backup file creation to prevent noise, confusion, and maintenance burden.