Your change doesn't show on your website or app
You changed an article, a page, a setting or a picture in Laramin, and your website or mobile app still shows the old one. Find which add-on serves it, how long it may take, and what to check.
- Applies to
- Core 12.7 and later
- Who can do this
- Administrator, Team member, Platform owner
On this page
Symptom
You saved a change in Laramin, but your website or mobile app still shows the old text or picture, leaves something out, or says it can't find it.
First, wait a few minutes
Some answers are kept for a while so websites and apps load quickly. A change that shows after a few minutes, or after the app is closed and opened again, worked. The table below gives the usual delay for each kind of content.
Find what serves it
Your website and app don't read Laramin's screens. Each kind of content comes from one add-on, which has its own rules for what's published and how long a copy is kept:
| What you changed | Served by | Usual delay | Read |
|---|---|---|---|
| A blog article | Blog | Short; your website may keep its own copy longer | An article doesn't show on your website |
| A page, a content entry or a picture in a content space | Headless CMS | Up to 6 minutes for a Public space, with the default settings | An application doesn't receive your content |
| Which page is your website's home page | Core, with Headless CMS | As for Headless CMS | Choose what your website's home page shows |
| App settings, menus, onboarding or dashboards | Core Mobile | Until the app asks again, usually when it starts | The app doesn't show your changes |
| What search engines see, or the sitemap | SEO | Up to Sitemap cache (minutes), 60 by default | Your pages don't show in search results and A page you hid still shows in search results or your sitemap |
| An uploaded picture is broken | Core storage | None | Uploaded images don't show |
If your website is served by an add-on of its own, it may keep its own copy of pages for a short while. Its help explains how long.
Check these, in order
1. The change isn't published
Most content has a draft and a published version, and websites and apps get only the published one. In Headless CMS, each language is published on its own.
Fix: publish the change, in every language your website asks for. The article for the add-on, in the table above, says how.
2. It was scheduled, and scheduled jobs don't run
A blog article set to publish later goes live only when your Laramin's scheduled jobs run.
Fix: publish it now from the article, then see Scheduled jobs don't run.
3. Nothing at all reaches your website or app
If every page or every app screen fails at once, the cause is in Laramin as a whole:
- Maintenance mode is on. Websites and apps get a maintenance answer. See The maintenance page shows when it shouldn't.
- The add-on that serves it is turned off. Its content disappears with it. See Add-on statuses and actions.
- The platform API key was replaced. An app that reads its settings before anyone signs in, still sending the old key, is refused. Your website's public pages aren't affected. See An integration stopped working.
Still not working?
Raise a ticket from Support Center in your Laramin app. Include this page's link, what you changed and when, the address or app screen where it should show, and what it shows instead.
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.