Ryan, thanks for looking into this. We started noticing the bug
after upgrading to Cascade 7.02. The data definition we're using is
attached. I'd recommend changing all the fields to "optional" for
Thank you for your patience. This sounds like a known defect in
which returning to the Page creation from a secondary step (ie
spell check, link check, accessibility check, etc.) causes
<system-xml> tags and numerical entities to be
inserted into the WYSIWYG. Feel free to track the progress of this
issue using the link I have provided to see if it has been resolved
in a future version of Cascade.
In the meantime, I was not able to reproduce the "null" error
you mentioned, this could very well have been some invalid data
entered within the WYSIWYG. Once the page is created, the
<system-xml> tags should be removed and the
numerical entities should be corrected when you edit the Page
again. If this is not the case, let us know.
I believe you are running into the following known defect in
which Content Type Index Block caches are not properly cleared when
attempting to create a new Page using the same Content Type as the
Can you confirm that you have caching enabled and there is a
news story Content Type and at least one Content Type Index Block
indexing that Content Type?
The link I provided explains in a little more information on the
issue, provides the steps to reproduce, and offers a workaround. To
sum things up, if you have 2 Index Blocks for that Content Type,
you need to hit submit 2 times to clear each cache and create the
Yes, I can confirm that:
1. In Preferences > General, we have "Index Block Rendering
2. We have a "News Story" content type.
3. We have 3 content type index blocks indexing
that content type.
That explains why one person got by the error by hitting submit
So it sounds like the workaround is to consolidate the two
content type index blocks into a single index block?
If you are not including page content (ie Render page XML
inline), you could certainly go well over 200-300. Once you
include page content; however, the size of the Index Block will
increase quite a bit.
That being said, with the introduction of caching, you should be
able to go over 200-300 because the Index Block won't take nearly
as long to render. I'm not sure of an exact number, it really
depends on what you are including within your block.