Things changed after an add-on upgrade
After you installed, upgraded or turned an add-on back on, menus moved, notifications came back on, people lost access or scheduled jobs stopped. See what each change was and how to put it right.
- Applies to
- Core 12.7 and later
- Who can do this
- Platform owner
On this page
Symptom
You installed or upgraded an add-on, upgraded Core, or turned an add-on off and on again. Since then, one or more of these:
- Menu items are back in their original places, or missing from the Admin Sidebar.
- Notifications you had turned off are sent again.
- Administrators are refused on the add-on's new screens.
- Scheduled jobs stopped.
- AI Manager's provider list is empty.
- Delivery reports from WhatsApp, Msg91 or Twilio are refused.
- Your own translations of Laramin's screen text are gone.
- Signing in with Google or another provider now asks for a two-factor code.
- Signing in with Google or another provider now answers "Access denied from your network address".
Read Check what's new in each version for the release notes of what you installed, then go through the matching checks.
Check these, in order
1. The add-on's menu items were replaced
When an add-on is turned on again or upgraded, Laramin replaces its menu items. They're put back in the Super Admin Sidebar, which Platform Administration uses, usually at the end of the Addons group, and removed from every other sidebar, such as the Admin Sidebar. Your positions, labels and hidden settings for them are lost.
Fix: place the items again in Menu Manager. See A menu item is missing or keeps coming back.
2. Notifications you turned off came back on
When an add-on install or upgrade changes the notifications that come with any add-on, Notification Manager resets the Status of every add-on's notification events, not only that add-on's.
Fix: check Status on Notification Manager's Business Events again. See A notification you turned off is sent, or goes out on the wrong channel.
3. Roles don't have the new permissions
An upgrade adds the add-on's new permissions to Laramin, but not to your roles, including the built-in Administrator role.
Fix: add them to the roles that need them. See You see "This action is unauthorized." or Access Denied.
4. Scheduled jobs stopped after Blog or AI Manager
On Core 12.8.0 or earlier, Blog 2.0.0 to 2.4.0 and AI Manager 2.1.0 to 2.3.0 stop every scheduled job, and with it the queued work that the scheduler handles.
Fix: update Blog to 2.4.1 and AI Manager to 2.3.1. See Scheduled jobs don't run.
5. AI Manager's provider list is empty
When AI Manager is installed from Addons, its provider list can start empty.
Fix: add providers with New provider. See An AI provider can't be connected or switched on.
6. Delivery reports are refused after Notification Manager 1.5.0
From 1.5.0, Notification Manager checks that delivery reports really come from the provider. Until you act, WhatsApp reports need the Meta App Secret, Twilio reports need the Auth Token, and Msg91 needs its new report address. Its card on Webhook Center shows a warning.
Fix: see Check what was sent.
7. A Core upgrade replaced your translations
For languages that come with Laramin, your changes to Core's screen text are saved in the file Laramin ships, so a Core upgrade can replace them.
Fix: see A translation doesn't show.
8. The add-on needs a newer Core
The upload or upgrade stops with "This addon requires app version … or higher (current: …)." or Addon upgrade requires system version … or higher.
Fix: upgrade Core first, then the add-on. See Run a system upgrade. Don't copy a newer add-on's files onto an older Core by hand.
9. A queue worker still runs the old code
If whoever runs your server keeps a queue worker running, it keeps the code it started with.
Fix: after every Core or add-on upgrade, they restart it:
Couldn't copy. Select the code and press Ctrl+C (⌘+C on a Mac).
php artisan queue:restart10. Social sign-in asks for a two-factor code
From Social Login 2.1.1, someone who has set up two-factor authentication is asked for their code after signing in with Google or another provider on the website or admin, as after their password. Before, a social sign-in there skipped the code.
Fix: nothing to fix: this is the protection two-factor authentication is for. Someone without their phone uses a recovery code. See How social sign-in works and You can't sign in because you lost your authenticator app.
11. Social sign-in says "Access denied from your network address"
From Social Login 2.1.2, your IP rules apply to a sign-in with Google or another provider, on the website, the admin and the mobile app, as they do to a password. Before, a social sign-in skipped them, so someone on a blocked address, or outside your allow list, could still sign in with a provider. They're now refused with Access denied from your network address. Please contact your administrator., exactly as their password sign-in from there would be. From Social Login 2.1.3, someone refused on their first social sign-in doesn't get an account either. With 2.1.2, the account was created before the refusal: you may find such accounts, with no roles, in Users Accounts › Users, and can delete them.
Fix: nothing to fix if the rule is right: the person signs in from a network you allow. If they should be allowed, change the rule. See Someone is locked out by an IP rule.
After upgrading Core to 12.8.2
Upgrading to Core 12.8.2 doesn't repair what an earlier installer set up wrongly. If your Laramin was installed with Core 12.8.1 or earlier, check each of these once:
| What you notice | What to do |
|---|---|
| Notification Manager's emails fail; Email Settings looks empty | Run php artisan app:check-, then enter every SMTP field again. See Emails from Laramin don't arrive. |
| Links from emails or other websites sign people out; social sign-in fails | Set Same-Site Cookie to Lax in Developer Tools › Developer Settings › Session Settings. See A setting or a change to the settings file doesn't take effect. |
Links in emails point at http://127.0.0.1:8000 | Set APP_URL to your site's address, and ASSET_URL and LOCAL_ASSET_URL too if they name http://127.0.0.1:8000. Then run php artisan config:clear. See Uploaded images don't show. |
| Every mobile app sign-in fails with "Mobile authentication is not configured." | Run php artisan auth:mobile-. If it reports a problem, run php artisan auth:mobile-. See Someone can't sign in to the mobile app. |
After upgrading Core to 12.8.5
| What you notice | What to do |
|---|---|
| Signing in on your website's own address shows Page not found | When the website has its own Site host, the admin and its sign-in answer only on your Laramin's own address. Sign in there. See Choose what your website's home page shows. |
| People in the mobile app see "Access denied from your network address. Please contact your administrator." | Your IP rules now apply to the app's sign-in too. Change the rule if they should be allowed. See Someone can't sign in to the mobile app. |
After upgrading Core to 12.8.6
| What you notice | What to do |
|---|---|
| Signing up in the mobile app, or entering the two-factor code there, says "Access denied from your network address. Please contact your administrator." | Your IP rules now apply to those steps too. Change the rule if the person should be allowed. See People can't create an account in the app and Someone can't sign in to the mobile app. |
An app or integration that read status and message from an IP refusal shows a blank or generic error | A signed-in API request your IP rules refuse now answers the standard error envelope: read error.code (UNAUTHORIZED) and message. See API errors and error codes. |
After upgrading Core to 12.8.7
| What you notice | What to do |
|---|---|
| Signing up on the sign-up form says "Access denied from your network address. Please contact your administrator." under the email field | Your global IP rules now apply to signing up too. Change the rule if the person should be allowed. See Someone is locked out by an IP rule. |
An app or integration gets 403 UNAUTHORIZED from POST /api/ or POST /api/ | The web API's sign-in and sign-up now follow your IP rules. Change the rule if the address should be allowed. See Authenticate API requests. |
Still not working?
Raise a ticket from Support Center in your Laramin app. Include this page's link, what you installed or upgraded, from which version to which, and what changed.
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.bsscn.com. The online article may have changed since.