Foxy Forum Status

We're no longer responding to questions via our forum, but we will keep it up for historical reasons. If you can't find the answer you're looking for, please visit our knowledge base or contact us. If there's enough interest in the future, we may bring the forum back.

Checkout Template CSS Trouble

varsitypixelsvarsitypixels Member
in Help edited May 2013
Hey Everyone,

I'm having an issue with creating a custom checkout template. The FC CSS seems to be overriding my custom CSS for the site...adding bullet points, and clearing floats....long story short, I can't seem to figure out what I'm doing wrong.

Please take a look here:

Please notice the CSS (almost done) on that page, then add something to the cart and click checkout....

At that point you'll notice that the CSS has left for crazy-town.

Is it possible that the FC CSS is being loaded after the main css and overriding everything?

Is this just a standard starting point that everyone begins their custom FC CSS from?

Cheers, and thank you in advance for any help you may be able to give. :)
  • fc_adamfc_adam FoxyCart Team

    Looking at your checkout, I'm not seeing any default FoxyCart styles overwriting your own stuff - in fact, there isn't really any FoxyCart styles present on your page, as the default text stylesheet isn't being included properly. For some reason there are some special characters being included in the tag that is breaking it, like this:
    <link rel=&#8221;stylesheet&#8221; href=&#8221;; type=&#8221;text/css&#8221; media=&#8221;screen&#8221; charset=&#8221;utf-8&#8243; />

    If you cleaned that code up have the correct quotations, that should clean up the styling of the cart/checkout form a bit. In terms of your own styling, have you been recaching and resaving your checkout template as you change your own stylesheets? The templates will need to be recached and saved after each change you make to the template or its associated stylesheets.
  • Thanks Adam...I'll mess with that and head in that direction for a bit. I'll keep you posted.

    I appreciate your assistance. :)

  • Adam, I'm struggling with this...and loosing steam.

    I was able to get FC to use its CSS...just simply by trying over and over to cut and paste it properly in the wordpress post. Its seems that wordpress was converting the quotation marks in the css link into odd characters.

    But my issues with the sites main CSS being cancelled out still remain.

    I'll let you know where I end up at the end of the day.

  • Could the fact that my theme is a child theme and calls the twentytwelve css at the top of the style sheet be confusing the caching system?

    It looks like that call is mis-interpreted within the cached checkout template....and the css foundation that my child theme is built on isn't getting pulled in...

    In the cached template right at the start of it pulling in my CSS... you'll see:

    <style type="text/css" media='all'>
    /* <![CDATA[ */
    /* Pulled from _ */
    Theme Name: The Varsity Pixels Nemesis Theme
    Description: The Varsity Pixels Nemesis Theme.
    Author: Varsity Pixels & Aaron Adams
    Author URI:
    Template: twentytwelve
    Version: 1

    /* @ IMPORT START: from _ */
    /* ERROR: The CSS file returned a code of 404 */
    /* @ IMPORT END from _ */

    Then my custom css comes in normally....

    What'cha think? Is this a common Wordpress integration issue?
  • Instead of the caching system, could I force some of this from within my functions.php file? that might be smoother....
  • fc_adamfc_adam FoxyCart Team

    Interesting. Our caching system does support input tags as long as it's a top level input - we don't support an import within an import, which doesn't seem to be the case here.

    What looks to be happening is that instead of going up one level in the import to the themes folder, it's going up to the wp-content folder, making the path for the file incorrect.

    For now, if you manually include your twentytwelve stylesheet in your checkout template, that will get things working. We'll dig into what might be happening with the include there that would be making it include incorrectly.
Sign In or Register to comment.