WordPress.org

Ready to get started?Download WordPress

Forums

TubePress
style sheet and img issue (3 posts)

  1. carlytx
    Member
    Posted 1 year ago #

    Using Firefox Firebug we checked the performance of one of our sites and noticed the following 2 404 (not found) errors:

    http://oursite.com/wp-content/plugins/tubepress/sys/ui/themes/default/style.css?ver=3.5
    
    http://oursite.com/wp-content/plugins/tubepress/sys/ui/themes/default/img/bullet.png

    First error: We integrated the CSS for tubepress into our standard style.css and as per the documentation were under the impression that the use of CSS by tubepress was deprecated.

    Second error: We checked and we do not have an IMG directory under the DEFAULT directory in the tubepress plugin directory. So we don't know why it is searching for the .png file there.

    The code in the header for this site is

    <link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); ?>" type="text/css" media="screen" />

    we are using the latest version of tubepress.

    http://wordpress.org/extend/plugins/tubepress/

  2. Eric
    Member
    Plugin Author

    Posted 1 year ago #

    Hi,

    wp-content/plugins/tubepress/sys/ui/themes/default/style.css

    for TubePress 2.4.5 and below, this path is valid and should return a 200. The use of custom CSS in user themes is indeed deprecated, but this version of TubePress still uses this stylesheet to do the bulk of its styling. If you customize TubePress's CSS, you should only put your *modifications* into your theme's style.css. Not the entire TubePress stylesheet. Does that make sense?

    wp-content/plugins/tubepress/sys/ui/themes/default/img/bullet.png

    This looks unfamiliar to me. I'm guessing that it was added by someone that had customized TubePress? Probably safe to get rid of that reference if everything else is looking good to you.

  3. carlytx
    Member
    Posted 1 year ago #

    thanks. We will clean up the first issue.

    We will have to figure out what happened with the second issue. We are not sure where the call is coming from for that .png file.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic