Forum Replies Created
-
-
Never mind, we ran a backup then updated the theme normally from inside the WP-ADMIN dashboard, and it worked just fine.
Closed issue.
@sharmstr – OK, almost there. Here’s the problem:
.btn-default {
color: #cccccc !important;
font-family: ‘BlairMdITC TT-Medium’;
font-color: ‘#990000’ !important;
font-style: ‘bold’;
}Apparently ‘font-color’ isn’t valid css, only ‘color’ is for text, so the correct font is now displaying, but it’s grey in color just like the buttons. Ergo, you can’t read the text.
I’m wondering how we style that font so that it’s #990000, and shows up legibly on the buttons.
@sharmstr – OK:
Here’s exactly how we have the css set up:
btn-default {
color: #cccccc !important;
font-family: ‘BlairMdITC TT-Medium’;
font-color: #990000;
font-style: ‘bold‘;
}Here’s exactly how we’re calling a button:
[kleo_button title="What You Get" href="http://www.myselfdefensetraining.com/self-defense-training-what-you-get/" target="_self" size="lg" style="highlight" el_class="btn-default"]
So, it’s (correctly) displaying the grey for the buttons, but it’s not displaying the font, the font style, or the font color. What are we doing wrong!?!
@sharmstr – ok, we added in our css blurb to the ‘quickCSS’ area in the theme’s general settings, and are calling the buttons like so:
[kleo_button title="What You Get" href="http://www.myselfdefensetraining.com/self-defense-training-what-you-get/" target="_self" style="highlight" size="lg" el_class=".btn-default"]
But, our buttons are still showing up as red, not grey as we’ve defined them in the CSS. Are we doing the shortcode configuration correctly?
@sharmstr – I’m not the best with CSS, and am wondering if we can use hex values to define the button color and the button text color, like so:
.btn-default {
color: #cccccc !important;
font-family: ‘whatever’;
font-color: #990000;
}Sure, right here, @Radu :
http://www.myselfdefensetraining.com/awesome-enrollment-options/
See the four tabs below the first image? I’d like to figure out how to make each take up 1/4th of the width instead of being all stacked up in the center.
Hey, @Laura – just wanted to say thanks a lot for checking in to that. I figure it was some kind of a conflict with two different flavors of jQuery or something. Your fix totally worked, and the best thing is we didn’t really need that, it was just kind of cool to do jQuery slides down a page to anchor text, but we can totally live without it.
And to answer your question, @Laura – no: WPEngine is a managed solution that does not allow cPanel access. We can give you an FTP login, we can get a copy of the .sql for you, beyond that…
You already have admin access. Do you need access to phpMyAdmin or something? Why would you need cpanel access to answer our question about this theme? That’s Linux admin stuff, which you do not need.
We can add you in as a user on WPEngine, and that’s it.
Why are our tabs and accordions not working. We’re getting really upset here.
@Laura – that didn’t work. Here’s what WPEngine said:
“Michael Clayton
Thanks for waiting…. looks like your problem isn’t caching here. If you notice, the screenshot shows the error as “404 not found”. I checked the path on our server and those files do not exist. So there’s nothing to exclude because there’s nothing there.”So, are there scripts we’re missing? Why would those not be in our Kleo installation? Is there something we need to add to get accordions and tabs working?
@Andrei – well, all we really need to do is have a unique full page background image for each page. Is there a better (read: easier) way to do that than in QuickCSS?
@Andrei – maybe I’m not describing the problem correctly. We have custom CSS that’s discreet to specific pages, so adding that CSS in to the QuickCSS or to that one style.css file isn’t going to cut it.
Kleo/VisualComposer has a spot for custom CSS that’s specific to one page (in the ‘gear’ icon near the top of the visual editor), but adding our CSS in to that area when editing a page does not succeed in styling the page.
Gotcha – we put it in Quick CSS, and that seems to solve the problem site-wide.
That’s weird with those 404’s. We just put the kleo-child theme in place this morning, which looks like…that’s where page-press-kid.js is being called from, right?
“also, your site is throwing 404 errors for page press jquery in your child theme.”
Ummmmm, ok – what are we missing that would throw that error?
Oh, also – shouldn’t we add that CSS in to the child theme’s custom css area in general settings, @sharmstr ?
@Laura – We have many front end pages that are custom CSS, the css is unique to each page. Our home page, for instance, has a different style than our ‘bio’ page. We are essentially doing a CSS include on each of those pages, as some have different backgrounds (and other style elements) than others.
Ok, that totally worked – just had to change the name of the container in the CSS. You are a ROCKSTAR, @sharmstr !!!
Drat – I’m not seeing any radio buttons in there (screen shot attached). I do see the ‘visibility’ field though.
Am I lookin’ in the right place, @sharmstr ?
Right, but we’d be applying this to the ‘visibility’ field in each menu. So, @sharmstr , what would we want to include in that field if we wanted to display it to bp users only?
You’ll forgive me, I’m far from being an expert with procedural logic…
Ok, @sharmstr – just to be clear, we’d do something like:
! bp_is_user()
to HIDE a menu from a buddypress user, and
bp_is_user()
to SHOW it to someone who is a buddypress user, correct?
