CMS Troubleshooting
Invalid XML: The prefix "o" for element "o:p" is not found
If you receive this error when trying to create or submit changes to an asset, there may be <o:p> tags in the source code of your asset, likely in the source code of the WYSIWYG editor, that will need to be removed or converted to regular <p> tags before the asset can be submitted.
Usually these tags are leftovers from pasting formatted content from Microsoft Word into the WYSIWYG editor. To avoid this error in the future, you can:
- Enable the Edit > Paste as text option in the WYSIWYG and then paste your content.
- Paste the content into a plain-text editor like Notepad, TextEdit, or any code editor to remove formatting prior to pasting it into the WYSIWYG.
An error occurred during publish: The folder hierarchy does not allow this asset to be published
This means the parent folder (the folder that's house the page or file you're editing) is set "not to publish."
Start by Editing the current folder the asset is in, and select "Properties"
There will be three checkboxes and the center one you'll see "Include When Publish"
If this is unchecked, then that's the reason why you receive that error. Check the box and try republishing your asset.
If the box is checked, go up another folder level and repeat.
File isn't rendering
common issue with uploading files is removing the extension at the end of the file name. Extensions include:
- jpg
- png
- docx
without this extension, the CMS doesn't know what to render and will return an error.
Rename the file and add the proper extension to resolve the issue.
