Forum Replies Created

Viewing 9 replies - 16 through 24 (of 24 total)
  • The widget has disappeared for me too

    Thread Starter Andy Leppard

    (@andyleppard)

    One of the rich-editor fields that are in my repeater series has an ID of:
    id="wysiwyg-acf-field-field_5289f6eeb3725_0_field_5289f7f3b3729-528b28b4ab2ac"

    This may not be the easiest of fields to target by ID. Might a useful alternative be to target fields by type, eg textarea?

    I’m also not able to save the option to:

    Exclude post X from categories A and B when A or B is excluded

    I would like to be able to colour table rows based on an entry’s field values.

    It’s a nice little plugin, but the CSS causes headaches I don’t need, so it’s disabled for the time being.

    BTW there’s a spelling mistake in one of your classes: .attachement

    Keep up the good work!

    Hi, yeah, I’d like to second this – you just need to prefix your CSS with your plugin-specific class:

    /* Document attachment widget style sheet */
    
    .widget_document_attachments .attachement {
      margin: 0;
      padding: 7px 0;
      list-style: none;
    }
    .widget_document_attachments li {
      padding: 2px 0 2px 25px;
    }
    .widget_document_attachments .powerpoint {
      background: url('../icons/pp_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .csv, .widget_document_attachments .txt, .widget_document_attachments .plain {
      background: url('../icons/txt_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .msword {
      background: url('../icons/word_icon.gif') no-repeat scroll 0 0;
    }
    .widget_document_attachments .pdf {
      background: url('../icons/pdf_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .excel {
      background: url('../icons/excel_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .gif {
      background: url('../icons/gif_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .png {
      background: url('../icons/png_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .jpeg {
      background: url('../icons/jpg_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .x-shockwave-flash {
      background: url('../icons/swf_icon.gif') no-repeat 0 0;
    }
    .widget_document_attachments .filesize {
      font-size: 9px;
    }
    .widget_document_attachments .description {
      font-style: italic;
    }

    Thanks Helga – I’d come to the conclusion that caching and browser-specific body classes are not mutually compatible.

    I’ve been using them out of convenience, not because they are the best method for browser-specific styles.

    Thanks for your input, and I have to agree that dropping them from Thematic is a good idea, just don’t drop any of the post, template or taxonomy body classes!

    @nicolas & @scott – I think we can call this one resolved.

    I’m using a child theme with Thematic and W3 Total Cache, and I’ve experienced the same issue as Nicolas.

    When Page Caching is enabled, W3 Total Cache serves a copy of the page which includes Thematic’s body classes from the instance when the cache file was first created – I see that after the cache has been emptied, then first viewing my test site in IE8 on Windows and subsequently viewing it in Mac OSX Safari, the browser specific body classes are defined as “windows”, “msie” and “ie8”.

    I’ve checked out the example site provided by sfrangos (https://bfgl.com), and this issue is not present – are you using Page Caching sfrangos?

    I use the Thematic body classes extensively to deliver page-specific styles, not so much for browser tailored css, but where I do , it’s usually quite important.

    Any update on getting the class added to the expanded question?

    It could be anywhere, so long as it can be targeted with css. Lovely plugin BTW.

Viewing 9 replies - 16 through 24 (of 24 total)