What's new

Release notes for the core platform and the modules, newest first.

Core

Core 12.8.7

Your IP rules now apply to the web sign-up form and to the web API's sign-in and sign-up.

Security

  • Your IP rules now apply when someone signs up on the sign-up form, with Allow public registration on, as they already did to signing in. Before, someone on a network address your rules refuse could create an account there and be signed in, and was sent the verification email. The form is now checked against your global rules before the account is created, because the account doesn't exist yet. A refused address sees Access denied from your network address. Please contact your administrator. under the email field, as on the Sign-In screen. No account is created and no email is sent. Someone on an allowed address signs up as before. See How IP access control works.
  • For developers: POST /api/v1/web/login and POST /api/v1/web/register now follow your IP rules too. They issued a web token without checking them. The sign-in is checked before the password, against the account's own rules, then its roles', then the global ones, with the super-admin break-glass, exactly like the Sign-In screen. An email address that doesn't belong to an account gets the global rules. Sign-up is checked against the global rules before the account is created, after the Allow public registration check. A refusal answers 403 with error.code UNAUTHORIZED and Access denied from your network address. Please contact your administrator. It issues no token, creates no account, and doesn't say whether the email address is already registered. The web token still isn't accepted by the other /api/v1/web/… endpoints. See Authenticate API requests.

Core

Core 12.8.6

Signing up in the mobile app, and its two-factor step, follow your IP rules, and the API's IP refusal has an error code.

Fixed

  • When your IP rules refused a request from someone already signed in to the API, the answer was {"status": false, "message": "Access denied from your network address."}, the only API error without the standard envelope and an error code. It now answers like every other API error: 403, error.code UNAUTHORIZED, and Access denied from your network address. Please contact your administrator., the message a refused sign-in gets. An app or integration that read status reads error.code instead. See API errors and error codes.
  • The maintenance page's title is now saved under its correct name, maintenance_title. It was saved under a misspelt one, maintenance_tite. The upgrade renames your saved title, so your maintenance page keeps it, and nothing changes on screen. For developers: GET /api/v1/public/settings now has consent.maintenance_title, and keeps consent.maintenance_tite, with the same value, until the next major version. The older GET /api/v1/mobile/get_setting lists the row under its new name.

Security

  • Your IP rules now apply when someone signs up in your mobile app and when they enter their two-factor code there, as they already did to the app's password sign-in. Before, someone on a network address your rules refuse could create an account in the app and be signed in when they verified it, or finish at the two-factor step a sign-in they'd started from an allowed address. Signing up is checked against your global rules before the account is created, so a refused address leaves no account and gets no email. Entering the emailed code, and getting the first sign-in after verifying in a browser, are checked against the new account's own rules, then its roles', then the global ones. The two-factor step is checked again for the account signing in, before the code. A refused step gets Access denied from your network address. Please contact your administrator. and no session, and uses up no code, attempt or sign-up session: it works from an allowed network. Someone on an allowed address signs up and signs in as before, and the super-admin break-glass works as on the web. See How IP access control works and People can't create an account in the app.

Core

Core 12.8.5

The mobile app's sign-in follows your IP rules, and the admin's sign-in is no longer on your website's own address.

Fixed

  • With Google reCAPTCHA, Cloudflare Turnstile or hCaptcha set up and Fallback on Failure off, a provider's box that couldn't load in someone's browser, because a network or extension blocked it or the provider was down, left an empty space on the sign-in, sign-up or password-reset form, with no message, and the form couldn't be sent. Now the form says The security check couldn't load. Refresh the page or contact your administrator., in the same way it says the CAPTCHA isn't set up. With Fallback on Failure on, nothing changes: the built-in code stands in for the provider's box. See You can't get past the CAPTCHA.

Security

  • Your IP rules now apply when someone signs in to your mobile app with their password, and each time the app renews its sign-in, as they do on the web. Before, someone on a blocked network address, or outside your allow list, still got signed in to the app there. Laramin now checks the address before the password: the account's own rules, then its roles', then the global ones, with the super-admin break-glass as on the web. A refused sign-in gets Access denied from your network address. Please contact your administrator. and no session, and doesn't count as a failed attempt. Someone on an allowed address signs in as before, two-factor code included. See How IP access control works and Someone can't sign in to the mobile app.
  • When your public website has its own Site host, the admin and its sign-in now answer only on your Laramin's own address. Before, signing in, and the whole admin, also worked on the website's address. There they now show Page not found, like any page the website doesn't have. The website keeps working, and when Site host is empty or is your Laramin's own address, nothing changes. Sign in on your Laramin's own address. See Choose what your website's home page shows.

Core

Core 12.8.4

When the CAPTCHA can't work, the sign-in form says it isn't set up instead of showing a code that's always refused.

Fixed

  • With Google reCAPTCHA, Cloudflare Turnstile or hCaptcha chosen, no site key saved for it, and Fallback on Failure off, the sign-in, sign-up and password-reset forms showed Laramin's built-in picture. Only the provider's answer counts while Fallback on Failure is off, so the code people typed from it was refused every time, and nobody could get past the form. Now the forms say plainly that the CAPTCHA isn't set up and that people should contact their administrator, and show no code. An administrator saves the provider's site key, turns Fallback on Failure on, or chooses the built-in CAPTCHA. With Fallback on Failure on, nothing changes: the built-in code is shown and accepted, as in 12.8.3. See You can't get past the CAPTCHA and Set up CAPTCHA.

Articles this release changed

Core

Core 12.8.3

When the CAPTCHA provider's box can't load, the built-in code shown in its place lets people sign in.

Fixed

  • When your CAPTCHA comes from Google reCAPTCHA, Cloudflare Turnstile or hCaptcha and the provider's box can't load, or no site key is saved, the form shows Laramin's built-in picture instead, as long as Fallback on Failure is on. The code people type from that picture is now accepted. Before, Laramin checked it with the provider and refused it every time, so nobody could get past the form. Falling back never skips the CAPTCHA: the built-in code still has to be typed correctly, and only the picture shown to that person counts. With Fallback on Failure off, only the provider's answer counts, as before. See You can't get past the CAPTCHA and Set up CAPTCHA.

Articles this release changed

Core

Core 12.8.2

A new Laramin sends email, keeps people signed in from links, knows its own address and lets the mobile app sign in.

Fixed

  • Notification Manager can send email on a newly installed Laramin. Installing locked away the email details Notification Manager starts with, in a form Laramin couldn't read again, so none of its emails went out. On a Laramin installed before 12.8.2, whoever runs your server runs php artisan app:check-encrypted, which lists any saved details Laramin can't read and changes nothing. For each one, enter the details again on its screen and save. For Notification Manager that's Email Settings, under Notification Providers in Settings: on the SMTP tab, fill in every field, including SMTP Password, and select Save changes. See Notification Manager settings.
  • Laramin's own emails, such as password resets, use the mail server set in your server's settings file. Before, Laramin ignored the mail server's address there, so these emails didn't go out.
  • Following a link from an email or another website keeps you signed in. On a new Laramin, such a link opened the sign-in page and signed you out, and social sign-in couldn't finish. New installs now allow these links. On a Laramin installed before 12.8.2, open Developer Tools › Developer Settings › Session Settings, set Same-Site Cookie to Lax and save, unless your team chose Strict on purpose. See Someone can't sign in with a social account.
  • The web installer saves your site's address, the one you opened it at. Before, links in emails and some images pointed at http://127.0.0.1:8000. Installing from the command line, you can give the address with --url. On a Laramin installed before 12.8.2, whoever runs your server checks APP_URL, ASSET_URL and LOCAL_ASSET_URL in its settings file, then runs php artisan config:clear. See Install with the web installer and Install from the command line.
  • The mobile app can sign in on a newly installed Laramin. Before, every app sign-in failed with "Mobile authentication is not configured.", even with a wrong password. On a Laramin installed before 12.8.2, whoever runs your server runs php artisan auth:mobile-client --check. If it reports a problem, they run php artisan auth:mobile-client to set the sign-in up; running it again changes nothing. See Sign people in from a mobile app.

