An entry can't be published
Publishing an entry stops with "This couldn't be published. Fix these first:" or another refusal. Find the message below and fix the field it names.
- Applies to
- Headless CMS 1.0 and later
- Who can do this
- Team member, Administrator
- Permission
feature.hcms. entry. publish - Where
- Headless CMS › Content
On this page
Symptom
You select the publish button and the entry isn't published. You see This couldn't be published. Fix these first: with a list of fields, or one of these:
| Message | Go to |
|---|---|
| … is required to publish. | 1 |
| Add alt text to … to publish. | 2 |
| Give this entry an address to publish. | 3 |
| This entry can't be published yet. Fix the fields named and try again. | 4 and 5 |
| This upload has expired. Upload the file again. | 6 |
| No publish button, or Save your draft and ask someone who can publish | 7 |
Required fields are only checked when you publish, not when you save a draft. So a draft that saved without complaint can still be refused.
Check these, in order
1. A required field is empty in this language
… is required to publish. names a field marked Required to publish that is empty. Publishing checks the language you're publishing, so a field filled in English can still be empty in Tamil. Values shared by every language are always checked.
Which languages must fill in every required field is set by Required fields must be filled in in the settings, for the whole Headless CMS or for one content space. With Every language of the space, each language needs its own values.
Fix: Switch to the language you're publishing, fill in the field, and publish again. See Translate content into your other languages.
2. An image has no alt text
Add alt text to … to publish. means an image field needs a short description of the picture, for people who can't see it.
Fix: Add the alt text in the image field the message names, and publish again.
3. The entry has no address
Give this entry an address to publish. appears when the schema gives entries a web address and Address is empty.
Fix: Type an address in Address, such as opening-hours, and publish again.
4. A value is over a limit that was lowered
An administrator lowered a limit, such as a maximum length, after the entry was written. A value you haven't touched still saves. But once you change it, it must fit the new limit, and Publish refuses until it does.
Fix: Shorten the value to fit the limit shown under the field. See Headless CMS settings.
5. A field's rule was tightened
When a field's rule is made stricter, entries already published stay delivered, but can't be published again until they meet the new rule.
Fix: Correct the field the message names, then publish. See How schema changes and versions keep applications working.
6. An upload expired
A file you uploaded wasn't saved in time.
Fix: Upload the file again, save, and publish.
7. You can't publish
The editor shows Save your draft and ask someone who can publish, with the names of people who can. Your role lets you write but not publish.
Fix: Save your draft and ask one of them, or ask an administrator for Content Publisher. See Your editors can't open Headless CMS or publish.
Still not working?
Raise a ticket from Support Center in your Laramin app. Include this page's link, the entry, the language you tried to publish, and the full message.
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.