[NSFW] Custom theme: CSS being 80% ignored?…

  • Resolved shawncbarry

    (@shawncbarry)


    11 years, 8 months ago

    I did a quick search but couldn’t find any posts about this exact issue. I’m creating a custom theme, using this blank theme: https://github.com/shawncope/blankSlate-theme (I understand no one at WordPress offers support on custom themes).

    Using this blank theme, I’ve completely replaced the css file, from top to bottom. There’s none of the CSS from this theme fighting against mine – it was completely purged. My CSS files are fine, and I built the site in static HTML5 and CSS first, and it’s all fine. I also deleted all the php template files from this theme that I didn’t need using only the wordpress files like footer.php, header, etc. It’s my understanding that it wouldn’t affect the CSS anyway.

    My theme simply gets the header, the footer, the sidebar, all which contain my html elements with the classes I’ve styled, and I use my own template files and custom fields to get the content to the page. I’m not using the WordPress content fields inside the admin panel to send any HTML to the browser. I also have another site I built the same way previously that works fine.

    This site, however is just flat-out collapsing. It reads the fonts from my CSS ok, and one or two elements seem to be styled properly, but the rest just goes south, completely. I checked the page source, and it appears that all the classes are being output to the browser properly, but the information in the CSS is being mostly ignored, but not completely – that’s pretty confusing. I know the CSS file is being called, because some elements have the proper colours, widths, etc. Only a couple though. I find that really weird.

    NOTE: I develop adult-content sites, so before I post any links, I’d prefer someone volunteered to have a look with the understanding that the content is adult. I thought to start by describing the problem first to see if this was something anyone recognized as a common problem they could point me in the right direction on.

    Thoughts, anyone?
    Shawn

Viewing 9 replies - 1 through 9 (of 9 total)
  • Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    It’s okay to post adult links if you label them with [NSFW], which stands for Not Safe For Work.

    Thread Starter shawncbarry

    (@shawncbarry)

    Yes, I understand that, thanks Andrew. Just thought I’d begin with that information. I’ll just go ahead then.
    (note – this is NOT my content. IMHO, “dirty panties” belong in the hamper. However…)

    [NSFW]
    Here is the static design for the homepage. All the content is for position only – the real content would be added after the CMS is up-and-running:

    https://kookoo4panties.com/development/home.html

    Here’s what’s happening with the same css code, through WordPress (this is just the header and sidebar, so far:

    https://kookoo4panties.com/CMS/

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Do you have a screenshot of how the website should look?

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Or should it look like the static design?

    Thread Starter shawncbarry

    (@shawncbarry)

    It should look like the static design.

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    I think the issue is the syntax error on the comment just above your nav styles.

    You have these dashes;

    -------------------------------------------------

    But they’re not within CSS comments;

    /*      */

    Either remove them or put them within the comments.

    Thread Starter shawncbarry

    (@shawncbarry)

    Oh man …I thought I’d put those inside the comment parameters. That’s what happens late at night.

    Thanks for the second set of eyes, my friend.

    Shawn

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Glad you sorted it.

    Thread Starter shawncbarry

    (@shawncbarry)

    Yup, got it (see my comment above).

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[NSFW] Custom theme: CSS being 80% ignored?…’ is closed to new replies.

Tags