- What is mortezamasumi/fb-report used for in Laravel?
- It is a Laravel package for working with Facebook report data, giving you configurable metrics plus a lightweight API to query, format, and export reports without repeating boilerplate. It fits best in Laravel applications with server-rendered Blade dashboards or reporting screens. For API-only or SPA front ends, the report-rendering and loading-screen features may be less relevant. Check the README for the exact supported report types and export formats.
- How do I install mortezamasumi/fb-report with Composer?
- Install it with composer require mortezamasumi/fb-report, pinning a constraint such as ^5.4.0 if you want the current minor release. If Laravel package discovery is enabled, the service provider should register automatically; otherwise add it to your providers list as documented. Publish any config, views, or assets the README specifies, then run php artisan config:clear and php artisan view:clear. Commit the Composer lockfile change so deployments are reproducible.
- Which Laravel and PHP versions does fb-report support?
- The provided package context does not include a version matrix, so confirm the exact Laravel and PHP constraints in the package composer.json and README before upgrading. Version 5.4.0 is a minor release after 5.3.2, so it should preserve the package API while changing default report UX. Validate it against your platform baseline in staging, especially if you run older Laravel or PHP versions. If your baseline is not supported, stay on a compatible release rather than forcing the upgrade.
- How do I configure Facebook report metrics in fb-report?
- Start by publishing the package configuration and reviewing the metric and report definitions it exposes. Define the metrics your reports need in config or in the package's report classes, following the README examples, and keep Facebook credentials in environment variables rather than source control. Because exact configuration keys are package-specific, verify them against the published config file for your installed version. Then render a small report in staging to confirm the metrics resolve correctly.
- How do I publish fb-report config, views, and assets?
- Use Laravel's vendor:publish command and select the fb-report service provider or publish tag documented in the README. Publish views only if you need to customize report rendering, since overridden views can mask new features such as the 5.4.0 loading screen. After upgrading, republish or refresh package assets if the release notes or README require it, then clear config, view, and asset caches. Always test the published output in staging before production.
- How do I disable the loading screen added in fb-report v5.4.0?
- Version 5.4.0 enables a loading screen by default for all reports, so first check the published config for a supported toggle and the documented view override path. If no configuration option exists, publish and override the relevant Blade view or pin back to 5.3.2 until an opt-out is available. Confirm whether the change affects only HTML/Blade report views or also JSON responses. Include slow and failing data sources in your smoke tests to catch stuck loading states.
- Can fb-report be used in an API-only or headless Laravel application?
- The loading screen is a presentation-layer feature, so it most likely affects server-rendered report views rather than the underlying report data. API-only consumers should verify whether the package exposes JSON responses and whether new frontend assets are loaded on non-HTML routes. If your reporting surface is SPA-based, evaluate the upgrade mainly for regressions rather than for loading-screen value. Confirm behavior in staging before relying on it in production.
- How do I export Facebook report data with fb-report?
- The package advertises querying, formatting, and exporting report data, so use its report API to retrieve and format rows, then pass that output to your preferred export step. Check the README for built-in CSV or spreadsheet export support and any required configuration before building your own exporter. Keep large exports queued rather than running them inside web requests. Test exports with realistic data volumes and slow Facebook responses.
- How can I test fb-report without calling Facebook in CI?
- Look for an injectable client or data source in the package so you can bind a fake implementation in your Laravel test container. If the package uses Laravel's HTTP client, Http::fake() can return fixture responses for report queries. Cache representative fixtures and assert on formatted report output rather than live network calls. Also test failure and timeout paths, because the 5.4.0 loading screen can remain visible when data retrieval fails.
- What should I check before upgrading fb-report from 5.3.2 to 5.4.0?
- Treat it as a low-risk minor upgrade at the API level but a user-visible behavior change because the loading screen is now enabled by default. Update the Composer constraint, run composer update in a branch, republish assets if required, and clear config, view, and asset caches. Exercise every report type, including slow and failing data sources, and compare rendering before and after. Keep a rollback pin to 5.3.2 and notify report users about the new loading state before production rollout.