ReviewUpgrading.
Install the complete review experience, choose an interface, and configure customer and team workflows.
← All Pro topicsUpgrading
Back up your database/files and test upgrades in staging. Update Composer dependencies, inspect new migration/config requirements, run pending migrations, and compare any published view overrides with the new package templates.
Core's GitHub repository includes its source, changelog, and issue tracker. Pro's docs cover the current 1.1.0 release and its published interfaces. Review the Pro license terms before purchasing; licensed releases are installed through CodebyRay’s private Composer repository.
Upgrade to Pro 1.1.0
Set the application's minimum Pro version and update the lockfile through the private repository:
composer require codebyray/laravel-review-rateable-pro:^1.1 --no-update
composer update codebyray/laravel-review-rateable-pro --with-dependencies
The dependency update may also select Core 2.3.0. No new migration is required for the rating aspect selector. If your application uses Pro's shipped Livewire templates, the new selector comes with the package. If you published Livewire list views, compare them with the 1.1.0 views and merge the selector into your overrides.
React and Vue components are copied into your application when published, so Composer does not update those files. Review local changes before re-publishing the interface you use; --force overwrites published files:
php artisan vendor:publish --tag=review-rateable-pro-react --force
# Or, if your application uses Vue:
php artisan vendor:publish --tag=review-rateable-pro-vue --force
npm run build
After rebuilding and deploying, open the review list with more than one criterion and confirm that Rating aspect changes the headline and distribution.
Never commit license credentials, Composer authentication, customer data, or populated environment files. Expired Pro update access is not intended to disable installed review functionality.