Skip to main content
Use this guide when an Article fails to reach your CMS or an update does not appear on the live page. Keep the Article open and copy the exact error before changing anything.

​
Check before retrying

  1. Confirm the Project, Article and publishing destination. Open the CMS and look for the Article, including drafts and the trash.
  2. Read the publishing result. A successful Save as WordPress draft leaves an unpublished item in WordPress; it does not make the page live.
  3. If the result is uncertain, stop retrying until you know whether the CMS created an item. Check the title, URL and last edit time. Do not create a duplicate just to clear an error.
If publishing is unavailable rather than failing, check the Project’s Plan and ask a Workspace Admin to check your Content Studio permissions and access to the publishing destination. Read the Article’s current status after a failure; do not assume it remained an unpublished draft. The CMS may have accepted the write even when Videntic could not confirm it. If your Plan does not include direct CMS publishing, you can publish manually on your site and record the live page.

​
Choose the matching error

​
WordPress rejected the publishing credentials

Ask your WordPress administrator to confirm that Application Passwords are enabled and that the connected WordPress user can create and publish the intended post type. Site moves, revoked authorization or security policies can change this access. Once access is restored, follow Connect WordPress to authorize the connection again. Retry once, then open the resulting item in WordPress and check its status. A Connected badge alone does not verify publishing permission.

​
The WordPress REST API was not found

Check that the connection uses the public HTTPS address of the WordPress installation, including its subdirectory if it has one. Ask the site’s administrator to confirm that the REST API is enabled and reachable. Correct the address or site configuration before retrying.

​
The website refused the connection, or its certificate could not be verified

Send the exact message to your web host or website administrator. Ask them to check the firewall or the site’s security certificate, according to the error. Retry after they confirm the problem is fixed; reconnecting does not repair a certificate or unblock a firewall.

​
The linked WordPress post no longer exists

Ask the WordPress editor to check the trash and restore the original post if it should remain the same page. If you deliberately need a new post, use Duplicate on the Article and review the copy before publishing it. A new post can have a different URL; check links to the old page with your website editor.

​
WordPress may already have this Article

Check WordPress for the title and intended URL, including unpublished items. If an item exists, inspect it rather than creating another. If you cannot establish whether the write succeeded, contact support with the error and what you found. Do not keep retrying or duplicate the Article while the result is uncertain.

​
Webflow or Framer asks you to confirm the collection mapping

Open the provider in Settings → Integrations. Review the destination collection and its field mapping, then confirm it. If the collection fields changed, review the refreshed fields and confirm again. Ask the person managing the CMS collection to help if you do not recognise the fields. Retry after confirmation, then open the CMS item and check its content and publication state. See Webflow or Framer for setup.

​
Check the result

Open the intended public URL without being signed in to the CMS. Confirm the title, changed passage, images and links. If you deliberately sent a draft, verify the draft in the CMS instead and leave it unpublished until approved. If the live page still differs from Videntic, follow Resume and update an Article. Saving an Article and updating its live page are separate actions.

​
Still blocked, or a different error?

Email [email protected] with the Project, Article title, CMS, approximate time, exact error, intended action and whether you found an item in the CMS. Include its URL if available. Do not send passwords, authorization tokens or private connection addresses. Keep the Article so support can investigate the same item.
Last modified on November 5, 2026