Social Login

Social Login 2.1.3

A first sign-in with Google or another provider from a network your IP rules refuse no longer creates an account.

Security

  • Your IP rules are now checked before a social sign-in creates or links an account. With 2.1.2, someone signing in with a provider for the first time from a network address your rules refuse was refused, but only after their new account had been created. Now nothing is created: on the website, the admin and the mobile app, a first sign-in is checked against your global IP rules before the account is made, and someone whose account already exists is checked against that account's rules before the provider is linked to it. They see the same message, Access denied from your network address. Please contact your administrator. A first sign-in from an allowed address creates the account as before. See How social sign-in works.
  • In your mobile app's browser sign-in, a refused address is now stopped in the browser, with that message, before the app is handed a code. See Social sign-in from a mobile app.
  • Accounts that 2.1.2 created for refused first sign-ins have no roles. You can find and delete them in Users Accounts › Users. See Things changed after an add-on upgrade.

Social Login

Social Login 2.1.2

Signing in with Google or another provider follows your IP rules, on the website, the admin and the mobile app.

Security

  • Your IP rules now apply to a sign-in with Google or another provider, exactly as to a password sign-in. Before, a social sign-in skipped them, so someone on a blocked network address, or outside your allow list, could still sign in with a provider on the website or admin, and your mobile app was given a session there too. Now, once the provider says who the person is, Laramin checks their address against the rules for that account: its own, then its roles', then the global ones, with the super-admin break-glass as after a password. If they refuse it, the person isn't signed in and isn't asked for a two-factor code. They see Access denied from your network address. Please contact your administrator., the message a password sign-in gets, and your mobile app is refused with the same sentence. Someone on an allowed address signs in as before, two-factor code included. See How IP access control works and How social sign-in works.
  • After you update, someone who used to sign in with a provider from a network your rules refuse can't any more. To let them in, change the rule. See Someone is locked out by an IP rule.

Social Login

Social Login 2.1.1

Signing in with Google or another provider on the web asks for the two-factor code of people who use it.

Changed

  • Needs Laramin 12.7.0 or later. Upgrade Laramin first.

Security

  • On the website and admin, someone who has set up two-factor authentication is asked for their code after signing in with Google or another provider, exactly as after their password. They're signed in only once the code, or a recovery code, is accepted. A device they've trusted skips the code, as after a password. Before, a social sign-in there skipped the code. The mobile app already asked for it. See How social sign-in works.
  • With Require two-factor authentication on, someone who hasn't set it up is taken to Profile › Security after a social sign-in, as after a password. See Set up two-factor authentication.
  • After you update, people who use two-factor authentication need their authenticator app, or a recovery code, to sign in with a provider. Someone who has neither can ask an administrator to reset it. See You can't sign in because you lost your authenticator app.

Core

Core 12.8.1

Scheduled jobs and background work, such as queued emails, run again, even when an add-on sets a schedule Laramin can't read.

Fixed

  • Scheduled jobs and background work run again. With the Blog or AI Manager installed, none of Laramin's scheduled jobs ran: queued emails and notifications waited, scheduled articles weren't published, reminders and backups didn't run. Now, if an add-on asks for a schedule Laramin can't read, Laramin skips only that job, notes it in the server log, and runs everything else. Updating the Blog to 2.4.1 and AI Manager to 2.3.1 fixes the same problem on any version of Laramin.
  • In Developer Tools › Scheduler, a job Laramin skips shows Not scheduled: invalid frequency, and a daily job shows the time it runs, such as Daily at 03:20.

Core

Core 12.8

The mobile app asks for your two-factor code, signs out for good, and can show your workspaces and what you may do.

New

  • The mobile app can list the workspaces you may work in, with each one's time zone and office hours. See Mobile API endpoints.
  • The mobile app can check what you may do in the workspace you're in, so it shows only what you can use. Laramin still checks every request.

Changed

  • When an app asks for a workspace or team the person can't enter, the answer now says so with its own code, so the app can show its workspace picker again. If you've built an app or integration that picks a workspace, handle the new answer. See Authenticate API requests.

Fixed

  • Someone who started signing up in the mobile app but didn't enter the emailed code in time can finish. They sign in with their password, and the app sends them a new code. See Let people sign up from a mobile app.
  • While Laramin is under maintenance, apps get a clear maintenance answer that says when it ends, so they can show a maintenance screen instead of an error. If you've built an app or integration that looks for maintenance, have it look for the new answer. See Turn on maintenance mode and API errors and error codes.
  • Phones on one office network or mobile carrier no longer share one allowance for staying signed in. If your Laramin is behind a load balancer or proxy, ask whoever runs your server to set TRUSTED_PROXIES. See API rate limits.
  • The mobile app no longer signs people out, or tells them their password is wrong, when sign-in is briefly unavailable on the server.
  • Changing the app's key no longer signs everyone out of the mobile app. See Register an API consumer and issue its key.

Security

  • The mobile app asks for the two-factor code of everyone who uses two-factor authentication, after their password or social sign-in. Require two-factor authentication applies to the app too. Update your mobile app before you upgrade: an older app can't finish signing in someone who uses two-factor authentication. After upgrading, whoever runs your server updates the database and ends the app sign-ins that were made without a code, as the upgrade notes describe; those people sign in again once. See Sign people in from a mobile app, Security settings and Set up two-factor authentication.
  • A temporary password, or one you've asked someone to change, doesn't work in the mobile app until they choose their own. Setting a password, a password reset and changing your own password on the web also sign the person out of the mobile app and stop their personal API tokens. Update your mobile app so it takes people to Forgot password when this happens. See Reset or set a user's password and Change your password.
  • Signing out of the mobile app ends that phone's sign-in completely: it can't sign itself back in. Your other phones stay signed in.
  • The mobile sign-in only tells someone who knows the password that an account is deactivated, unverified or without API access.
  • The mobile sign-in gives an app only the access a mobile app needs.
  • The mobile app's older settings list returns only public settings, never stored passwords or keys. If your app reads anything else from it, move it to the public settings before you upgrade. Whoever runs your server should run the check in the upgrade notes. If your mobile API could be reached by people outside your team before this release, they replace the passwords and keys it finds, and change the app's key only after upgrading. See Mobile API endpoints and Core Mobile configuration settings.
  • Every mobile address a module adds gets Laramin's own checks, such as the minimum app version and IP rules.
  • Permissions work the same in the mobile app as in the browser.

Property CRM

Property CRM 5.3

Only people who may assign inquiries can change an inquiry's Assigned To. For Agents and Telecallers, the field is read-only.

New

  • The ? Help link on the dashboard, the timeline, Clients, Properties, Requirements, Inquiries and the Property CRM settings opens the Help Center article for that screen, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Security

  • Changing who has an inquiry needs feature.pcrm.inquiry.assign, in the inquiry form as in the Assign action. Before, anyone who could edit an inquiry, Agents and Telecallers included, could hand it to someone else from the form. Without the permission, Assigned To is read-only, and a new inquiry they add arrives unassigned. See Work through new inquiries and Give people a Property CRM role.
  • Properties, requirements and inquiries can be added, changed and deleted only through Property CRM's own screens, so its rules always apply. A sold property can't be put back on the market, and a fulfilled requirement can't be reopened, by going around them. The row actions, bulk delete and edit forms work as before.

Payment Gateway

Payment Gateway 4.1

On the Payment Gateway screens, the ? Help link now opens the Help Center article for the screen you're on.

New

  • Select ? in the header on Payment Gateways, on Update Supported Currencies, or on a manual payment method's payer fields (Update Gateway Fields), and the Help Center opens at the article for that screen. Before, it opened the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Question Bank

Question Bank 3.6

Across Question Bank, and on My Tests for learners, the ? Help link now opens the Help Center article for that screen.

New

  • For the people who run tests: on Exam Boards, Topics, Sub Topics, Exams, Questions and the question builder, Paper Queue and its review, Mock Tests, and Test Submissions with their analytics, the ? icon in the header opens the Help Center at the article for that screen.
  • For learners: on My Tests and a test's result page, the ? icon opens the article on seeing your tests and results.
  • Before, these screens opened the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Activities

