VCU - Technology Services

Page # is empty, maybe not approved?
Log into the CMS. From the left menu choose Tasks -> # Edit Pages -> Check all complete pages and click on "Submit to Workflow" button. If there is an approval flow for your department, your approver will need to release your page before it can be published.

PageId # without Content, not published
The CMS will not publish pages without at least one content element populated. Note: Anchors (anc_) and lists (lst_) are structural elements and will sometimes cause the publication to fail.

Page # not linked in HTML/ENU
During publication, the CMS follows lists and anchors when publishing a website. Checking "publish related pages" will look for any lists or anchors and publish the attached pages. If a page exists that is not connected to a list or is incorrectly attached to an anchor, the page is considered "unlinked". Unlinked pages (orphan pages) must be manually published. Unlinked pages are generally discouraged, since they are not part of the website structure and can be easily deleted.
Note: HTML/ENU is the project/language variant used for publication. HTML is the project variant checked by default during publication, though others may exist. Project variants define the format of a project's published pages.

Page not changed
If you changed an image or content on a page and try to publish but the server returns a report saying the page is already published you will need to clear the page cache. Do this by selecting "Administer Project Structure" -> Project -> Action Menu (Clear Page Cache). The system will ask "Are you sure you want to clear the page cache?" - click "Yes". The system asks this question because the operation taxes the CMS server. Wait about 10 minutes, then republish. If your pages are still not publishing, make sure your "Tasks" folder is clear and republish once more. If your changes are still not publishing contact Web Services.

Blank Publishing Report
The "images" folder, a subdirectory of one of my sites, had temporarily been set to read-only. When the CMS tried to publish any page of this website, it returned a blank publication report which was neither "successful" or "failure". I cleared the cache, and tried to republish but I received another blank report. By logging into my external server with an ftp client I realized that I did not have access to that folder. The CMS stops publication at the first error from the server. In this case, the error was access to a subdirectory, therefore nothing was published, not even to other directories. To fix this problem, remove that folder from the publication package and from the folder structure OR get permissions to the folder.

Have you seen other errors? Leave a comment or email me: tlfrance.