5121 Posts in 1527 Topics by 1119 members
|
Page:
1
|
Go to End | |
| Author | Topic: | 462 Views |
-
Remove or Disable the Silverstripe Navigator on the Front End

15 July 2011 at 8:23am
Hi,
I was wondering if there is a way to remove or disable the Silverstripe Navigator on the front end? It seems to be overwriting some of my CSS styles for the rest of my site.
I'd really rather turn this off than hunt down all of the conflicts. I saw that there is a Compact Navigator module too. Which is closer to what I want if I *have* to keep the navigator on the front end.
Any suggestions would be great!
Thanks!
-
Re: Remove or Disable the Silverstripe Navigator on the Front End

15 July 2011 at 9:39pm
Hi,
you could search for the variable $SilverStripeNavigator
in your template and delete it. This should disable the SilverStripe Navigator.Cheers
-
Re: Remove or Disable the Silverstripe Navigator on the Front End

15 July 2011 at 11:35pm
Thank you for the reply! I'll look for that.
On second thought I might leave it. Its not my preference to have it visible but that might not be everyone's preference.
Alternatively, I may see if there is a way to move it before my other style sheets... to see if that will prevent it from overwriting some of my styles.
Thanks!
-
Re: Remove or Disable the Silverstripe Navigator on the Front End

16 July 2011 at 12:00am
This worked, thanks! I feel silly that I didn't see that myself.
Also, just for reference the SilverStripeNavigator class/function is located in a php file in sapphire/core/control
I haven't poked around yet to see if I can change where the CSS file is inserted in the header. In my installation layout, form and typography also seem to get re-inserted even though I've included them in my template. But this may be a question/conversation for another thread.
-
Re: Remove or Disable the Silverstripe Navigator on the Front End

16 July 2011 at 1:33am
...also seem to get re-inserted ...
If you include your stylesheets in your template, check your /mysite/Page.php file.
Maybe you are calling them again in your Page_Controller class.
(Have a look at the init method for Requirements:: ...)Cheers
| 462 Views | ||
|
Page:
1
|
Go to Top |


