• When I created my child a backslash was stripped from my additonal CSS causing problems with the appearance of the theme. Has anyone else experienced this bug?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author J B

    (@johnpbloch)

    a backslash was stripped from my additional CSS

    Could you please elaborate? The plugin doesn’t use any backslashes in the generated stylesheets, so this might be an issue with the WP file editor. An interesting bug that I haven’t encountered either way.

    Thread Starter derekseabrooke

    (@derekseabrooke)

    The additonal CSS was as followed:

    #et-info-fax:before {
    content: “\e0fa”;
    font-family:ETmodules;
    padding-right: 2px;
    }

    #et-info-phone:before {
    padding-right: 2px;
    }

    @media (max-width: 960px) {
    .et_header_style_left #logo {
    max-height: 100%;
    width: 80px;
    max-width: 100%;
    }
    }

    This was a child of the DIVI theme if that matters.

    Plugin Author J B

    (@johnpbloch)

    Yeah, this definitely has nothing to do with Child Themify. You could try adding an extra backslash (e.g. content: "\\e0fa";).

    I’m going to mark this as “not a support request” since it’s unrelated to my plugin, but if doubling the backslashes doesn’t work, I’d encourage you to open another ticket on the forums to get to the bottom of the issue.

    Thread Starter derekseabrooke

    (@derekseabrooke)

    Not certain how you can rule out the plugin as this backslash was not present on the child theme after using it. It was easy to re-add but there was no flashing arrow saying your problem is here. Without the backslash the child theme did not perform properly. It seems to me that if your plugin did not clone the backslash with the theme it is the fault of the plugin.

    Plugin Author J B

    (@johnpbloch)

    The plugin is extremely limited in scope. It only creates the child theme files. Extra CSS is stored in the database. Child themify does not contain any code at all that performs a write operation to the database. Therefore it is categorically impossible for the plugin to have caused this change.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘backslash stripped?’ is closed to new replies.