[Building Sakai] Portal NEO Prefix

[David Adams]

I was just looking at this earlier this week. There's also a new
property "portal.templates" that specifies what VM templates to use
when rendering the HTML. Hardcoded into the portal logic, it checks to
see if portal.templates is "neoskin" and if it is, it ensures that the
skin name (property skin.default) is prefixed with the value of
property portal.neoprefix.

I assume the reasoning behind it was to make sure you don't
accidentally specify a non-"neo" skin. But in practice it's turned out
to make things much more confusing. In our case, our developers
updated the "default" skin directory with their new neoportal CSS,
thinking that since skin.default was set to "default" that meant (as
it has up through 2.8) that the skin directory would be named
"default". But nope, it was "neo-default" that was actually getting
served.

Doh.

-dave


Sam Ottenhoff wrote:
> Can someone explain the need for the 2.9+ property called portal.neoprefix with a default value of "neo-"?  I understand that it means your "default" skin now becomes "neo-default", but why was it needed?
>
> We are starting to see some requests like this one:
>
>   https://jira.sakaiproject.org/browse/STAT-345
>
> The tools include a link to the tool.css file, but it's not the one they expect because the tool has no idea about this neoprefix.
>
> So, is neoprefix necessary?  Do we need to patch the tools to make them neo-aware?
>
> Thanks,
> Sam
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"