Activities 3.2

On Tasks, Queues and the other Activities screens, the ? Help link now opens the Help Center article for that screen.

New

  • On Tasks, History, Queues, Templates, Calendars and Task Statuses, the ? icon in the header opens the Help Center at the article for the screen you're on, not the Help Center home. On Queues, for example, that's the article on sharing work through a queue. See Open the Help Center.
  • You see the ? icon from Laramin 12.7 on. On an earlier Laramin these screens work as before.

Organization

Organization 3.2

Saving a party's business terms works again, and each business sees and changes only its own roles and parties.

New

  • The ? Help link on Organization's screens opens the Help Center article for that screen, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Fixed

  • Save on a party's Business Profile stores your business terms: owner, team, currency, payment terms and credit. It used to fail with a "not found" message for every party. See Set your business's terms for a party.

Security

  • A party's Roles screen and its Party 360 show only the roles your business gave it. In All Workspaces, each role names its business. You can correct, end or delete a role only from the business that holds it, and End this role ends the role you chose. See Give a party a role, or end one.
  • A party your business doesn't deal with doesn't open from your business, and its details can't be changed from there. The With list on a relationship offers only parties your businesses deal with, and a party's Business Profile lists only that party's terms. See How Organization keeps one record per person and company.
  • Client lists in other add-ons, such as Property CRM's Clients, show and filter by only the roles a person holds with your business. A seller at another business no longer shows as a seller on your client. See Deal roles: buyer, seller, tenant, landlord and more.

Monetization

Monetization 3.1

Across Monetization, from plans and pricing to subscriptions, the ? Help link now opens the Help Center article for that screen.

New

  • The ? Help link on Monetization's screens opens the Help Center article for that screen, not the Help Center home: plans, pricing, features, offerings, promotions, regions, subscriptions, renewals and product credits. See Open the Help Center.
  • You see the new link from Laramin 12.7 on. On an earlier Laramin, these screens work as before.

Blog

Blog 2.4.1

With the Blog installed, scheduled articles are published again and all of Laramin's scheduled jobs and background work run.

Fixed

  • Scheduled jobs run again. The Blog's daily clean-up of old view records was set up in a way Laramin couldn't read, and that stopped all of Laramin's scheduled jobs, not only the Blog's: scheduled articles weren't published or archived on time, and queued emails and other background work waited. Articles that were due go live within a minute of updating. The clean-up still runs every day at 03:20. Update the Blog to 2.4.1 on any Laramin version. See An article doesn't show on your website.

Articles this release changed

Blog

Blog 2.4

In the Blog, the ? Help link now opens the Help Center article for the screen you're on, from Articles to Blog URLs.

New

  • Select ? in the header on Articles, an article's Version history, Categories, Tags, Authors or the Blog URLs settings, and the Help Center opens at the article for that screen instead of its home page. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

AI Manager

AI Manager 2.3.1

With AI Manager installed, the daily model check and all of Laramin's scheduled jobs and background work run again.

Fixed

  • Scheduled jobs run again. AI Manager's daily model check was set up in a way Laramin couldn't read, and that stopped all of Laramin's scheduled jobs, not only AI Manager's: the hourly cost and failover alerts didn't run, and queued emails and other background work waited. The model check still runs every day at 04:10. Update AI Manager to 2.3.1 on any Laramin version. See How AI Manager works.

Articles this release changed

AI Manager

AI Manager 2.3

Across AI Manager, from Overview to Routing Settings, the ? Help link now opens the Help Center article for that screen.

New

  • The ? icon in the header opens the Help Center at the article for the AI Manager screen you're on: Overview, AI Providers and a provider's Models & rates, Usage & Cost, and Routing Settings. Before, it opened the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Webhook Engine

Webhook Engine 2.3

On Destinations, Delivery Logs and the Test Console, the ? Help link now opens the Help Center article for that screen.

New

  • On Destinations, Delivery Logs and a destination's Test Console, the ? icon in the header opens the Help Center at the article for that screen, instead of the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Billing

Billing 2.1

Press G then O to open Orders, and the ? Help link on Billing's screens opens the article for the screen you're on.

New

  • Press G then O to open Orders from any screen. The shortcut is offered only to people who may open Orders. See How Billing keeps your money records.
  • The ? Help link on Billing's screens, from Billing Accounts and Orders to Payments and Tax Rules, opens the Help Center article for that screen, not the Help Center home. You see the new link from Laramin 12.7 on. See Open the Help Center.

Changed

  • Needs Laramin 12.2 or later. Upgrade Laramin first.

Articles this release changed

Core Mobile

Core Mobile 2.1

The app offers every language your Laramin publishes. Upgrading? Run one server command so the app stops offering English only.

New

  • The ? Help link on Core Mobile's screens opens the Help Center article for that screen, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

  • Supported Languages and Active Languages can be left empty, which offers every language your Laramin publishes, and that's the new default. You can still choose some of them, but only published languages. See Core Mobile configuration settings.

  • If your Laramin had Core Mobile before this version, both lists still hold only English. After you upgrade, ask whoever runs your server to run these on the server:

    1. php artisan coremobile:reset-seeded-languages shows what would change, and changes nothing.
    2. php artisan coremobile:reset-seeded-languages --apply clears each list that holds English alone. Lists you chose yourself aren't touched.

    Skip the second step if your app should offer English only.

Fixed

  • The app's language screen offers the languages your Laramin publishes. Before, it offered English only. A default or fallback language that isn't published any more is replaced by your Laramin's default language.
  • Saving Localization refuses a language your Laramin doesn't publish.
  • Saving Release Control refuses a Minimum Version higher than the platform's latest app version, and the field now says it's the mobile app's version, not your Laramin's. Typing your Laramin's version there sent every app an update screen. See How Core Mobile works.
  • The maintenance window's Start Time and End Time reach the app with your Laramin's time zone. A phone in another time zone used to start and end maintenance at the wrong time.

Custom Fields

Custom Fields 2.1

On Custom Fields and the field builder, the ? Help link now opens the Help Center article on adding a custom field.

New

  • On the Custom Fields list and on Manage fields, where you build the fields for a form, the ? icon in the header opens the Help Center article on adding a custom field, instead of the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Social Login

Social Login 2.1

On the Social Login providers screen, the ? Help link now opens the Help Center article on setting up a sign-in provider.

New

  • In Platform Administration › Social Login, the ? icon in the header opens the Help Center at the article on setting up a sign-in provider, instead of the Help Center home. See Open the Help Center.
  • You see the ? icon from Laramin 12.7 on. On an earlier Laramin the screen works as before.

Notification Manager

Notification Manager 1.5

Using WhatsApp or Msg91? Save the Meta App Secret and paste Msg91's new report address, or delivery reports are refused.

New

  • Add-ons can attach files to the emails they send, such as a PDF. Only email carries them, through SMTP or AWS SES: up to 10 files and 7 MB per message, of document, spreadsheet, image and text types. A file that is really a program is refused. See How Notification Manager sends notifications.
  • WhatsApp Settings has a new field, App Secret. See Notification Manager settings.
  • The ? Help link on Notification Manager's screens opens the Help Center article for that screen, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.
  • After you upgrade, do these steps for the providers you use. See Check what was sent.
    1. WhatsApp: in your Meta app, open App settings › Basic and copy the App Secret. Paste it in WhatsApp Settings › App Secret and save. Until you do, every delivery report from Meta is refused, and Webhook Center shows a warning.
    2. Msg91: open Notification Manager › Settings › Webhook Center, copy the Msg91 DLR Webhook URL, and paste it in your Msg91 account again. The address now ends in a secret for your Laramin, and the old address is refused. In Msg91's Webhook (New), you can send the secret in an X-Webhook-Token header instead.
    3. Twilio: check that the Auth Token is saved in SMS Settings. Without it, Twilio's delivery reports are refused, and Webhook Center shows a warning.
    4. Meta verify token: your Laramin now has its own, shown on Webhook Center. You only need it if you subscribe the webhook in Meta again.
    5. Server: ask whoever runs your server to run php artisan nm:purge-attachments once a day. It deletes copies of email attachments left behind when a send was stopped, after 48 hours.

