- How do I install overtrue/laravel-qcloud-content-audit in a Laravel app?
- Install it with Composer by running composer require overtrue/laravel-qcloud-content-audit. The package ships an auto-discovered service provider and a facade, so Laravel registers everything without you editing config/app.php by hand. After installing, publish the package config if you want to customise defaults, and check the README for the exact vendor:publish tag.
- How do I configure Tencent Cloud SecretId, SecretKey and region for this package?
- Credentials, region and audit scenes live in the package config file rather than in your application code. Put the values in your .env file and reference them from the config so secrets never land in version control. In production, run php artisan config:cache after deploying so the resolved values are cached.
- How do I moderate user-generated text for sensitive words, spam or abuse?
- Make a single call through the facade and pass the text you want screened. Tencent Cloud returns a result that includes a suggestion such as pass, review or block, which you can use to reject, flag or queue the content for manual review. Keep the call close to your validation or form-request layer so unsafe text never reaches the database.
- Can I audit user-uploaded images for porn or terrorism content with this package?
- Yes. The package exposes image auditing alongside text moderation, so you can submit an image for checking before it becomes publicly visible. Make sure the image scene is enabled in your config, then branch on the returned suggestion to allow, hold or reject the upload. For sensitive flows, store the image privately until the audit result comes back.
- Which Laravel and PHP versions does this package support?
- The exact PHP and Laravel constraints are declared in the package's composer.json, so check those before upgrading. The 5.x line targets modern PHP 8.3+ and current Laravel releases, and the baseline review notes there is no dual-support window within a major, so applications on older Laravel should stay on the matching earlier release. Pin the package version that matches your framework version and test the upgrade in a branch first.
- How should I handle errors and exceptions when a content audit request fails?
- Failures from the underlying API surface as exceptions, which makes them easy to catch around your moderation call. Decide deliberately whether your application should fail open (accept the content and flag it) or fail closed (reject or hold it) when Tencent Cloud is unreachable or times out. Log the exception with enough context to investigate, and consider a retry or queue for transient network errors.
- What are audit scenes and how do I set them in the config?
- Scenes tell Tencent Cloud which moderation policy and business context to apply, so different content types get different rule sets. They are configured in the package config file rather than passed on every call, which keeps your controllers clean. Set sensible defaults for your main use case and override per call only where you genuinely need a different policy.
- Can I run content moderation inside a queued job?
- Yes, the package is a normal Laravel service, so you can resolve the facade or inject the underlying client inside a job or event listener. Auditing asynchronously keeps API latency out of the request cycle, but you then need a UI state such as pending review while the job runs. Watch for API rate limits when a queue worker processes a large backlog.
- How do I test content moderation in my Laravel test suite without calling Tencent Cloud?
- Never hit the real API from automated tests. Swap the facade or container binding for a fake that returns canned suggestions, or fake the underlying HTTP responses so you can assert on pass, review and block branches. Cover the failure path too, since your fail-open or fail-closed policy is the part most likely to break in production.
- Is this package still maintained, and what are the alternatives?
- Check Packagist for recent releases and the GitHub issue tracker for response times before committing to it. The alternative is using the Tencent Cloud SDK directly, which gives you full API coverage at the cost of more boilerplate, or choosing a different moderation vendor entirely. For most Laravel teams the facade wrapper is worth it because configuration and error handling stay idiomatic.