But it still requires that you make a change to the Matrix code, albeit a small one. For those of you who may be lost, RwD is suggesting that all of the Matrix template code between {if} and {else} be replaced with a simpler {g->theme include=�../matrix/templates/theme.tpl�}.
Actually, because you would have to make a change to the Matrix code, it is recommended that you create a copy of the template file in gallery2/themes/matrix/templates/local/ and edit that. That way you can make other changes to the template without erasing them when you upgrade. This would mean making the replacement code {g->theme include=�../matrix/templates/local/theme.tpl�}.
Then, make your change to the Matrix code: change line 19 from theme url="matrix.css"}"/> to theme url="../matrix/theme.css"}"/>.
And although it should work, the <link> tag that includes the Matrix CSS will look a little funny: gallery2/themes/siriux/../matrix/theme.css.
Instead of changing the matrix theme you can also have your theme assign a different value to the $theme['themeUrl'] variable. Just replace the name of the current theme which is at the end for “matrix” and if all goes right the matrix theme will never know and happily put in the correct url…
Of course you should save the value after the inclusion…
4 Comments
To avoid having to update your files whenever the matrix theme changes you could also include the files rather then copying (parts) to the siriux dir.
To include the template file use something like {g->theme include=”../matrix/templates/theme.tpl”}
To use the matrix css use something like {g->theme url=”../matrix/theme.css”}
But it still requires that you make a change to the Matrix code, albeit a small one. For those of you who may be lost, RwD is suggesting that all of the Matrix template code between
{if}and{else}be replaced with a simpler{g->theme include=�../matrix/templates/theme.tpl�}.Actually, because you would have to make a change to the Matrix code, it is recommended that you create a copy of the template file in gallery2/themes/matrix/templates/local/ and edit that. That way you can make other changes to the template without erasing them when you upgrade. This would mean making the replacement code
{g->theme include=�../matrix/templates/local/theme.tpl�}.Then, make your change to the Matrix code: change line 19 from
theme url="matrix.css"}"/>totheme url="../matrix/theme.css"}"/>.And although it should work, the
<link>tag that includes the Matrix CSS will look a little funny:gallery2/themes/siriux/../matrix/theme.css.Anyway, thanks for the tip.
Instead of changing the matrix theme you can also have your theme assign a different value to the $theme['themeUrl'] variable. Just replace the name of the current theme which is at the end for “matrix” and if all goes right the matrix theme will never know and happily put in the correct url…
Of course you should save the value after the inclusion…
This is perfect! thanks! I wanted it so the client would have a nice clean admin screen but everything still looked good on the site.
2 Trackbacks/Pingbacks
free non downlaoad bj games…
Israel:exerting packed minute clouding …
after bankruptcy loan relief settlements in highlands ranch co…
Bohr grains wielding …