Weave Code
Metabox Bridge Laravel Package
pollora/metabox-bridge
Bridges the Meta Box WordPress plugin with Pollora and Laravel, letting you define and manage custom fields in code and access meta box data through familiar, Laravel-friendly APIs in your theme or application.
Connect Pollora to Meta Box data: migrations and Eloquent models for MB Custom Table
Frequently asked questions about Metabox Bridge
- How do I install pollora/metabox-bridge in a Laravel app?
- Install it with Composer in a Laravel application that already uses Pollora, and upgrade pollora/metabox to 3.1 as required by the bridge. Then publish the package config with php artisan vendor:publish --tag=metabox-config and review the defaults before adopting attributes. Validate your existing post types, taxonomies, and block Blade views after installation.
- What Laravel and PHP versions does pollora/metabox-bridge support?
- The provided release details do not list explicit Laravel or PHP version constraints, so check the package composer.json and Pollora requirements before upgrading. The key compatibility constraint is pollora/metabox 3.1, which consumers on older Pollora versions must adopt or avoid by staying on a prior bridge release. Confirm your application's Laravel, PHP, and Pollora versions together.
- How do I publish the metabox-bridge configuration file?
- Run php artisan vendor:publish --tag=metabox-config to publish config/metabox.php. The config controls defaults such as block category, mode, views, and field-group priority. Review those defaults against existing behavior and keep the file under version control.
- What is attribute-based discovery and how does it work?
- Attribute discovery lets container-managed classes declare Meta Box structures with attributes such as #[FieldGroup], #[Block], and #[SettingsPage]. This reduces boilerplate for teams already using Pollora and Laravel service-container patterns. Because discovery can obscure registration behavior, validate attribute-declared classes against real post types, taxonomies, and block views.
- How are invalid attribute declarations handled?
- Invalid attribute declarations are reported without stopping other classes from being processed, which improves resilience. That also means operators must monitor logs and triage invalid declarations rather than assuming silent success. A runbook should define who reviews those reports and how misconfigurations are corrected.
- Does attribute discovery work in CLI, queue, and test contexts?
- The evaluation explicitly asks whether discovery idempotency is guaranteed across CLI, queue, and test contexts, so do not assume it without verification. Test registration in each execution path your application uses. Also confirm whether discovery results are cached or repeated at boot as declared classes grow.
- How do I migrate from an older Pollora Metabox version to v1.1.0?
- Upgrade pollora/metabox-bridge to v1.1.0 and pollora/metabox to 3.1 together, then run your existing test suite. Publish and review config/metabox.php, migrate applicable classes to the new attributes, and validate post type, taxonomy, and Blade view targets. Because 3.1 may be a breaking dependency change, plan the upgrade before changing registration code.
- Are there breaking changes in pollora/metabox-bridge v1.1.0?
- The release does not list explicit breaking API changes, but the pollora/metabox 3.1 requirement can be a breaking dependency change for applications on older Pollora versions. Config defaults introduced in v1.1.0 should also be checked against existing behavior. Treat the dependency upgrade and config review as part of the same migration.
- How do I avoid Blade namespace and view-name collisions for Meta Box blocks?
- The available details do not document a specific Blade namespace collision handler, so verify block view names by namespace and ID after migration. Keep the configurable views and mode settings intentional, and follow existing Laravel view performance and naming practices. Test for duplicate or missed block rendering when multiple classes declare blocks.
- Is pollora/metabox-bridge suitable for production and how do I monitor it?
- It is suitable for production when your application is already on Pollora and can use pollora/metabox 3.1. Monitor logs for invalid attribute declarations, missing block Blade views, unavailable post type or taxonomy targets, and container-binding errors. Track boot-time discovery work and confirm idempotency in the execution paths you deploy.
Weaver
How can I help you explore Laravel packages today?