Fixed

  • A notification sent to a person in Laramin, as Property CRM sends its team alerts, reaches their email address, phone or device. Before, only the in-app copy arrived, and email, SMS, WhatsApp and push failed. See A notification wasn't sent or didn't arrive.

Security

  • Delivery reports from Twilio, Meta and Msg91 are checked before they change a delivery log. A report that fails the check is refused and changes nothing. Before, anyone who had the address could mark a message delivered, read or failed. Sending isn't affected. See Connect an email, SMS, WhatsApp or push provider.
  • The verify token for Meta is unique to your Laramin, instead of the same for every installation.

Demo Mode

Demo Mode 1.4

On Demo Mode's settings, the ? Help link now opens the Help Center article on setting up Demo Mode.

New

Language

Language 1.4

On the Languages screens, the ? Help link now opens the Help Center article for the job at hand, such as translating screen text.

New

  • The ? icon in the header opens the Help Center at the article for the screen you're on: Languages, Translation Strings, the screen where you translate a record's content, and Language Settings. Before, it opened the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Product Catalog

Product Catalog 1.4

Across the Catalog, from Products to the variant matrix, the ? Help link now opens the Help Center article for that screen.

New

  • On Products, Categories, Brands and Collections, and on a product's images and files, bundle items and variant matrix, the ? icon in the header opens the Help Center at the article for what you're doing, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Roles & Permissions

Roles & Permissions 1.4

You can give someone a role only if you hold every permission it carries there. Roles above yours are listed but can't be chosen.

New

  • The ? Help link on Roles, the role permission editor, Access Assignments and a role's list of who holds it opens the Help Center article for that screen, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Security

  • Giving someone a role is limited the way granting a permission directly already was: you can give a role only if you hold every permission it carries in that scope. Before, anyone with Edit Assignment could give any role, Administrator included, to anyone, themselves included. See How roles and permissions work.
  • Roles you can't give are listed but can't be chosen. If the person already holds one of them in that scope, it stays when you save. See Give someone a role and You can't give someone a role or permission.
  • Super admins aren't limited.

Activity Log

Activity Log 1.3

In the Activity Log, the ? Help link now opens the Help Center article for the list you're on, not the Help Center home.

New

  • On User Activities, the ? icon in the header takes you to the Help Center article on finding out who did what. On Login Activities and Visitor Activities, it opens the one on reviewing sign-ins and open sessions. See Open the Help Center.
  • You see the ? icon from Laramin 12.7 on. On an earlier Laramin these lists work as before.

Support Center

Support Center 1.3

In Support Center, the ? Help link now opens the Help Center article for the screen you're on, from Overview to a ticket.

New

  • On Overview, Tickets, a ticket's page, New ticket and the Connection settings, the ? icon in the header opens the Help Center at the article for that screen, instead of its home page. On a ticket, that's the article on replying to or closing a ticket. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Backup

Backup 1.2

A restore puts back everything the backup holds, encrypted archives included, or stops and says why before it changes anything.

New

  • A new status, Partial: the backup is safe on your Laramin's server, but its copy to cloud storage or another server failed, or was skipped because the destination's details are missing. You can download and restore a Partial backup like a Completed one. See Schedule backups to cloud storage.
  • A Problem column on Backups History says why a backup failed, or which copy failed and why. See A backup or restore is stuck or failed.
  • The ? Help link on Backups History, Restore Logs, Schedules and Storage Destinations opens the Help Center article for that screen, not the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Fixed

  • A restore puts back what the archive holds. Before, it could show Completed after changing nothing: encrypted archives weren't opened, Full and Files restores put back no uploaded files, and a database copied in CLI mode was skipped. See Restore a backup.
  • A restore unpacks and checks the archive before it changes anything. If something is wrong, it stops with Failed and the process log says Nothing was changed. A dry run makes the same checks.
  • An encrypted archive is opened with the Archive Password in Backup settings. If that password doesn't open it, the restore says so. See Backup settings.
  • Maximum Age set to 0 keeps backups of any age, as its label says. It used to delete every backup beyond the Always Keep count. The size limit no longer deletes the most recent backups you always keep.
  • A copy to a destination that failed shows on screen. The backup used to show Completed, and Destinations listed the failed copy. See Make a backup now and download it.
  • Every active schedule runs. Two schedules with the same scope, such as a daily and a weekly Full backup, used to run as one.
  • A backup records the archive it made. When a backup failed, it could take an older archive from the folder as its own.

SEO

SEO 1.2

On SEO Settings and Redirects, the ? Help link now opens the Help Center article for that screen, not the Help Center home.

New

  • On SEO Settings, the ? icon in the header opens the Help Center article on setting up your SEO defaults. On Redirects, it opens the one on adding a redirect. See Open the Help Center.
  • You see the ? icon from Laramin 12.7 on. On an earlier Laramin these screens work as before.

Headless CMS

Headless CMS 1.1

Across Headless CMS, from Content spaces to the API explorer, the ? Help link now opens the Help Center article for that screen.

New

  • On Content spaces, Content schemas, Assignments, Content and its entries, Channels, API access, API explorer and Settings, the ? icon in the header opens the Help Center at the article for that screen. Before, it opened the Help Center home. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Razorpay

Razorpay 1.1

The add-on console, the add-on's details and What's new call the add-on Razorpay instead of PgRazorpay.

New

  • Addons › Addon Management, the add-on's details and What's new call the add-on Razorpay. They used to show PgRazorpay. This needs Laramin 12.4 or later. On an earlier Laramin, it's still listed as PgRazorpay, and everything else works as before. See Set up Razorpay.

Articles this release changed

Stub Generator

Stub Generator 1.1

On the Scaffolder, the ? Help link now opens the Help Center article on generating a resource, not the Help Center home.

New

  • In Platform Administration › Scaffolder, the ? icon in the header opens the Help Center article on generating a resource with the Scaffolder. See Open the Help Center.

Changed

  • Needs Laramin 12.7 or later. Upgrade Laramin first.

Core

Core 12.7

Open the Help Center from any screen at the right article, and sign in to see the docs for your own modules.

New

  • Open the Help Center from the ? icon in the header, or from Help Center in the account menu. It opens in a new tab at the article for the screen you're on. See Open the Help Center.
  • Sign in to the Help Center with your Laramin account to see the docs for the modules your Laramin has, including private docs for the people you allow. The Help Center shows the articles for your role first.
  • A new permission, Open the Help Center, decides who sees the Help link. Every role you have when you install 12.7 gets it. Roles you create later don't, so you add it when you want to.
  • Super admins connect your Laramin to the Help Center in Settings › General › Help Center. See Connect your installation to the Help Center.
  • Import Countries, States and Cities from a CSV file. See Import records from a CSV file.
  • Reset a user's two-factor authentication when they lose their authenticator app. See Reset a user's two-factor authentication.

Changed

  • The search box in the header reads Search…. It finds what your modules offer, not pages, users or settings.
  • If you belong to several workspaces and haven't chosen one, you sign in to the default workspace instead of being asked, when your Laramin allows it.

Fixed

  • Maintenance mode no longer locks out the people who can end it. The sign-in page stays open, super admins can still get in, and bypass addresses accept ranges. See Turn on maintenance mode.
  • Blocked IPs can block a range of addresses. The IP Range To box, which did nothing, is gone. See Block an IP address.
  • Automatic IP blocks lift when they expire.
  • Recent alerts shows alerts again.
  • Add-ons: Reset on a stuck add-on works, both ways of upgrading an add-on run the same checks, a system upgrade updates every module's data, and free add-ons are no longer marked as waiting for a license. See Run a system upgrade.
  • Every shortcut in the keyboard shortcuts list works.
  • Esc ends editing a cell in a list without saving, and edits in a cell save on every list.
  • The Import button only shows for people who may import.

