Peggy
in memoriam 2016
I saw that. Thanks so much Erik!It's fixed. I just accidentally uploaded Flexile Dark.![]()
I'm assuming that I just need to re-import the xml?
I saw that. Thanks so much Erik!It's fixed. I just accidentally uploaded Flexile Dark.![]()
Yep.I saw that. Thanks so much Erik!
I'm assuming that I just need to re-import the xml?
Nope, those have actually never been updated. They have been the same since the first release of Flexile since all they do is change some color values.And the xml files in the additional colors have been updated as well?
Nope, those have actually never been updated. They have been the same since the first release of Flexile since all they do is change some color values.They will likely never be updated unless the color palette system is changed.
![]()
Essentially, yes. Although you don't want to overwrite the Red style, you want to overwrite it's parent.oh I see. So I can safely update the red style with that xml file, because it takes on the blue files' internal workings?
Very smart...
oh my. See? I told you I'm easily confused! lol.Essentially, yes. Although you don't want to overwrite the Red style, you want to overwrite it's parent.![]()
Correct. It's kind of hard to understand but the "blue" Flexile contains all of the code that makes Flexile look like Flexile (the structure, the templates, etc.). It just happens to be blue by default. The "red" XML file essentially just says, "make everything red", which is why it's a child of the "blue" Flexile style.So I don't need to upload the red style's xml at all. (the red is a child of the blue).
Correct. It's kind of hard to understand but the "blue" Flexile contains all of the code that makes Flexile look like Flexile (the structure, the templates, etc.). It just happens to be blue by default. The "red" XML file essentially just says, "make everything red", which is why it's a child of the "blue" Flexile style.
If you were to upload the "red" Flexile XML as a child of the default style, it would just give you a red default style!
So the original, base "blue" Flexile style is the one that gets updated with each release. And as you said, the "red" style simply inherits the "blue"s internal workings. Hopefully that makes a bit easier to understand.![]()
This is also why I recommend making changes in a child style to Flexile. That way, you don't have to touch the original and can just overwrite it when it comes time to update.![]()
Just create a new style that's a child of the Flexile style, and then modify the templates in that child style. The child style will only contain your modifications and inherit everything else from the parent Flexile style, so when you update the parent, the child will inherit all of the changes made in the update. Hopefully that makes sense.If I wish to use the basic Flexile template for my site, what is the best way to take your suggestion so the next upgrade process is easier? Can I import Flexile as a child of Flexile? then modify the child?
Just create a new style that's a child of the Flexile style, and then modify the templates in that child style. The child style will only contain your modifications and inherit everything else from the parent Flexile style, so when you update the parent, the child will inherit all of the changes made in the update. Hopefully that makes sense.![]()
.EWRporta_Portal .mainContainer { margin-bottom: 10px; }
/* FLEXILE > MEDIA > TAG CLOUD SETTINGS */
.mediaCloud #keywordCloud { margin: -30px -15px -30px !important; }
.mediaCloud #textCloud { margin: 40px 15px 30px !important; }
/* FLEXILE > PORTAL > TWITTER SETTINGS */
.EWRporta_Portal #twitter .twtr-widget { margin-top: -5px; }
Also, everytime I update my skin, it wipes out EXTRA.css... I don't think this is normal.
The first way. Extra color styles should be installed as a child to the created child of Flexile.Just one more from me regarding this.. The extra color style - should these be installed as child to the created child of Flexile..
<snip>
Awesome, these will be included in the next update. If anyone wants/needs the fixes now, you can add the posted code to EXTRA.css.Erik, good work as always... I just got a chance to look at the "Enable support for 8wayRun addons" option... and I have a few changes for you which have been made to my addons...
<snip>
Ok, will do. Didn't realize it had such a large effect there.And I still think you should increase the sidebar width to 260 pixels. It does make a difference, as for the "member" blocks which use avatars (on the members page). With the default skin, it fits 4 users perfectly. With the default width of this skin, it fits only 3, and has a large open space to the right. Setting the width to 260px will fix this.
Also, everytime I update my skin, it wipes out EXTRA.css... I don't think this is normal.
Did it just start doing this? The EXTRA.css template isn't included in the style file, so I can't think of any reason it would be wiping it out other than this being the default behavior of XenForo.I was worried if I'd ask it would be a stupid question, but I have the same issue.
Did it just start doing this? The EXTRA.css template isn't included in the style file, so I can't think of any reason it would be wiping it out other than this being the default behavior of XenForo.![]()
We use essential cookies to make this site work, and optional cookies to enhance your experience.