Yeah same here,
Any fast addon to fix it? or some change @ code/css.. or in generally for all the fixes? using XF 1.2 beta5
Core - PixelExit.com [Deleted]
- Thread starter Russ
- Start date
Any fast addon to fix it? or some change @ code/css.. or in generally for all the fixes? using XF 1.2 beta5
Anthony Parsons
Well-known member
Using commonsense, obviously some functions of the xenbase don't play well with a style as they're made for specific styles use, however...
Mini avatar doesn't lineup
Move ACP link doesn't remove it from mod bar, but does add it into account menu
Moderator navtab moves the tab to visitor tabs, but doesn't remove the moderator bar itself from view.
Mini avatar doesn't lineup
Move ACP link doesn't remove it from mod bar, but does add it into account menu
Moderator navtab moves the tab to visitor tabs, but doesn't remove the moderator bar itself from view.
Sheldon
Well-known member
I know I tried to style the user navigation drop down area, went to search the template, wouldn't find it. Couldn't get anything to show up on it when I manually edited it with TM either. There are a few things in [XB] I don't quite understand. That is the reason I haven't done much styling on my site. Waiting on the update.
Anthony Parsons
Well-known member
Same as above for admin post indicator being enabled.
Russ
Well-known member
Moving the ACP link doesn't remove it from the moderator bar on purpose, it's used more in conjunction with "enable mod bar", same thing with the MOD Nav Bar.
A lot of these issues have been address and still more are being addressed. Thanks for your input.
Last thing too in my update I did clearly put:
***NOTE*** This is considered a beta release of a style...
Just a heads up some things are broken, I'm working on fixing everything up though.
Steve F
Well-known member
Not every option in [XB] is setup for every style, although we do try to make sure things are close by default, things will need to be adjusted if the style does not ship with these things enabled.
Anthony Parsons
Well-known member
I have to say... there are some excellent ideas encompassed in this framework compared to others I've used for XF to date. That moderator bar shift into a visitorTab is excellent.
Anthony Parsons
Well-known member
No worries Russ... I'm not using this on a production environment, just a dev setup to help work out the kinks towards a gold release of XF.
Russ
Well-known member
Thanks, the Moderator Tab is almost done, a few bugs I found and also the responsive fix.
Russ
Well-known member
You can go to Style Properties -> Message Elements -> New Indicator (Outer)
Put this in misc:
Code:
margin-right: -15px !important;At the bottom of the rest of the code.
Anthony Parsons
Well-known member
I'm noticing repetitive CSS in media queries, where you're entering the same thing at maxResponsiveMediumWidth and maxResponsiveNarrowWidth, when you only need enter at the location you want to target either above, or below, but not both.
@media (max-width
maxResponsiveMediumWidth)
{
#footerlists
{
display: none;
}
p.expandFooter
{
display: block;
}
#advancefooter
{
text-align: center;
}
#advancefooter .section
{
float: none;
margin: 10px auto;
}
#footerleftarea
{
float: none;
width: auto;
}
#footerleftarea .flogo
{
}
.footercol
{
float: none;
margin: 0 auto;
}
}
@media (max-widthmaxResponsiveNarrowWidth)
{
#footerlists
{
display: none;
}
p.expandFooter
{
display: block;
}
#advancefooter
{
}
#advancefooter .section
{
float: none;
margin: 10px auto;
}
#footerleftarea
{
float: none;
width: auto;
}
#footerleftarea .flogo
{
}
.footercol
{
float: none;
margin: 0 auto;
}
}
You could remove that entire narrow width code, as it's all enabled at the medium width for narrow width viewing, as an example. Not sure how much you do this throughout...
@media (max-width
maxResponsiveMediumWidth){
#footerlists
{
display: none;
}
p.expandFooter
{
display: block;
}
#advancefooter
{
text-align: center;
}
#advancefooter .section
{
float: none;
margin: 10px auto;
}
#footerleftarea
{
float: none;
width: auto;
}
#footerleftarea .flogo
{
}
.footercol
{
float: none;
margin: 0 auto;
}
}
@media (max-width
maxResponsiveNarrowWidth){
{
display: none;
}
{
display: block;
}
{
}
{
float: none;
margin: 10px auto;
}
{
float: none;
width: auto;
}
{
}
{
float: none;
margin: 0 auto;
}
}
You could remove that entire narrow width code, as it's all enabled at the medium width for narrow width viewing, as an example. Not sure how much you do this throughout...
Russ
Well-known member
I'm noticing repetitive CSS in media queries, where you're entering the same thing at maxResponsiveMediumWidth and maxResponsiveNarrowWidth, when you only need enter at the location you want to target either above, or below, but not both.
@media (max-width
{
#footerlists
{
display: none;
}
p.expandFooter
{
display: block;
}
#advancefooter
{
text-align: center;
}
#advancefooter .section
{
float: none;
margin: 10px auto;
}
#footerleftarea
{
float: none;
width: auto;
}
#footerleftarea .flogo
{
}
.footercol
{
float: none;
margin: 0 auto;
}
}
@media (max-width
{
#footerlists
{
display: none;
}
p.expandFooter
{
display: block;
}
#advancefooter
{
}
#advancefooter .section
{
float: none;
margin: 10px auto;
}
#footerleftarea
{
float: none;
width: auto;
}
#footerleftarea .flogo
{
}
.footercol
{
float: none;
margin: 0 auto;
}
}
You could remove that entire narrow width code, as it's all enabled at the medium width for narrow width viewing, as an example. Not sure how much you do this throughout...
The entire footer is getting a little revamp where I'll need the individual media queries to be different at the different widths, it'll be cleaned up.
Anthony Parsons
Well-known member
You also might want to consider simply using this to get rid of that ugly footer gradient that you were covering with another footer gradient to hide:
.secondaryContent.footercol {
background: none;
}
It was being forced because of .secondaryContent class use. You can get rid of:
background: url("@imagePath/xenforo/images/flistsep.png") repeat-y scroll left top transparent;
From your footer block and then simply use the primary medium background color to correct the issue, without trying to cover one gradient with another, which you're currently doing.
.secondaryContent.footercol {
background: none;
}
It was being forced because of .secondaryContent class use. You can get rid of:
background: url("@imagePath/xenforo/images/flistsep.png") repeat-y scroll left top transparent;
From your footer block and then simply use the primary medium background color to correct the issue, without trying to cover one gradient with another, which you're currently doing.
Russ
Well-known member
Appreciate the input Anthony
Anthony Parsons
Well-known member
Sorry... I'm just going through it and I get picky with styling issues so as to produce the minimalist output possible to achieve the aim.
You don't want to see my sprite, as I pretty much get the entire style + add ons into a single sprite, so readers only load one image for the entire style. Google love it, which is why I do it.
You don't want to see my sprite, as I pretty much get the entire style + add ons into a single sprite, so readers only load one image for the entire style. Google love it, which is why I do it.
Russ
Well-known member
Haha no worries at all, many of the things have already been fixed or working on, I just know better not to release things over the weekend and Mondays.
Steve F
Well-known member
There is no gradient being "covered" it is simply specifying in more detail that .footercol is the target and overwriting (not covering) the secondaryContent. We used that there for the blocks to help be consistent with sidebar blocks.
Anthony Parsons
Well-known member
You might want to take a closer look at that, because you have an underlying gradient that has nothing to do with .footercol class, as it's being introduced into your footer due to .secondaryContent. It doesn't matter what you put in .footercol, that gradient is still present, thus being loaded. This is why I said, one is covering the other, being .footercol is loading after .secondaryContent and covering it.
Russ
Well-known member
We use secondaryContent as normally the blocks take the look of the traditional sidebar block.
We use footercol to help us with additional styling.
This is just something how we chose to do it.
On Core specifically... the footer is dark which is why we're using the footercol selector to help us style it further.
It worked, thanks!
