[Glass] GsDevKit_stones - questions
Kurt Kilpela
kurt.kilpela at gemtalksystems.com
Tue Dec 3 14:06:58 PST 2024
Marten,
You are correct. There was a bug in the default_seaside template. It used
the wrong class name. This has been fixed by
https://github.com/GsDevKit/GsDevKit_stones/pull/27.
You will need to update your registry's default_seaside.ston template. Once
you update the GsDevKit_stones repo, you'll find the updated
default_seaside.ston in the repo's template folder.
Kurt
On Tue, Dec 3, 2024 at 1:35 AM Marten Feldtmann <m at feldtmann.online> wrote:
> On 03.12.24 00:03, Kurt Kilpela wrote:
> >
> > >- when I create stones with different templates (--template=) I
> > sometimes must define tode-stuff (default_seaside) in the registry,
> > sometimes not (minimal).
> > What command and arguments are you using to create a stone showing
> > this problem? I wouldn't expect tode unless the template contains
> > `#tode : 'enabled'`.
> >
>
> The reason for this problem is, that the method todeHome is called when
> calling customizeCustomEnv - and this happens, when "customenv" is
> defined in the specific stone file.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20241203/37d97cc0/attachment.htm>
More information about the Glass
mailing list