
Why won’t it let me publish - something about a photo?
You asked for something to go live and got a refusal mentioning a photo instead of your page. That’s not a glitch - it’s your library stopping a photo you shouldn’t publish before it happens, rather than after.
The prompt
“Publishing was refused because of a photo - tell me exactly which one, why, and what I need to do to clear it.”
Signed in, Get my prompt fills in your site for you. Otherwise press Copy and fill in the [bracketed] parts. First time? Connect your AI to bernard once: Use your own AI (opens in a new tab).
Two different refusals, two different fixes
A new photo nobody has answered for. When your assistant publishes, every new photo in the draft must be settled. That means you already gave consent (the photo is on your live site, you uploaded it yourself, you confirmed the import, or it is marked Part of the site design), or the photo says Mine, Licensed, Stock or From a client. A photo fetched from a web address you did not confirm, and still at Not sure yet, holds the publish. The fix is to say whose it is: How do I approve a photo so my assistant can publish it? shows where. Then publish again. The Publish button in the app is not held up by this.
A rights problem means the photo’s licence has expired, or its usage terms say it isn’t cleared for the web. This one is a fact about the photo, not a decision waiting on anyone, and it blocks everyone, you included. Open the photo in your library and fix the rights details (a later expiry date if the licence was actually renewed, or different terms if what’s recorded was wrong); once the card is accurate, the block lifts by itself. See Am I allowed to use this photo? for how those details get recorded in the first place.
Your assistant can’t answer for you
It can tell you exactly which photo is blocking things and why - it reads the same refusal you’d see. It can write down rights details you give it, such as a renewed expiry date or whose the photo is, and only in your words, never on a guess. It has no way to mark a photo Part of the site design. Whose a photo is stays your answer, every time.
“Not sure yet” is fine on your own site
A photo marked Not sure yet can still go on your pages when you publish yourself. It just carries no name inside the file until you say whose it is (bernard asks whose a photo is. What should I answer?).
Nothing else about your change is lost
The refusal only stops the publish - your draft is untouched and everything else you changed is still sitting there ready. Fix the one photo and publish again; you won’t have to redo any of the rest.
Questions people ask
- Why did publishing get refused because of a photo?
- One of two reasons. Either a new photo still says Not sure yet and bernard cannot show you gave consent for it - answer whose it is and it clears - or its rights have a problem (an expired licence, or terms that do not cover using it on the web), and only updating the rights details fixes that.
- Can my assistant answer for me so publishing goes ahead?
- No, and it will not try. It can tell you which photo is holding things up and ask you whose it is. It records only what you say in your own words. Then it tries publishing again. Your own Publish button in the app is not held up by a photo that says Not sure yet, and it clears that photo as before.
- The licence says it’s expired but I’m sure we’re still allowed to use it - what do I do?
- Update the expiry date (or the rest of the rights details) on the photo’s card in your library. Once the details are right, the block clears on its own - there’s nothing else to approve or reset.