Search Results for 'css'

I see what you meant Ecofame and thanks for your reply. What I meant is that the new 4.3 version which came out at last friday should have fixed all the “space” problems, so you would not need the custom css code anymore. But unfortunately it didnt at least at my project.

Likely you could look at page source, find the classes for those blocks, then add some custom css to the theme panel to over-ride the size of those specific classes. 🙂

Could it be due to manually minified style.css file?

Oh okay… Sorry, I appologize for being rude to you. I thought you were someone who “worked” here (maybe with Customer Support), hence my frusteration and confusion at what you were saying at times.

Sorry.
Wait for Lucian or Marius to get in tomorrow.

I think they need to update that code on their docs page you’re referencing, which pulls list of the CSS and JS, which is what you’re looking for.

I don’t work here, just helping people as I’ve been doing webdev since 1994 and using WordPress since it launched in beta.

Sure, if you want to pay me to replicate the steps, would be happy to. “My” guide does not include those steps, as I NEVER edit the core code, and I only use compliant WordPress functions to optimize the functions.php file and well known suggestions for htaccess directives, etc.

I never made those instructions you refer to, so I’m going to pass on any help. Sorry to have offered; I likely only added to the confusion. Sorry about that.

I’m sure one of the other contributors here using that “hack” might be able to help. Likely you will want to post the question in that thread, as the hack you’re looking to do has nothing to do with theme support, or my suggestions for PageSpeed improvement.

Sorry, I can’t be any further help on this topic. Perhaps the person who suggested that hack might be able to help – try posting in that thread for help from those of us contributing suggestions for pagespeed improvements. Maybe the person who posted the hack will follow up for you on what he/she did to use that element you’re trying to use.

And again, the tagdiv speedbooster code and plugin has been updated for September, so the July hack may no longer work. But I’ve already said that, so I’ll stop talking now. 🙂

Not all fonts support 300 weight, as 400 is “normal” much like 700 is the normal strong/bold.

Likely you would want to edit the style.css file to specify the font and the weight you want; or over ride classes with the custom css box in theme panel.

For me, I opted to edit my style.css to specify the font to use explicitly and the font weight I wanted.

For Google fonts, you can check their font site to see which fonts actually support the 300 weight, and then you probably would need to call that font weight from either adding the Google css to bottom of your style.css file, or edit the functions or fonts file depending on version of theme being used, to call the 300 weight.

Hope that made sense, or at least points you in a good starting direction to make that modification.

Okay, well https://forum.tagdiv.com/pagespeed-guide/ is where I got this reference from, and it was suggested by “you” guys. The post date is July 20, 2014 which I would say is fairly new and should still be aplicable as of this date, as I see no reason why it should not be. And I’m sure if you bothered to replicate these steps to see what was wrong, we would be able to come to a conclusion already.

All I want is a fix for this. I’m following “your” guide to achieve removing render blocking css/js – using the TagDiv Speed Booster plugin as set out in: https://forum.tagdiv.com/pagespeed-guide/

I followed your instructions and it did not work. The only line of code that gives me a fatal error is “add_action( ‘wp_print_scripts’, ‘td_inspect_scripts’ );”. And that is also the line of code that enables me to see a list of all the ids for all the css and js (needed for the next step).

So I ask again, please help me get through this step successfully.

I never suggested adding that code to the functions.php file, so it might have been somebody else; obviously if it’s causing an error, it doesn’t work. That may have been posted by somebody using the OLD version of the theme and the OLDER version of the Tagdiv Speedbooster plugin, which has been recently updated, so that suggested code may no longer work. hence the error you’re getting.

Anything which tells you to edit core WP code should NEVER be done, in my opinion. “Generally.” But you know what you’re doing, so have at it.

Always check the DATE on any post which suggests changing theme code, in some way, outside of normal wordpress functions such as I use, and line that up with current date/version of theme and plugins. So, if something worked with v1 of a plugin, it might not work with v2 of a plugin, “generally” speaking.

• This reply was modified 11 years by simchris.

Okay… Well I just tried it with ALL the plugins deactivated and it still gives me the fatal error…

I’m simply following your instructions on removing render blocking css/js – using the TagDiv Speed Booster plugin by adding the code :

function td_inspect_scripts() {
global $wp_scripts, $wp_styles;
echo ‘registered scripts<br>’;
foreach ($wp_scripts->queue as $handle) {
echo $handle . ‘ | ‘ . $wp_scripts->registered[$handle]->src . ‘<br>’;
}
echo ‘registered styles<br>’;
foreach ($wp_styles->queue as $handle) {
echo $handle . ‘ | ‘ . $wp_styles->registered[$handle]->src . ‘<br>’;
}
}
add_action( ‘wp_print_scripts’, ‘td_inspect_scripts’ );

into Functions.php as you have stated… And “generally,” I do know what I am doing. I followed your steps to a tea.

+1 on all the great evolution of the theme. I, too, started with the theme back in2013, and have been very happy so far.

@Arved007
I “think” the new grid system might be based on Bootstrap 3, which allows you to do more things with column classes. The “old” 960/80 grid is now considered old by today’s standards. I haven’t looked at the new css file in depth, honestly.

I could be wrong, but BS3 has
750, 970, 1170 as the main containers.

That is part of the main WordPress install and not part of the theme, so I’d likely start by turning off your plugins, then turning them back on one by one to see if you still get that error.

You generally do *NOT* want to edit the core WordPress files inside admin, or includes, unless you know what you’re doing.

• This reply was modified 11 years by simchris.

Hi Sergenial,

All the white spaces are reduced as I wished and that is to thank for TheMediumUTM tha helped me a lot.

These are the codes I got from him and pasted in to theme panels costom css area.
————————————————————–

@media (min-width: 1019px) {
.span1, .span3, .span4, .span6, .span8, .span9, .span11, .span12 { margin-left: 20px !important; }
}
.td_mod_wrap .meta-info {
display: none !important;
}
.td_block_wrap { margin-bottom: 0px; padding-bottom: 10px; }
.td_mod_wrap { margin-bottom: 10px; }
.td_mod1, .td_mod2, .td_mod3, .td_mod4, .td_mod5, .td_mod6, .td_mod7, .td_mod8, .td_mod9 { margin-bottom:
10px!important; }
.td_mod_wrap .thumb-wrap { margin-bottom: 10px; }
.wpb_row { margin-bottom: 10px; }
.td_mod3 { min-height: 65px; }
.td-grid-wrap {
padding: 10px
}

Now I am happy with how the home page looks. There is only one problem and that is that the content-wrap has margin left.

here is my site:
http://www.ecofame.com

good luck
ecofame

This CSS code should fix ur problem…

.td-footer-wrap .td-grid-wrap {
padding: 0px !important;
}

Not sure about the double arrows.

The shadow is a CSS gradient effect and can be removed like this:

1. In single_template_3.php find the line <div class="td-post-header-full td-image-gradient"> and remove td-image-gradient

2. In single_template_4.php find the line <div class="td-big-slide-background"><div id="td-full-screen-header-image" class="td-image-gradient"> and remove class="td-image-gradient"

The class will no longer be applied to the image.

• This reply was modified 11 years by TheMediumUTM.