tag:help-archives.hannonhill.com,2010-02-09:/discussions/how-do-i/16402-alert-blockCascade CMS: Discussion 2018-10-18T20:37:26Ztag:help-archives.hannonhill.com,2010-02-09:Comment/360047612015-02-10T13:12:29Z2015-02-10T13:12:29ZAlert Block<div><p>Hi Katie,</p>
<p>Before answering your question, I would like to clarify two
things first.</p>
<ol>
<li>
<p>When you said "every page", how many pages were you talking
about? Do you plan to republish all the pages when needed?</p>
</li>
<li>
<p>What language do you use on the server side, after pages have
been published?</p>
</li>
</ol>
<p>I built an announcement system more than a year ago. Here is
some brief information:</p>
<ol>
<li>
<p>In the templates we have, I insert a line of PHP code for this
purpose, so that every page already has this line of code. The code
basically checks if two files exist (one for public, one for
intranet), and if they do, displays the content of the files
accordingly.</p>
</li>
<li>
<p>A site was built with two simple pages (hooked up with two data
definition blocks) that can be published and unpublished. When
these two pages are published, the PHP code embedded in step one
will be executed. If they don't exist, then no messages will be
displayed.</p>
</li>
<li>
<p>A web service script is used to hook up two web pages served by
the server to send commands and messages into Cascade, and
publishes/unpublishes the two Cascade pages. Users of these web
pages don't have to know anything about Cascade.</p>
</li>
</ol>
<p>In this setup, there is no page publishing other than using the
two web pages to publish/unpublish the two Cascade pages. If you
are interested, see <a href=
"http://www.upstate.edu/cascade-admin/projects/web-services/announcements/index.php">
Announcements</a> for more details.</p>
<p>Wing</p></div>Wing Ming Chantag:help-archives.hannonhill.com,2010-02-09:Comment/360047612015-02-10T15:48:19Z2015-02-10T15:48:19ZAlert Block<div><p>Every page is just that, every single page on the website. That
is part of the reason why I thought using a block would be more
efficient. I'm not sure how publishing works in the grand scheme
because we haven't got to that point. I assumed when you changed a
block and published that item that every page that used that block
would be updated.</p>
<p>We do not have a server side language setup yet, but it is most
likely coldfusion.</p></div>~katie~tag:help-archives.hannonhill.com,2010-02-09:Comment/360047612015-02-10T16:00:50Z2015-02-10T16:00:50ZAlert Block<div><p>I asked about the number of pages precisely because, if you
attach the block to every page, you need to republish every one of
them when the block is updated. This can take, for us at Upstate,
days to finish, and hence extremely undesirable. With PHP code
already embedded, no pages need to be republished, and that's the
whole point.</p>
<p>Wing</p></div>Wing Ming Chantag:help-archives.hannonhill.com,2010-02-09:Comment/360047612015-02-10T16:05:40Z2015-02-10T16:05:40ZAlert Block<div><p>Can anyone else confirm that you have to republish every single
page that uses a block? What if you apply the block at the template
level? If you make no changes to the structure and only to the
content of the block, do you have to republish every asset that
uses that block?</p></div>~katie~tag:help-archives.hannonhill.com,2010-02-09:Comment/360047612015-02-10T16:19:37Z2015-02-10T16:19:37ZAlert Block<div><p>Hi Katie,</p>
<p>Yes, Wing is correct. Any time a Block's content changes, you'll
need to re-publish any Pages that use the Block in question.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/360047612015-02-10T17:42:47Z2015-02-10T17:42:47ZAlert Block<div><p>Thank you Tim and Wing.</p></div>~katie~