Search Results for 'child theme'

Not using a child theme, nope.

That’s fine, thanks for your help so far!

are you using the child theme?

I’ve got to head out for about an hour. I can help more when I get back.

Stefan
open Style.css in the newspaper-child

in Template, change it from 009 to Newspaper

Before
Template: 009

after
Template: newspaper

and it will 100% work 🙂

Hello, the update to 3.0.1 on the child theme to activate it loses the CSS style I can do to fix it?
Thank you!

Yes sort of – see my other topic about this – https://forum.tagdiv.com/topic/top-menu-bar-colour/#post-6012

I had to add to me child style sheet and set the same bg colour as the theme options panel bg colour.

Yes I do have other plugins.

It seems that the css was loading my custom theme options settings after the default css was already visible for a second. Not sure if that makes sense.

I added the top nav bar, and the main nav bar colours to my child style sheet so the effect is hidden. (i.e.. nav bar starts blue instead of grey so we don’t see it ‘change’).

Still on my home page – I see my headings change from a large font down to the smaller size chosen when the page loads. I imagine the same solution will work – but this means I am bypassing the admin theme panel all the time now.

so do you recon copying the footer.php to the child theme and editing that would be the best way to do this ?

A mi me ha pasado exactamente lo mismo ¿?

Thanks for the update Radu,

I am very happy to hear that you are aware of the issues and that a fix is near release.

Hi, the “next” pages work on both of my sites running theme with only the core set of plugins (no Jetpack!), plus using AddThis, AdSense ads, and no insert of ads in content (only header + sidebar).

Usually this “error” is from modifying a page, using a child theme with a bad addition to the functions file, or a conflicting CSS element from another plugin.

On one of my old themes, I also had another navigation plugin running from a prior theme and forgot to turn that off, and so it broke it.

Not sure if any of that helps. But it does work properly on both our test magazine site and a live production site (2004 site updated for 2014 with this theme) without any trouble, which implies a local issue vs a theme specific issue.

On another theme I found going to the admin > settings > permalinks and resaving the permalinks actually helped. Which is bizarre, but there you go.

• This reply was modified 12 years by simchris.

Thanks!
Its a site I am developing on a sub-domain
http://develop.alltomtrav.info

Whats the best? To do it in original CSS or the Child Theme?

It seems that I can not get the Child Theme to work…

• This reply was modified 12 years by Stefan.

Hi, Radu
that would be awesome. I switched from using the child theme so as to not impact my pagespeed adventures, and so the custom CSS I put at bottom of style.css didn’t have an impact in the way the child/style.css did. Being able to tweak a few things here or there with either a custom.css file, or perhaps more appropriately these days a “hook” to drop some code in the head at bottom before the body tag (Woo Themes does this fairly well, btw; they have all these little ‘hook’ locations to drop in code, although it does add a slew of if/then crap; disclosure we’re trying to ramp up your theme to replace Woo Canvas!).

So for us to be semi-done and in full “go mode” my laundry list of stuff needed is simply:
1) Google async alignment in top bar
2) websafe fonts option – which would save me hacking that one
3) custom.css injection hook in head, to over-ride couple of minor things (like making the author box bio text size smaller, when making the post side larger so the author bio isn’t over-large from the base adjustment)
4) not critical; but option to have a local image for author box (add new user meta field for ‘author image’ — we used to do this on our in house theme, not difficult) to not pull gravatar and save some bandwidth from external site — if you wanted to wow the kids, you could add a “grab my image from gravatar” option 😉 Peeps love the “automagical” stuff.

Otherwise, for us — you’re done! I’m hoping the v3 won’t introduce new issues, but right now we’re very happy.

BTW: for ‘web safe’ fonts, Adobe came up with some really quite brilliant ‘stacks’ of the best font mix to use across Mac, Windows, iOS, Android, et al. They can be found in Dreamweaver, and possibly their help system – but if you need those, just let me know. Much nicer than the old skool ‘Helvetica, arial, sans-serif’ stack. 🙂

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

Ooops: one more.

For those who are testing for speed-speed-speed and want to fix all their “you could optimize image xyz” warnings. I actually wrote an article on this once upon a time on my old site no longer seen anywhere since it was behind a login.

BASICALLY:
1) backup all your images
2) install the wp regenerate thumbnails plugin
3) check your wp settings > media and make sure the S / M /L sizes match what is being used by theme so you don’t end up with more thumbs than needed (seriously this is the #1 mistake folks make with thumbnails in general)
4) add the following code to your functions.php file in the theme root at the end –or– in your child theme (TIP: stop using a child theme)
add_filter( 'jpeg_quality', create_function( '', 'return 50;' ) );
5) run the regenerate thumbnails plugin under wp admin > tools

Voila!~ go rerun your speed test with Google and magically no more “you need to optimize image xyz to save 5kb” crap.

If your images don’t look as sparkly as they did, you can always delete the thumbs, put your original images back, and then try changing the “50” to “60” if you prefer.

For all those thumbnails all over the place “50” is recommended setting, and this uses both the built-in function of wordpress for images which hooks into the image mod stuff on the server. UPSHOT: when you make this change to your functions.php file – ALL YOUR FUTURE IMAGE THUMBS will be compressed automatically.

No more extra plugin to do that unless you really want to.
Simple. Easy. Quick.

I second this emotion. I was actually trying to make the post story titles 48px and was limited to the 40px. I suppose simple fix is just adding css adjust for that at bottom of the main style.css ?

Since we’re not using a child theme, where *is* the best place to insert custom CSS ? I don’t think there is a hook to put custom style inline with the head to override the main style. I tried to over-ride something by putting at bottom of the main style.css, but I guess I need to do mods for each viewport section.

Thanks Christopher. I took a look at mod_pagespeed, but it doesnt look like it could do anything for me at this point. I’m already on a VPS that runs Plesk 11 with nginx as a reverse proxy. I’m letting nginx handle all php scripts and serve static and dynamic content. Gzip compression is enabled and i enabled browser caching through nginx with the expiration set to two weeks. I’m running WP Super Cache as well to create pre cached pages and i use EWWWW Image Optimizer to optimize all images. I also optimazed all theme and plugin images with that plugin. You might want to look it up, imo it really is a better plugin than smush.it and so. I use the simple minify plugin to minify all javascripts and i my pagespeed currently toggles between 85 en 92 for desktop, depending on my server response time and between 70 and 80 for mobile. The only red warning i still get is to defer javascript and css (moste google fonts, and 3 theme css files: bootstrap, style.css and child theme style.css) to below the fold, but i have no experience on how to do that. Im really pleased with the pagespeed right now, but more tips (besides using a CDN) are welcome!

Thanks for you responce anyway 🙂