• Skip to main content
  • Skip to forum navigation

StudioPress

  • Shop for Themes
  • My StudioPress

Forum navigation

  • Home
  • General Genesis Discussions
  • StudioPress Themes
  • Genesis Blocks
    • Genesis Blocks
    • Genesis Custom Blocks
  • Retired Themes
  • FAQs
  • Forum Rules
  • Internationalization and Translations
  • Forum Bugs and Suggestions
  • Forum Log In

Are You Using The WordPress Block Editor?

Genesis now offers plugins that help you build better sites faster with the WordPress block editor (Gutenberg). Try the feature-rich free versions of each plugin for yourself!

Genesis Blocks Genesis Custom Blocks

Customising Parallax Pro

Welcome!

These forums are for general discussion on WordPress and Genesis. Official support for StudioPress themes is offered exclusively at My StudioPress. Responses in this forum are not guaranteed. Please note that this forum will require a new username, separate from the one used for My.StudioPress.

Log In
Register Lost Password

Community Forums › Forums › Archived Forums › Design Tips and Tricks › Customising Parallax Pro

This topic is: not resolved

Tagged: custom css, parallax-pro, stylesheet

  • This topic has 2 replies, 2 voices, and was last updated 11 years, 11 months ago by PicciaNeri.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • September 23, 2014 at 9:52 am #125432
    PicciaNeri
    Member

    Hello forum,
    I needed to customise Parallax Pro and I was lucky enough to come across Katrinah's great tutorial on how to safely customise a Genesis child theme.

    I've had no problem in following it – however, my site does not seem to be taking what I did into account and it's ignoring my custom.css file – but only for the changes, as it seems to know it's there and goes on the blink if it can't find it. here's what I did and what happens:
    – I have created a custom.css file and I have placed it inside the parallax-pro folder.
    – I have entered this code into the header:
    <link rel='stylesheet' type='text/css' href='http://piccianeri.com/public_html/fffdesignglobal/newff/wp-content/themes/parallax-pro/custom.css' media="all" />

    I have tested whether it's a problem with the code above: I have changed the path by removing /public_html/ and if I do so, then the site does not load at all, which means it is indeed trying to read custom.css. When I restore the right path, the site works again – but does not take into account the customisations I have made in custom.css.

    These are font customisations: so in order to test whether I had made any mistakes with the @fontface code or with putting my fonts into the right FTP folder, I changed the font in the style.css file to my font:

    h1,
    h2,
    h3,
    h4,
    h5,
    h6 {
    font-family: 'novecentowide-medium', sans-serif;
    }

    This works, so there is no mistake with my fonts.

    As a further check, I have then gone back to the custom.css editor in the dashboard and I have added a yellow background to the headings, but nothing happens.
    This is confirmed by the fact that when I go and inspect, it's reading the style.css file for the elements I've modified, and not the custom.css file. Yet this must be active, because if I change the path in the header, the site won't load.

    Can anyone help? it's doing my head in. I also add that I use the Busted plugin to make sure that the browser loads the most recent styles.

    Thank you in advance from Piccia.

    http://www.fffdesignglobal.org/newfff/
    September 23, 2014 at 12:02 pm #125451
    jbergen
    Member

    Hi,

    I'm wondering if the link you put in the header is correct. What if you tried this:

    <link rel='stylesheet' type='text/css' href='http://www.fffdesignglobal.org/newfff/wp-content/themes/parallax-pro/custom.css' media="all" />

    The reason I suggest this is because, when I go to the style editor for http://www.fffdesignglobal.org/newfff/, a custom.css does appear, but it's not CSS. It appears to be the code for http://piccianeri.com/newsite/.

    If that doesn't work, do keep in mind that making a separate custom.css file isn't absolutely critical. I used to think that making a custom.css was the best way to modify a child theme, but Susan recently responded to a post and explained that it's actually okay to simply modify the child theme's style.css directly.

    Jamie


    Jamie @ Ladebug Studios

    September 23, 2014 at 12:16 pm #125453
    PicciaNeri
    Member

    You GENIUS.

    THANK YOU.

    I thought I should use the path for where the custom.css file physically was – but you are right. It now works.

    Thank you very much also for the link to Susan's response. Also, I would think there would be other ways of restoring modified CSS should it be wiped out – for instance, you could keep a copy of your style.css file locally.

    However, another mystery has been solved for me, and for that I am grateful.

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
  • The forum ‘Design Tips and Tricks’ is closed to new topics and replies.

CTA

Ready to get started? Create a site or shop for themes.

Create a site with WP EngineShop for Themes

Footer

StudioPress

© 2026 WPEngine, Inc.

Products
  • Create a Site with WP Engine
  • Shop for Themes
  • Theme Features
  • Get Started
  • Showcase
Company
  • Brand Assets
  • Terms of Service
  • Accptable Usse Policy
  • Privacy Policy
  • Refund Policy
  • Contact Us
Community
  • Find Developers
  • Forums
  • Facebook Group
  • #GenesisWP
  • Showcase
Resources
  • StudioPress Blog
  • Help & Documentation
  • FAQs
  • Code Snippets
  • Affiliates
Connect
  • StudioPress Live
  • StudioPress FM
  • Facebook
  • Twitter
  • Dribbble