Security

  • Require two-factor authentication now works. A team member who hasn't set up two-factor is asked to do so before they continue. Check who hasn't set it up before you turn it on. See Security settings.
  • A new web install no longer leaves the demo administrator account active. See Install Laramin with the web installer.
  • Paid add-ons need a real license key to activate.
  • The dashboard's people counts only show for people who may see the Users list.
  • Changes to security settings are written to the security log, and Clear log keeps the security log.

Core

Core 12.6

A multiple-choice list can show a second line under each option, such as a person's email under their name.

New

  • A multiple-choice list can show a second line under each option, such as a person's email under their name. Search finds an option by either line, and an option you've chosen shows only its name.

Core

Core 12.5.1

Amount filters keep "at least" and "at most", and you type amounts in the units the list shows, such as Lakh or Crore.

Fixed

  • An amount filter, such as a budget, can be set to at least or at most and keeps that choice. It used to jump back to between, and typing one side of a between range made the other box disappear.
  • You type an amount filter in the units the list shows. With Lakh selected, "40" means ₹40,00,000, and the full amount is spelled out under the box. You can switch a box to Crore. The filter chip shows the amount the way the list does, for example "₹ 40L–1Cr", and the match count updates as you type. See Filter a list.
  • Choosing an option from a dropdown inside a filter no longer closes the filter before you apply it.

Articles this release changed

Core

Core 12.5

Lists filter from a bar of plain chips above the table, and a filtered list keeps its filter in the page address.

New

  • Lists filter from a bar of chips above the table. The filters you use every day sit on the bar, ready to fill in, and any other filter is one + Add filter away (or press F). Each chip says in words what it filters on, shows how many records it will match before you apply it, and offers Undo when you remove it. See Filter a list.
  • When nothing matches, the bar suggests which filter to remove. A filter the list can't run says so on the bar, instead of the list quietly showing nothing.
  • A filtered list keeps its filter in the page address, so you can bookmark it or share it. If a filter is too long for the address, the list says so and suggests you save it as a view.
  • Build an "and / or" filter as a plain sentence, such as "Show inquiries that match all of these", in a panel beside the list, so the results stay in view.
  • Every kind of filter has an editor that suits it: a checklist for a short set of choices, a search for a long one, a from-to range for amounts, and "today", "this month" or a date range for dates. Is not works on choices too.
  • A list's search box says what it searches, for example "Search title, owner, phone…". You can also filter on something the list doesn't show as a column, such as a phone number.
  • Lists can find people by name, client code or phone number separately, and find a phone number however it was typed.

Changed

  • A column's own filter opens from a funnel icon in its heading, instead of a row of boxes under the headings. If you chose the row of boxes in the view settings, you keep it. See Customize the columns in a list.
  • The text in What's new and in the filters follows the text size chosen for your Laramin, and no label is smaller than 11 pixels.

Fixed

  • In Arabic, What's new shows the number in every count. Some counts spelled out the word for "one" and left the number out.

Core

Core 12.4

What's new replaces Version history: one feed of every update to your Laramin and its add-ons, newest first.

New

  • What's new replaces Version history. It opens on one feed of every update to the platform and the add-ons you use, newest first and grouped by month, with search, filters and a summary of recent changes. Each add-on also has its own history, and after an upgrade the versions just installed are marked New for you. See Check what's new in each version.
  • Add-ons are named the way your sidebar names them, in your language, in Addon Management, an add-on's details, What's new and the panel shown before an upgrade.
  • Release notes read as a headline and its detail, without links to code, tracker numbers or developer labels.

Changed

  • Release notes are grouped as New, Improved, Fixed, Being retired, Removed and Security.
  • What's new opens faster: it loads the first page of updates instead of every version of every add-on.

Fixed

  • Release notes are shown in full. About 300 notes that stopped after their first line now read to the end, and a release's breaking changes are listed again, under "Changes in how things work".

Articles this release changed

Property CRM

Property CRM 5.2.1

Type the Requirements budget filter in lakh and crore, as the Budget column shows it: "40" means ₹40 lakh.

Fixed

  • On Requirements, you type the budget filter in lakh and crore, as the Budget column shows amounts. "40" means ₹40 lakh, not forty rupees, and the full amount is spelled out under the box. This needs Laramin 12.5.1 or later. On 12.5.0, the filter works as before. See Filter a list.

Articles this release changed

Organization

Organization 3.1

Search boxes that look people up find them by phone number, email or city, as well as by name and code.

New

  • Search boxes in other modules that look people up from Organization find a person by any of their phone numbers, however it was typed, by email address and by the city they live in, as well as by name and code.
  • A list's Mobile filter, in a module that offers one, matches the phone number and nothing else.

Changed

  • Needs Laramin 12.5.0 or later. Upgrade Laramin first.

Support Center

Support Center 1.2

Copy others lists people by name, with their email under it, and a ticket draft opens only for the person who wrote it.

New

  • Copy others lists people by name, with their email under it, on a new ticket, on replies and in Always copy. A person you choose shows by name, and the search finds people by name or email. The email address is still what's sent. See Raise a ticket and Reply to or close a ticket.

Changed

  • Needs Laramin 12.6.0 or later. Upgrade Laramin first.

Fixed

  • Copy others no longer offers the person the ticket belongs to. The desk already emails them about every answer. That's you on a new ticket, and whoever opened the ticket on a reply. They aren't copied even when Always copy names them or their address is typed in. See Connect your Laramin to Brine Webs support.
  • A ticket draft one person started no longer opens for the next person on the same computer. Drafts, and which tickets you've seen, are kept for each account. Drafts kept before this update are cleared once, because there's no way to tell whose they were. See See which tickets need your reply.

Core

Core 12.3.4

The horizontal menu keeps every item that fits, instead of folding down to one item and a "More" button.

Fixed

  • In the layouts with a horizontal menu, the menu keeps every item that fits. After you moved between screens, it could fold down to one item and More +7, however wide the window was.

Core

Core 12.3.3

Someone whose password an administrator set goes straight to the screen where they choose their own.

Fixed

  • When an administrator sets someone's password, that person is taken straight to the screen where they choose their own. They used to land on a half-loaded screen that showed the same "choose a new password" message on every click, with no way to the form. Add-on pages also ignored the requirement, and now wait until a new password is chosen.

Core

Core 12.3.2

A fresh install opens the web installer before any database is set up, instead of showing a server error.

Fixed

  • A new installation opens the web installer before any database is configured. Every page, the installer included, used to show a server error until the database details were typed into the environment file by hand.

Core

Core 12.3.1

Addon Management no longer reports a successful add-on upgrade as failed.

Fixed

  • Addon Management no longer says "Upgrade failed" after an add-on upgrade that worked. The upgrade always finished, database changes included, but the refresh at the end failed. The Refresh button and uploading an add-on's ZIP file failed the same way, and now work. See Upgrade an add-on.

Articles this release changed

Core

Core 12.3

"Discard changes?" is asked only about the screen you're leaving, not about forms left open in the background.

New

  • An add-on can add an icon link with a count to the header, next to the Website link. It's there only while the add-on is enabled and only for people who may open it. It opens inside your Laramin, and no page waits for its count to load.
  • An add-on's link in the account menu can have its own icon.

Fixed

  • Discard changes? is asked only about the screen you're leaving. A form left open in the background used to make every move, anywhere in your Laramin, ask about changes you couldn't see.
  • A screen can use your microphone and your location when it asks for them, for example to record a voice note or to center a map on where you are. The browser used to refuse both without asking. Content from other sites embedded in a page, and your public website, still can't use them.
  • An add-on's header link now appears, and opens inside your Laramin instead of reloading the page.
  • The sidebar highlights the item that best matches the page you're on, not the first one that partly matches.
  • A block editor cleared at the same moment it's unlocked stays cleared.

Activity Log

Activity Log 1.2.1

Activity Log records actions again when it was installed from Addons. Before, it recorded nothing.

Fixed

  • Installing Activity Log from Addons › Addon Management sets it up correctly, so actions are recorded. Before, an install from there recorded nothing. If your Laramin is affected, upgrading fixes it, and actions are recorded from then on. Actions from before the upgrade can't be brought back. See Nothing appears in the Activity Log.

