Re: nugget bug

Hi!

> I added a macro to a nugget (say, the firstBelowCalendar one), and set 
> its Active flag to 'yes'.

Why? "Active" is one of the worst (but coolest) featurs of PyDS. Maybe I
_should_ write some documentation ;-)

Active=yes doesn't say anything about wether the nugget is used or not
used. It modifies the _way_ it is used. An active nugget isn't rendered
inline into the HTML source, but just renders an external script
reference. When your page is fetched, the external Javascript source
inserts the nuggets content into the document. To make the active nugget
current, you either update it manually or - better - set up a timer to
rerender this active nugget.

> But, then I went back and modified the macro that the nugget calls, 
> saved it, and published a new post - and did not see the changes.

Sure. Active nuggets are only rerendered when the active nugget itself
is rerendered. Used macros never trigger rerendering.

> Also, I can't recall for certain, but I think I also tried just
changing 
> nugget content directly (not the content of the called macro), and
also 
> got the same behavior - PyDS ignoring the new changes.

Hmm. I am quite sure that changing the nugget itself should rerender it.
But I usually only use them from timers. For example my google box is
rendered as an active nugget.

bye, Georg