basercms-plugin-migration

Analyze baserCMS plugin migration issues from version 5.2 to 5.3.

194|141|Updated Feb 12, 2012
One-click install
npx skills add https://github.com/baserproject/basercms --skill basercms-plugin-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: basercms-plugin-migration
Source: https://github.com/baserproject/basercms/tree/main/.agents/skills/basercms-plugin-migration
Command: npx skills add https://github.com/baserproject/basercms --skill basercms-plugin-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers migrate baserCMS plugins from the 5.2 line to 5.3 by organizing the framework-specific breaking changes, deprecations, and test failures that commonly appear during the upgrade.

Core Features & Use Cases

  • Upgrade Guidance: Clarifies the required baser-core version change and the practical impact on plugin code and dependencies.
  • Test Harness Troubleshooting: Explains common failures in standalone plugin tests, including plugin loading conflicts, null plugin config issues, and duplicate CakePHP loading.
  • baserCMS-Specific Fixes: Covers issues such as subplugin class resolution, TreeBehavior content fixtures, error-page masking, and BcFile deprecation handling.
  • Use Case: A plugin maintainer can use this Skill to diagnose a failing 5.3 migration, isolate the root cause, and apply the correct baserCMS-specific repair pattern.

Quick Start

Ask for a baserCMS 5.2-to-5.3 plugin migration review for your plugin, and include any failing test messages or deprecated API warnings you want analyzed.

Frequently Asked Questions about basercms-plugin-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate a baserCMS plugin from 5.2 to 5.3?

To migrate a baserCMS plugin from 5.2 to 5.3, you analyze required baser-core version changes, update dependencies, resolve subplugin loading conflicts, correct TreeBehavior content fixtures, and replace deprecated BcFile usage to ensure framework compatibility.

Why does my standalone baserCMS plugin test harness fail after upgrading to 5.3?

Standalone baserCMS plugin test harness failures during a 5.3 migration often stem from test bootstrap conflicts, null plugin config issues, duplicate CakePHP loading, or incorrect plugin loading rules that require specific configuration adjustments.

What are the common breaking changes when upgrading baserCMS plugins to version 5.3?

Common breaking changes when upgrading baserCMS plugins to 5.3 include deprecated BcFile usage, TreeBehavior fixture corrections, subplugin class resolution errors, and error-page masking behaviors that require targeted code adjustments.

Does baserCMS 5.3 require updating plugin dependencies and loading rules?

Yes, baserCMS 5.3 requires updating plugin dependencies and loading rules, specifically addressing baser-core version changes, resolving subplugin class resolution issues, and fixing null plugin config problems to maintain stable plugin functionality.

How do I fix TreeBehavior fixture errors in baserCMS 5.3 plugin migrations?

Fixing TreeBehavior fixture errors in baserCMS 5.3 plugin migrations requires applying specific baserCMS fixture corrections to align with the updated framework's data structure expectations and resolve testing regressions.

When should I replace deprecated BcFile usage during a baserCMS 5.3 upgrade?

You should replace deprecated BcFile usage during a baserCMS 5.3 upgrade as part of the migration process to eliminate deprecated API warnings and ensure your plugin maintains compatibility with the updated baser-core framework.