Articles this release changed

Core

Core 12.2

Choose which experiences each user may enter on the Users form. The Administrator role no longer grants them.

New

  • Choose which experiences each user may enter, on the Access step of the Users form. See Choose which experiences a user can enter.
  • Entering an experience, from the sign-in chooser or the header's View switch, opens that experience's home page.
  • Choose which module page your public website opens on, in Configurations › Security › Public website. If that page's module is disabled, the website falls back to the default page and the panel tells you. See Choose what your website's home page shows.
  • Your website's pages can show content published in a content space you choose, with the Content space setting.
  • A plain, branded default page for your website's main address, with the product's name and version. It loads no scripts and sets no cookies, and you can edit its search description.
  • An App icon in System settings. Browser tabs, phone home screens and the install prompt show your product's name, colors and icon, or a generated monogram until you upload one. See System and company settings.
  • Schedule follow-up in a list row's menu, when an add-on provides follow-ups and you may schedule them.
  • Forms can have file upload fields with their own formats and size limits, alt text for uploaded images, placeholder text, and email and web-address fields that check for a real address. A single-language text field can offer Ctrl+G phonetic typing, and a drawer form can have one language switcher for the whole form.
  • File sizes in File upload settings are typed as a number with a KB, MB or GB unit beside it.
  • Lists: reorder rows from the keyboard with Move up and Move down or Alt+Arrow keys, open a record by clicking its row or pressing Enter, and on a phone, press and hold to select a card. Some columns hide by default on smaller screens.
  • Saved views that an add-on provides show their name in your language. See How saved views work.
  • Issue, rotate and revoke an API consumer's key from the admin. A new key is shown once.
  • An add-on can refuse to be uninstalled and explain why, with choices. An add-on whose data is archived on uninstall has its tables exported before anything is removed. See Disable or delete an add-on.
  • A message can offer two actions, and show how long you have to use one, such as Undo.
  • On a phone, the page header fits on one row.

Changed

  • The Administrator role no longer lets people enter experiences. Which experiences a person may enter is chosen per user. Everyone who could enter one through the role keeps that access in each workspace they belong to, so nobody loses access.
  • The coming-soon page uses the same design as the default page.

Removed

  • The placeholder app icons. If your Laramin was installed by copying files to the server, ask whoever looks after the server to delete the old favicon and icon files listed in the developer changelog, or browsers keep showing the old blank icon.

Fixed

  • Opening a notification in the header panel marks it as read. See Read your notifications.
  • API Consumers and Public website are in the sidebar, under Developer Tools and Security. You used to have to type their address.
  • The header's Website link appears.
  • The cookie banner can be dismissed, and follows the visitor's answer.
  • Browser tabs show your icon instead of a blank one.
  • The admin's main address, and the logo in the header, open the page you land on after signing in, instead of "Screen not available".
  • Saved-view counts no longer read 0 on lists inside a record.
  • In Arabic, counts above one use the right plural form.
  • Installing, enabling or upgrading an add-on no longer rewrites the translations of Core and the other add-ons, or loses Core's menu labels.
  • A failed add-on install no longer leaves the add-on enabled with its menus.
  • A role that may create or edit records, but not see their list, can open the form.
  • Saving a drawer shows one loading indicator, not two.

Security

  • Self-registration from the website is off by default, and Allow public registration in Security settings really controls it. If your Laramin had turned it on, it stays on. Turn it on if you rely on open sign-up.
  • The web API's list of users needs the permission to list users, feature.core.user.list. Before, any signed-in session could read every user's name and email. Give that permission to any API client that reads the list.
  • Super admin accounts are hidden from anyone who isn't a super admin: in the Users list, its counts, search and export, and in the web API. See Super admin vs Administrator.
  • Responses no longer reveal the server's PHP version.
  • An App icon upload that claims an oversized image is refused before it's processed.

Payment Gateway

Payment Gateway 4.0.1

The payer fields screen of a manual payment method opens again, so you can reorder and remove its fields.

Fixed

  • Update Gateway Fields opens for a manual payment method that asks the payer for any field, so you can review, reorder and remove its fields. The screen used to fail as soon as one field was chosen. See Add a manual payment method.

Articles this release changed

Question Bank

Question Bank 3.5.2

Paper Queue imports, review comments and requeues record the person who did them, even when they finish in the background.

Fixed

  • Importing questions from a page, adding review comments and ReQueue the Paper record you as the person who did them, also when the work finishes in the background. The same goes for the Question Added to Exam notification. See Import questions from an exam paper.

Security

  • An unused API address is gone. Any API token could call it without a permission check, and it returned the caller's own user account. Nothing in Question Bank used it.

Articles this release changed

Activities

Activities 3.1

Work through a task in one view: its checklist, comments with @mentions, files, reminders, time, watchers and history.

New

  • Open a task over the list you're on, or on its own page, and work through it in one place: its checklist, comments, history, reminders, time, watchers, dependencies and files. See Work through a task: checklist, comments and files.
  • Bring people into a comment by typing @. Only people who can see the task are notified. When you edit a comment, only the people you added are notified.
  • A task's Activity tab shows, in one stream, what people did and what changed.
  • Attach files to a task by dragging, pasting or choosing them. Rename, remove and download them from the task. A removed file is taken off the task but kept in storage.
  • Claim and release queued work from the task itself. See Share work through a queue and claim a task.
  • Create, edit and delete tasks on the Tasks screen. A deleted task can be restored, with its time, checklist progress and history. See Create a task and set a reminder.
  • A new task starts as Open, Task and Low. You can change them before you save.
  • A task's description can be formatted, up to 5,000 characters of text.
  • Each task has a details page, grouped into what it is, who it's about, who's doing it and when it's due.
  • Keyboard shortcuts show beside the controls they work. Laramin asks before it throws away a comment you haven't posted.
  • Find a task by its number or title from the command palette. See Tasks, queues and activity history explained.

Changed

  • Needs Laramin 12.1.0 or later. Upgrade Laramin first.
  • Once a task has checklist items, its Progress follows the checklist, and you can't type a percentage.

Fixed

  • People who may work only on their own tasks can open and work on them.
  • A task can't be completed while a task it waits on is unfinished.
  • Moving a due date moves the reminders set Before due with it.
  • A task created on the Tasks screen gets the default reminders your server sets, if it sets any. It used to get none. See Create a task and set a reminder.
  • A business calendar reads its opening hours in its own time zone, or in the system time zone if it has none, not in the time zone of whoever is signed in. A new calendar starts in your workspace's time zone, and a task number takes its year from your Laramin's clock. See Tasks, queues and activity history explained.
  • Time and watchers added to a task are saved.
  • If someone else changed a task after you opened it, your save no longer overwrites their change. You're asked to reload first.
  • The Comments tab shows in every language. It was blank.
  • Complete, Reopen, Assign, Assign selected and Reschedule selected on the Tasks list do what they say. They used to report success and change nothing. You can also complete several selected tasks at once.
  • Assigning a task changes only the person, team or queue you choose. It used to clear the team and show nobody assigned.
  • A task given to a person from another record shows that person instead of Unassigned.
  • A link to a task from another module opens the task's page.
  • A task's type shows its name, not an internal code.
  • The progress you type on the new task form is kept.
  • Enter in the checklist adds the item, a tick shows who ticked it straight away, and you pick a dependency by its task number.
  • A task's dependencies show each task's title in full.

Blog

Blog 2.3.2

Article views and trending articles count each read on your Laramin's own calendar day, not the server's UTC day.

Changed

  • Needs Laramin 12.1.0 or later. Upgrade Laramin first.

Fixed

  • Article views, the trending articles your website shows, and the clean-up of old view records follow your Laramin's calendar day instead of the server's UTC day. A read late at night is counted on the day it happened. See Blog public API reference.
  • Before you restore an earlier version of an article, the confirmation is shown as a warning, because the restore replaces the current article.

Articles this release changed

AI Manager

AI Manager 2.2.2

A provider's daily spend limit resets at midnight on your Laramin's own calendar day, not at midnight UTC.

