Unless a tag needs to be -privileged, I find it much more convenient
to load tags from outside of the startup folder. That way the files
can reside alongside the rest of your project, and they're easy to
refresh as needed without restarting the site.
http://devblog.jasonhuck.com/2008/04/10/using-namespaces-to-load-lasso-tags-into-memory/- jason
On Thu, Jul 2, 2009 at 11:45 AM, Adam de Zoete<
lists@...> wrote:
> I've ended up in the tricky situation of not being able to unload a
> namespace.
>
> The namespace actn_ was created at startup and can not be unloaded or it
> contains unloadable namespaces or tags.
>
> Is there anyway can tell what namespaces were loaded at startup? I thought
> there was a $__global_namespaces__ global or something built into Lasso.
> Anyone know the best way to track this?
>
> I've check all the other site folders and it seems like it might be a
> problem with the tags and types themselves. Everything is defined as
> -namespace='actn'.
>
> Is there an easy way to track what's going on here? Any suggestions would be
> greatly appreciated?
>
> Many thanks,
>
> Adam
>
> --
> This list is a free service of LassoSoft:
http://www.LassoSoft.com/> Search the list archives:
http://www.ListSearch.com/Lasso/Browse/> Manage your subscription:
http://www.ListSearch.com/Lasso/>
>
>
--
tagSwap.net :: Open Source Lasso Code
<
http://tagSwap.net/>
--
This list is a free service of LassoSoft:
http://www.LassoSoft.com/Search the list archives:
http://www.ListSearch.com/Lasso/Browse/Manage your subscription:
http://www.ListSearch.com/Lasso/