Installation
Step 1: Upload the add-on
Go to Admin panel → Extensions → Add-ons, click Upload add-on and drop the add-on's .zip file into the upload area (50 MB maximum).
The archive is extracted into extensions/addons/reviews/ and Reviews appears in the list, deactivated.
extensions/addons/reviews/ over FTP or SSH: its addon.json file must sit directly inside that folder.
Then open Admin panel → Extensions → Add-ons. The page scans extensions/addons/ every time it loads, so the add-on is listed straight away (the Sync button runs the same scan on demand).
Step 2: Activate the add-on
Click Activate on the Reviews card. It is a paid add-on, so a dialog asks for its purchase code, which is verified before anything else happens: an invalid code is rejected in the dialog and nothing is changed.
Once the code is accepted, activation runs in one pass: it creates the add-on's database tables (its migrations), registers its permissions, runs its seeders and publishes its public assets. Reload the page to see its new entry in the Add-ons section of the admin sidebar.
Step 3: Configure
Open Admin panel → Reviews from the Add-ons section of the sidebar and set the add-on up: see Configuration.
Purchase Code (License Key)
Reviews System is sold as a separate product, so it has its own purchase code (license key), distinct from the purchase code of the main application and from the one of every other add-on. You are asked for it when you activate Reviews System in Admin panel → Extensions → Add-ons.
Our products are sold on three platforms. The way you receive a purchase code depends on where you bought the product.
| Platform / Marketplace | How you get the purchase code | Where to find it again |
|---|---|---|
| bedigit.com Store In-site purchase (Shop) |
Generated automatically when the order is paid, then sent by email, either in its own license email, or inside the order confirmation email. | My Account → My Licenses on bedigit.com |
| Gumroad | Created as soon as Gumroad notifies us of the sale, then sent in a separate email, in addition to the Gumroad receipt. | The license email, your Gumroad Library, and My Account → My Licenses on bedigit.com |
| Envato Market CodeCanyon |
Issued by Envato, not by us, and never sent by email: you download it yourself from your Envato account. | Envato account → Downloads → License certificate & purchase code |
1. bedigit.com Store (in-site purchase)
- As soon as the order’s payment status becomes Paid, a license key is generated automatically for every licensed item in the order (one key per purchased unit: buying 3 units gives 3 distinct keys).
- It is emailed to the address used on the order, either in a dedicated license email or inside the order confirmation email. Check your inbox and your spam / junk folder.
- The key stays available in your account under My Account → My Licenses. Keys are masked in the list; open the license detail page to reveal and copy the full key, see the domains it is activated on, and deactivate a domain to free an activation slot.
- The matching invoice is under My Account → My Orders.
2. Gumroad
- A Gumroad purchase produces two separate emails: the Gumroad receipt (sent by Gumroad, giving access to the files) and a license key email (sent by bedigit.com) that contains your purchase code.
- The license key email is generated as soon as Gumroad notifies us of the sale, so it normally arrives within seconds of the payment. Here too, check your inbox and your spam / junk folder.
- When the Gumroad product uses Gumroad’s own license-key feature, the same key also appears in your Gumroad receipt and under Library → your purchase on gumroad.com.
- Use the same email address on bedigit.com as on Gumroad: your keys are then linked to your account automatically and listed under My Account → My Licenses, even if you register after the purchase. You can also add a Gumroad key manually from My Account → My Gumroad Licenses.
3. Envato Market (CodeCanyon)
- Envato purchase codes are issued and delivered by Envato Market, never emailed by us, so there is nothing to look for in your spam folder: you retrieve the code from your Envato account.
- Log in to your Envato / CodeCanyon account, open the Downloads page, find the item, and choose License certificate & purchase code from the Download dropdown. The code is written in that certificate.
- An Envato purchase code looks like
12345678-90ab-cdef-1234-567890abcdef(8-4-4-4-12 characters). It never changes, and renewing item support does not issue a new one. - Official Envato article: Where Is My Purchase Code?
Compatibility
- v5.0.2 => LaraClassifier v19.1.0+
- v5.0.1 => LaraClassifier v19.1.0+
- v5.0.0 => LaraClassifier (v19.0.0 to v19.0.1)
- v4.4.6 => LaraClassifier v18.3.0+
- v4.4.5 => LaraClassifier v18.2.0
- v4.4.4 => LaraClassifier v18.1.1
- v4.4.3 => LaraClassifier v18.1.0
- v4.4.2 => LaraClassifier v18.0.3
- v4.4.1 => LaraClassifier v18.0.2
- v4.4.0 => LaraClassifier v18.0.1
- v4.3.9 => LaraClassifier v18.0.0
- v4.3.8 => LaraClassifier (v17.1.0 to v17.1.1)
- v4.3.7 => LaraClassifier v17.0.0 to v17.0.1
- v4.3.6 => LaraClassifier v17.0.0
- v4.3.5 => LaraClassifier v16.0.1 to v16.0.2
- v4.3.4 => LaraClassifier v16.0.0
- v4.3.3 => LaraClassifier v15.4.0 to v15.4.1
- v4.3.2 => LaraClassifier v15.3.4 to v15.3.5
- v4.3.1 => LaraClassifier v15.3.3+
- v4.3.0 => LaraClassifier v15.2.0+
- v4.2.2 => LaraClassifier v15.1.0 to v15.1.6
- v4.2.1 => LaraClassifier v15.1.0
- v4.2.0 => LaraClassifier v15.1.0
- v4.1.0 => LaraClassifier v15.0.0
- v4.0.2 => LaraClassifier v14.1.0 to v14.2.0
- v4.0.1 => LaraClassifier v14.0.2 to v14.0.3
- v4.0.0 => LaraClassifier v14.0.0 to v14.0.1
- v3.9 => LaraClassifier v13.0.0
- v3.8 => LaraClassifier v12.1.0 to v12.2.4
- v3.7 => LaraClassifier v12.0.0 to v12.0.2
- v3.6 => LaraClassifier v11.0.2 to v11.0.4
- v3.5 => LaraClassifier v11.0.0 to v11.0.1
- v3.4 => LaraClassifier v10.2.0 to v10.2.6
- v3.3 => LaraClassifier v10.2.0+
- v3.2 => LaraClassifier v10.1.2 to v10.1.4
- v3.1 => LaraClassifier v10.1.0 to v10.1.1
- v3.0 => LaraClassifier v10.0.2
- v2.9 => LaraClassifier v10.0.0 to v10.0.1
- v2.8 => LaraClassifier v9.0.0 to v9.0.1
- v2.6 => LaraClassifier v8.0.0 to v8.0.6
- v2.5 => LaraClassifier v7.3.7 to v7.3.8
- v2.4 => LaraClassifier v7.3.5 to v7.3.6
- v2.3 => LaraClassifier v7.1.0 to v7.2.4
- v2.2 => LaraClassifier v7.0.0 v7.0.4
- v2.1 => LaraClassifier v6.9
- v2.0 => LaraClassifier v6.8
- v1.9 => LaraClassifier v6.6 to v6.7
- v1.8 => LaraClassifier v5.7 to v6.5
- v1.7 => LaraClassifier v5.2 to v5.6
- v1.6 => LaraClassifier v5.1
- v1.3 to v1.5 => LaraClassifier v4.4 to v5.0
- v1.1 to v1.2 => LaraClassifier v3.7 to v4.3
- v1.0 => LaraClassifier v3.1 to v3.6
Updating
An update only replaces the add-on's files. Its database tables and data, its settings, its activation state and its recorded purchase code are all kept, so do not deactivate or remove the add-on before updating it. Back up your database first all the same.
Method 1: Upload the new version (recommended)
- Download the latest
.zipfile of the add-on. - Go to Admin panel → Extensions → Add-ons and click Upload add-on.
- Drop the
.zipfile into the upload area. - Because Reviews is already installed, a prompt shows the installed version and the new one. Click Replace: the
extensions/addons/reviews/folder is swapped for the new files. Cancelling the prompt discards the upload.
Method 2: Replace the files by hand
- Over FTP or SSH, delete the
extensions/addons/reviews/folder and upload the new one in its place. Replace the whole folder rather than copying over it, so files dropped by the new version do not linger. - Open Admin panel → Extensions → Add-ons: the page re-reads
addon.jsonand the card shows the new version number.
After the files are replaced
New database tables or columns. When a new version adds some, create them by running php artisan migrate --force over SSH, or without SSH by clicking Deactivate then Activate on the add-on's card: activation runs every pending migration (and asks for the purchase code again). Your data is not touched either way.
Public assets. The add-on's public files are copied to public/vendor/reviews/ when it is activated, and replacing its files does not refresh that copy. When an update changes them, republish them with php artisan vendor:publish --tag=reviews-assets --force, or click Deactivate then Activate on its card.
If your installation caches its configuration or routes (php artisan config:cache, route:cache), run php artisan optimize:clear after the update.
Configuration
The add-on adds a Reviews tab to the listing details page, where visitors rate the listing from 1 to 5 stars and leave a comment (10 to 1,000 characters). New reviews are published immediately, and the listing's average rating and number of ratings are recalculated after each review. Listing owners cannot review their own listings: the review form is not shown on their own listings, and a review they submit anyway (for example through the API) is refused with the message You cannot add reviews for your own listings.
Settings
Go to Admin panel → Reviews → Settings (in the Add-ons section of the sidebar) and click Save after your changes.
| Field | Description | Default |
|---|---|---|
| Allow Guests to post Reviews | When enabled, visitors who are not logged in can also post ratings and comments. When disabled, only logged-in users can post a review: guests see a message asking them to log in instead of the form, and a review sent without being logged in (for example through the API) is refused with the message You must be logged in to post a review. | Off |
Moderating reviews
Go to Admin panel → Reviews → All reviews to list every review. You can:
- search the comment text and filter by Approved / Pending, Spam / Not spam and Rating;
- edit a review in a dialog (comment, Approved and Spam flags): only reviews that are approved and not marked as spam are shown on the website;
- delete one review, or select several and delete them in bulk.
Translation
To translate this addon into your language:
- Go to the languages folder at
/extensions/addons/reviews/resources/lang/ - Duplicate the folder
/extensions/addons/reviews/resources/lang/en/to/extensions/addons/reviews/resources/lang/<code>/
NOTE: Don't forget replace<code>by your language code (e.g. "de" for German language). - Open the file
/extensions/addons/reviews/resources/lang/<code>/messages.phpand translate it.
NOTE: To translate the file, you must change the values and not the keys of the PHP array.
Uninstallation
Switching an add-on off without losing anything is a deactivation: go to Admin panel → Extensions → Add-ons, click Deactivate on the Reviews card and confirm.
- The add-on is no longer loaded: its routes, views, admin sidebar entry and front-end pages stop answering.
- Its database tables and all the data they hold are kept, and its files stay under
extensions/addons/reviews/. Nothing is deleted. - Its permissions and its recorded purchase code stay in the database. Only Remove deletes them.
- Deactivation is refused while another active add-on depends on this one: deactivate that add-on first.
Click Activate on the same card to switch it back on. As for a first activation, the purchase code is asked for and verified again; then any pending migrations run, the assets are republished, and the add-on picks up exactly where it left off.
Removing
Removing is permanent and destroys the add-on's data. The Remove button only appears on a deactivated add-on, so removal is always two steps:
- Deactivate Reviews (see Uninstallation).
- Click Remove on its card and confirm the prompt.
The admin panel then, in one pass:
- runs the add-on's uninstall hook, if it ships one, while its code is still on disk;
- revokes the permissions declared in its
addon.json; - rolls back its migrations (this drops its database tables and every row they hold) and purges its entries from the
migrationstable, so a later reinstall migrates from scratch; - deletes its published assets:
public/addons/reviews/,public/vendor/reviews/andstorage/app/public/addons/reviews/; - deletes the add-on directory
extensions/addons/reviews/; - deletes its row in the
addonstable (the recorded purchase code goes with it) and clears the application cache.
Removal is refused, with an explanatory message and before anything is destroyed, when the add-on is still active, when another active add-on depends on it, or when the web server (PHP) user cannot delete extensions/addons/reviews/. In that last case, give that user write permission on the directory and on its parent, then try again.
Deleting the folder over FTP or SSH is not equivalent: the add-on is only switched off, and its tables, its entries in the migrations table and its addons row are all left behind. Use Remove in the admin panel instead.