Changed

  • Needs Laramin 12.1.0 or later. Upgrade Laramin first.

Fixed

  • A provider's Daily spend limit (USD) resets at midnight on your Laramin's calendar day. It used to reset at midnight UTC, which is 5:30 a.m. in India. See Set spending limits and alerts.
  • The Daily spend chart and the AI spend well above its usual level alert count each call on your Laramin's day, so early-morning calls no longer land on the day before. See Track AI usage and cost.

Webhook Engine

Webhook Engine 2.2

Sign the timestamp protects deliveries against replay. It's on for new destinations, and off for existing ones until you switch it on.

New

  • Sign the timestamp, a setting on each destination. When it's on, the signature covers the delivery's timestamp as well as its payload, and deliveries say they use signature version 2. When it's off, deliveries are signed exactly as before. See Add a webhook destination.
  • With version 2, each attempt is signed when it's sent, so a delivery that was held back or retried carries a fresh timestamp and isn't mistaken for a replay. See Verify webhook signatures and handle retries.
  • The Test Console signs tests the way the destination does, and shows which way beside the destination's status. See Test a webhook destination.

Fixed

  • A failed attempt counts once. It used to be logged twice and counted twice, so a destination was suspended after 10 failed attempts instead of 20. See Deliveries fail or a destination is suspended.
  • A delivery to a destination deleted after it was queued no longer ends as a failed job. A destination in the trash is skipped, and one deleted for good is dropped.
  • Deliveries carry the installed Webhook Engine version in their User-Agent header. It always said 1.0.0. See Webhook payloads, headers and events.

Security

  • Deliveries can be protected against replay. Before, the timestamp wasn't signed, so a captured delivery passed the check every time it was resent. With Sign the timestamp on, a receiver can refuse a delivery whose timestamp is too old.
  • Sign the timestamp is on for every destination you create from now on, and off for every destination you already had, so no receiver starts failing when you upgrade. To protect an existing destination, have its receiver updated to accept version 2, then switch the setting on.
  • An unused API address is gone. Any API token could call it without a permission check, and it returned the caller's own user account. Nothing used it.

Core Mobile

Core Mobile 2.0.6

The Items, Widgets and Slides screens show the menu, dashboard or flow you opened them from, not the one you opened first.

Changed

  • Needs Laramin 12.2.0 or later. Upgrade Laramin first.

Fixed

  • The Items, Widgets and Slides screens show the menu, dashboard or onboarding flow you opened them from. If you opened a second one, they showed the first one's name and edit rights, and the slides' phone preview kept the first flow's slides. See Set up the app's menus and home dashboard and Build an onboarding flow.
  • If a menu, dashboard or flow's details fail to load, you can't edit its items. Before, the edit controls of the one you opened last were shown.
  • The item, widget and slide forms open at the drawer width you choose. A fixed width used to override it.

Custom Fields

Custom Fields 2.0.4

An entity's field list stays as you left it when you go to another screen and come back, instead of reloading.

Changed

  • Needs Laramin 12.2.0 or later. Upgrade Laramin first.

Fixed

  • The field list you open with Manage fields stays as you left it when you go to another screen and come back. It used to reload from scratch. See Add a custom field.
  • The custom field form opens at the standard drawer width, and keeps the width you choose. A fixed width used to override it.

Articles this release changed

Social Login

Social Login 2.0.2

A first social sign-in creates an account only when sign-up is turned on. Both sign-up switches start off.

Changed

  • Needs Laramin 12.2.0 or later. Upgrade Laramin first.

Fixed

  • An account created by a first social sign-in from your mobile app can use the app straight away. It used to be created and then refused. See Social sign-in from a mobile app.

Security

  • A first social sign-in no longer creates an account while sign-up is off. From the website or admin, Allow public registration decides. From your mobile app, Allow mobile app sign-up decides. Each switch covers only its own place. See How social sign-in works.
  • Both switches are off to start with, so after you upgrade, new visitors can't sign up with a social account. If they should, turn on the switch you need in Security settings. People who already have an account can still sign in, whatever the switches say.
  • A refused sign-up says that sign-up is closed. See Someone can't sign in with a social account.

Notification Manager

Notification Manager 1.4.2

Notification tab counts match what each tab lists, and an event with no template no longer shows its internal key.

Changed

  • Needs Laramin 12.2.0 or later. Upgrade Laramin first.

Fixed

  • The channel tabs in your notifications count only the messages they list. A message that failed to send was counted but not listed, so a tab could show 1 over an empty list. See Read your notifications.
  • When an event happens that has no template yet, the person no longer sees its internal key. The stand-in message names the event in a plain sentence, and the module's own template replaces it later. A template you've edited is never replaced. See How Notification Manager sends notifications.
  • Stand-in templates written before this release keep their old text, "A system event was triggered: …", and aren't replaced. Find them and write their message yourself. See Edit a message template and send a test.
  • The dashboard's 7-Day Dispatch Trend counts each day in your workspace's time zone, not in UTC. See Check what was sent.
  • The template builder no longer reloads, and shows an error in place of your template, when you go to another screen while it stays open.

Language

Language 1.3.2

The translation editors stay put when you leave them, and the content translation screen names what you're translating.

Changed

  • Needs Laramin 12.2.0 or later. Upgrade Laramin first.

Fixed

  • The Translation Strings editor, and the screen for translating a record's content, no longer reload in the background after you leave them. Opening one on another language or record still loads it. See Translate screen text.
  • The breadcrumb on the screen for translating a record's content names what you're translating.

Articles this release changed

Product Catalog

Product Catalog 1.3.2

Generate on the variant matrix creates your variants, and the Download Product Asset permission now works.

Fixed

  • Generate variants on the variant matrix creates the combinations you chose. Before, you could preview variants but never create them. See Create variants with the variant matrix.
  • Download Product Asset (feature.pcat.media.download) now works, so people who have it can download digital assets through a download link. Before, only super admins could. Check which roles have it, because it now takes effect. See Add images and files to a product.

Roles & Permissions

Roles & Permissions 1.3

Edit a role's permissions in one grid, review every change before you save, and see who changed what in History.

New

  • Edit a role's permissions in one grid, a row for each resource. Pick a Level for a row, or set each action to Not granted, Own records only or All records. Change a whole column or module at once, search, and filter by module. Risky permissions are marked, and you check every change in Review and save before it's saved. See Create a role and assign permissions.
  • Permissions you don't hold yourself are locked, so you can't grant them. See You can't give someone a role or permission.
  • Compare a role with another role with Compare with…, or copy another role's permissions in with Copy from role…. Nothing is saved until you review and save.
  • The History tab shows who granted or revoked which permission, and when. It needs the Activity Log module. Changes made before Laramin 12.1.0 weren't recorded. See Change or delete a role.
  • The role editor works on tablets and phones. On a phone you edit one resource at a time.

Changed

  • Needs Laramin 12.2.0 or later. Upgrade Laramin first.

Fixed

  • The permission editor, a role's assignees screen and a user's assignments screen keep their state when you go to another screen and come back.
  • When the user search on the assignment screen fails, it says so, instead of "No matching users".

Security

  • Super admin accounts are hidden from anyone who isn't a super admin: in the user search on the assignment screen and in the list of who holds a role. A super admin still sees everyone. See Give someone a role.

Backup

Backup 1.1.3

An unused API address that any API token could call is gone. Nothing changes in how you use Backup.

Security

  • An unused API address is gone. Any API token could call it without a permission check, and it returned the caller's own user account. Nothing in Backup used it, so nothing changes in how you use Backup.

SEO

SEO 1.1.2

Renaming a page's address and then changing it back no longer leaves the page unreachable at both addresses.

Changed

  • Needs Laramin 12.1.0 or later. Upgrade Laramin first. On an older Laramin, your website's SEO requests failed.

Fixed

  • If you change a page's address and later change it back, the page works again at its address. The automatic redirect that sent it away is retired, and you can restore it. Redirects you added yourself are left alone. See Add a redirect.
  • Redirects are checked whenever you add, edit or restore one:
    • A path that only differs by a trailing slash, such as /old/ and /old, counts as the same path.
    • A redirect that would send visitors round in a circle, directly or through other redirects, is refused.
    • When a new redirect starts where another one ends, the older one is changed to point straight at the new address, so visitors make one jump.
    • A redirect can't be restored if its path is taken now, or if it would send visitors round in a circle. See A redirect doesn't work.

