I think you *have* to use publish--(IIRC auto refreshing will work only for what you *manually* place in CVS xml-site CVS) Don't worry, go ahead and press the "publish" button--the Forrestbot web interface is a lot more robust than it looks!
After publishing, you will need to wait up to 6 hours before the site moves to production. (It updates after a publish 4 times per day IIRC.) Also, anytime after publishing, go ahead and update the xml-site CVS with the previous breadcrumb.js file. You have karma on xml-site also. [BTW, you forgot to add Jeremy's birthyear to your bio--no big deal, but you might be getting congratulatory emails/demands for cigars every late June! ;)] Glen --- Clay Leeds <[EMAIL PROTECTED]> wrote: > I made my 1st CVS *commit* via SSH last > night--team.xml--as a test (the > de facto initiation? ;-)), but don't recall how to > push it LIVE > (thought it would be LIVE this a.m. w the 6-hour > Forrestbot 'refresh'). > I hesitate to do use the Forrestbot Web Interface > 'til I'm clearer > about its use. Also, the temp version of > team.html[2] shows the dreaded > breadcrumb.js error. Can someone clue me in on when > to use Forrestbot > 'publish' as opposed to allowing the auto Forrestbot > 'refresh'? > > [1] > http://forrestbot.cocoondev.org/sites/xml-fop/team.html >
