I've been spending a lot of time fixing these problems since I bought JomSocial and the Socialize template a day ago, and hope to help the JomSocial team as well as other people who are running into these.
First, the big issues: in your Socialize demo site, any page you browse to was giving a javascript error for "collapse" being undefined, or something similar. I had also been getting the error "'joms' is undefined". This was coming from the new toolbar code. Additionally, when on any non-JomSocial page, if you're logged in and you click one of the toolbar buttons you get a javascript error "'cMiniWindowShow' is undefined". This is because the required javascript libraries aren't being loaded.
On a different topic, I couldn't get the template to use Google fonts, using either of the techniques described here:
www.joomlart.com/forums/showthread.php?8....0-with-google-fonts
.
To fix these, I inserted the following code at line 26 of /templates/socialize/tpls/blocks/head.php:
<?php
//$this->addStyleSheet(JURI::root() . 'components/com_community/templates/default/css/style.css');
//$this->addStyleSheet(JURI::root() . 'components/com_community/assets/modules/module.css');
$this->addStyleSheet(JURI::root() . 'components/com_community/assets/window.css');
//$this->addStyleSheet(JURI::root() . 'components/com_community/assets/minitip.css');
//$this->addStyleSheet(JURI::root() . 'components/com_community/assets/autocomplete.css');
//$this->addStyleSheet(JURI::root() . 'components/com_community/assets/jqueryui/datepicker/css/ui-lightness/jquery-ui-1.9.2.custom.css');
$this->addScript(JURI::root() . 'components/com_community/assets/joms.jquery-1.8.1.min.js');
//$this->addScript(JURI::root() . 'components/com_community/assets/script-1.2.min.js');
$this->addScript(JURI::root() . 'components/com_community/assets/window-1.0.min.js');
//$this->addScript(JURI::root() . 'components/com_community/assets/minitip-1.0.js');
$this->addScript(JURI::root() . 'components/com_community/assets/bootstrap/bootstrap.min.js');
//$this->addScript(JURI::root() . 'components/com_community/assets/jqueryui/datepicker/js/jquery-ui-1.9.2.custom.js');
//$this->addScript(JURI::root() . 'components/com_community/assets/joms.ajax.min.js');
?>
<?php
$this->addStyleSheet('
fonts.googleapis.com/css?family=Roboto:400,500,700
');
?>
I left those commented-out lines in there, just in case some other functionality might be required from one of those libraries/stylesheets for something I haven't encountered yet. But I believe the uncommented lines are minimally required for the toolbar to work correctly on all non-JomSocial pages.
In my custom.css, I have the following:
body {
font-family: 'Roboto', sans-serif;
font-size: 15px;
color: #333333;
}
#community-wrap .js-toolbar-mods.toolbar-login .btn,
#community-wrap.community-toolbar.toolbar-login .btn {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
}
td {
border-top: none;
padding: 0;
}
.form-horizontal .control-label {
text-align: left;
}
.pagination a {
padding-left:14px !important;
padding-right:14px !important;
}
Right now the big problem I'm working on is the Facebook Connect module. It doesn't play well with the toolbar at all. I want it in the header as part of the toolbar actually. First, I eventually had success getting it next to the toolbar in a visually almost seamless way, and working reasonably well with resizing the window. But, then I realized that it completely throws off the responsive design of the template, so I had to throw it out. I figured that the only way to make it work correctly, responsively, is to merge the jomsocialconnect and community_toolbar modules, so that the toolbar can include the Facebook login button. I'll have this ready in the next couple of days.
Hi Daniel.
1)To be honest I'm not able to replicate this problem, could you maybe provide us with some exact steps to reproduce this issue on your site?
2)Question about different fonts, was already answered on your joomlart's forum.
3)And about this FBC issue, could you also provide us with some steps to reproduce this problem so our developers could take a look?
Hey Chris, thanks for the prompt response.
For (1), I can do better than that - here's how to reproduce it on your site: :)
Hi Daniel.
I'm able to replicate this issue, so I'm passing this thread to our developers, thanks for report.