Articles this release changed

Stub Generator

Stub Generator 1.0.4

The confirmations before files are written show their own title and button: Generate or Create module.

Fixed

Security

  • An unused API address is gone. Any API token could call it without a permission check, and it returned the caller's own user account. Nothing used it, and modules you create with Stub Generator never had it.

Razorpay

Razorpay 1.0.1

When Razorpay can't take payments, its health check tells you to install or turn on Billing, the module that processes them.

Fixed

  • When Razorpay is inactive because nothing can process payments, its health check names Billing as the module to install or turn on. It used to name Payment Gateway, which no longer processes payments, so following it changed nothing. See Razorpay payments stay pending.

Articles this release changed

Headless CMS

Headless CMS 1.0

The first release: design your own content types, write and publish entries in every language, and deliver them to websites and apps.

New

  • Design structured content in your Laramin, write it in every language you offer, and deliver it to your websites and apps. A new kind of content needs no code or deployment. Needs Laramin 12.2.0 or later. See How the Headless CMS delivers your content.
  • Content spaces: one for each website, app or audience, with its own languages, default language and fallback. A space is Public, so anyone may read it, or Restricted, so only applications you allow may read it. See Set up a content space and deliver your first content.
  • Content schemas: build a Single or a Collection from 16 field types, with a live preview of the form and of what the API sends. Move schemas to another Laramin with Export definitions and Import definitions. See Create a content schema and add its fields.
  • Changes never break an application that reads your content. Once a schema is published, a change that could break a reader waits for Publish as version, and older versions keep being served until you retire them. See How schema changes and versions keep applications working.
  • Assignments decide which schemas each space offers, with delivery on or off for each one.
  • Write entries in a form built from the schema, with one language switcher for the whole form and phonetic typing for Indian languages. Publish each language on its own, keep revisions, duplicate, reorder, and publish, unpublish or trash many at once. See Write and publish content and Translate content into your other languages.
  • Channels, such as web, Android or iPhone, let you show an entry on chosen channels only. See Show content on chosen channels only.
  • A public delivery API that serves only published content. Give an application access to a space, see which version of each schema it reads, and move it to a newer one. See Give an application access to a content space and Delivery API: addresses, parameters and responses.
  • The API explorer runs any delivery request as a visitor or as an application, shows which checks it passed, copies it as code, and previews drafts before they reach a reader. See See what an application receives in the API explorer.
  • Your public website's own pages can show content you publish here.
  • Risky changes ask first and say what they affect, and most changes can be undone for a short time.
  • Three roles: CMS Administrator, Content Editor and Content Publisher. Nobody has them until you give them. See Headless CMS settings.
  • When Webhook Engine is installed, the Headless CMS offers it seven events, such as an entry being published.

Security

  • Drafts can never be read through the public delivery API.
  • An application's key is never shown back, and a Restricted space answers only applications you've given access.
  • Anything hidden or missing gets the same answer, so nobody can tell which it was.

Core

Core 12.1

Each workspace has its own time zone, and you see times in your own zone with the workspace's clock beside them.

New

  • Set a workspace's time zone on its own form. Laramin asks you to confirm before you change it. See Create a workspace.
  • "Today", working days and due times follow the workspace's time zone. You see times in your own time zone, with the workspace's clock beside a business time. See Update your profile.
  • Company settings have an Office Hours section, with hours for each day. See System and company settings.
  • A Website link in the admin header opens your public website.
  • With an add-on that provides follow-ups, you can schedule, complete and snooze a follow-up from a record's own screen, see the work still outstanding on a record, and snooze to the business's next working day.
  • An access matrix shows what each role may do, and changes to a role's permissions are recorded.
  • Step-by-step forms show your progress as a gauge, and keep every step's description on screen.
  • Animations stop when your device asks for reduced motion.

Fixed

  • A time picker's Today button sets the current time.
  • A browser tab left open during an update reloads once, instead of showing a broken screen.
  • The rich-text editor no longer turns every space into a non-breaking space.
  • If the database stops responding, pages show an error instead of loading forever.
  • In step-by-step forms, Save works again when everything is valid, the step list shows where you really are, and a blocked step's message no longer replaces Cancel.
  • A list remembers its row density only when you chose one.
  • The public website settings and the coming-soon page are translated.

Monetization

Monetization 3.0

If you have subscriptions started from a CRM quote, they need a one-time server step when you upgrade.

Changed

  • If any of your subscriptions were started by an accepted CRM quote, ask whoever looks after your server to follow the 3.0.0 steps in Monetization's upgrade guide before you upgrade. Without that step, Monetization no longer recognizes those subscriptions as coming from their quote. Nothing else changes in how you use Monetization.

Core

Core 12.0

Workspaces arrive: run several businesses in one Laramin, each with its own teams, roles and settings.

New

  • Workspaces: run more than one business in one Laramin, each with its own people, teams and settings. See Workspaces, teams and experiences: the basics.
  • Every team belongs to one workspace. See Create a team and add members.
  • A role can apply in one workspace instead of everywhere.
  • Experiences replace user types. An experience decides the menu, the layout and the home page you see. Switch experience from View in the header, and set a default. See Switch to another experience.
  • The admin's look comes from Appearances. See Customize the admin's appearance.
  • An add-on's details show which other add-ons, and which versions, it needs. An add-on can't be enabled while something it needs is missing, and one whose needs aren't met stays off and says why, instead of causing errors. See Add-on statuses and actions.
  • An empty menu says so, instead of staying blank.
  • A dropdown can create the option you're looking for, and an option you can't pick shows as unavailable instead of disappearing.

Changed

  • User types are gone. If your Laramin customized a user type's home page, menu or layout, those settings are ignored now: an experience does the same job. The permissions for user types no longer do anything.
  • A role given in a team adds to what the person may do everywhere. It no longer replaces it. To give someone less in a team, remove the broader role.

Fixed

  • The sidebar no longer offers screens you can't open.
  • The workspace switcher is hidden when there's only one place to go, and the team switcher shows just its icon.
  • The header switchers and the color picker work again.
  • A problem with one field's options no longer breaks the whole Users screen.
  • IP rules that name a role look at the roles a person holds everywhere, not roles given only in a team.

Billing

Billing 2.0

Each of your businesses keeps its own billing records, invoice numbers, tax rules and payments.

Changed

  • Each billing record belongs to one business (a workspace in Laramin) and stays with it. Two of your businesses can bill the same customer, each with its own billing account, tax rules, ledger, and invoice and credit note numbers. See How Billing keeps your money records.
  • In a single workspace, you see and work with that business's records only. In All Workspaces, you can read the records of every business you can enter, but you can't issue an invoice, refund a payment or change tax rules there. Switch to the business first. See Issue an invoice and Refund a payment.
  • A record from a business you can't enter doesn't show at all.
  • Tax rules belong to one business, and a business can have only one active rule for a country and region. See Set up your tax rules.
  • A document created outside a single business gets undetermined tax, so it can't be issued, instead of being charged no tax. See How Billing works out tax.
  • Needs Laramin 12.0.0 or later. Before you upgrade:
    • Deactivate or delete any second active tax rule for the same country and region. Otherwise the upgrade stops and names the rules.
    • If you already have billing records, make sure your Laramin has a default workspace. Otherwise the upgrade stops before it changes anything.

Fixed

  • Billing's screen text in Tamil, some of which was cut off, is complete again.

Demo Mode

Demo Mode 1.3.1

Only super admins can open Demo Mode's settings, and its menu items show only to people who may open them.

Fixed

  • Demo Mode's menu items show only to people who may open their screens. Others used to see the items and get an empty screen.

Security

  • Only super admins can open Demo Mode's settings. The role editor used to list them as a permission, and a role given it could change the settings. See Set up and turn on Demo Mode.

Articles this release changed