New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protostar template doesn't work with component links in SEF #5081
Comments
I can't reproduce this here. Can you be more specific with which enviroment you're testing this? |
@waveywhite I suppose, you have disabled a "System - SEF" plugin, right? 😄 |
I have disabled the SEF plugin, yes. I guess that must be a factor as well! Thanks, Fedik. I need to do that for performance reasons (the SEF plugin is lousy with embeded SVGs). Still, this problem doesn't happen in Beez and Protostar isn't following recommended practice (http://docs.joomla.org/Creating_a_basic_Joomla!_template) so I think it's still a bug. To reproduce bug:
The file is templates/protostar/index.php. The line numbers in question are 41 and 43. The environment is Ubuntu 14.04 with Apache 2.4.7 |
Can you replace |
Hi dgt41. Who would you like to do this? Either this->baseurl or JUri::base() should work, a the moment neither is in place. Which is preferable? |
Can you create a Pull Request then? See http://docs.joomla.org/Using_the_Github_UI_to_Make_Pull_Requests for how to do it. If you do, you will get proper credits for doing it 😄 |
In theory, |
Set to "closed" on behalf of @brianteeman by The JTracker Application at issues.joomla.org/joomla-cms/5081 |
In index.php for the protostar template the css and javascript links are relative. With SEF & .htaccess enabled this causes the template to attempt to load these files relative to the current path. These paths map to the component and Joomla tries to map them to a page and outputs HTML instead of the desired CSS file.
To recreate this bug:
Create a new Joomla install with Protostar as default template and no content
solution: prepend these with JUri::base calls to build the proper CSS and javascript paths.
-David.
The text was updated successfully, but these errors were encountered: