At 09:32 PM 2009-02-10, you wrote:

> > I want to transclude all tiddlers tagged "dashboard"
> > into a single tiddler, and make this my default tiddler.
>
>Try this inline script:
>    http://www.TiddlyTools.com/#EmbedTiddlers
>    (requires http://www.TiddlyTools.com/#InlineJavascriptPlugin

I'll take a look at that. Haven't yet.

> > "Error in macro <<tiddler>>"
>
>hmmm... "<<tiddler [[TiddlerName]]>>" is the correct usage... so there
>must be something else (i.e., a plugin) that is breaking the standard
><<tiddler>> macro syntax.  Click on the "error in macro" text to see
>the specific javascript error message.  This might provide a clue as
>to what has gone wrong.  Then, try disabling any plugins that might be
>re-defining  the "config.macros.tiddler.handler" function.  If the
>problem disappears, then you know that one of those plugins is the
>cause.  Then start re-enabling plugins one at a time, until the
>problem re-appears.  The last plugin you re-enable is the culprit.

The error message is
    Error while executing macro <<tiddler>>
    TypeError: stack.find is not a function

It went away when I disabled the TiddlerWithParamsPlugin,
and the tiddlers' contents appeared, as expected.

I don't think I'm currently using TiddlerWithParamsPlugin.
Does the current core code make it unnecessary?
(I'm currently using 2.4.1.)

 From the TiddlerWithParamsPlugin docs:
    The TiddlerWithParamsPlugin extends the build-in <<tiddler...>>
    macro. It replaces placeholders ($1, $2, ...) in the given tiddler
    by values passed with the macro. Then it inserts the (replaced)
    text, just like the original <<tiddler...>> macro.

- Sam



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/TiddlyWiki?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to