Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • @dasfgh:

    I found it! Strangely, it is related to hotlink protection. I turned on “Allow direct requests (i.e., entering the URL of an image into a browser)” in cpanel if someone needs it.

    OMG, thank you, thank you, thank you!!!

    I have been tearing my hair out over this issue for three weeks, and tried dozens of other suggested “fixes” to no avail. This finally resolved it for me.

    I hope your life is filled with candy and flowers and all manner of other wonderful things, because you TOTALLY ROCK. Thank you again.

    +1 for the metric/imperial system switcher.

    And just to clarify, what I’m really hoping for is what I would call a “view switcher” (as opposed to a converter).

    When I develop and test a recipe, I create two versions – one metric, the other imperial – each with “friendly” measurements and directions tailored appropriately to the system. The only way I’ve found to publish both versions online (each with microdata tags) is to create a completely separate post for the “alternative” version. With the result that, even though they are in fact the SAME recipe for the EXACT SAME THING… the database thinks they’re different. Which means page hits and “Likes” are counted separately, even though they should really be aggregated.

    Meanwhile… it’s anyone’s guess what Google thinks the alternative pages are, but I can’t help thinking that this method probably creates a serious “duplicate content” problem in terms of SEO.

    In my IDEAL world, then… I would be able to create ONE recipe with two different VIEWS (i.e., the metric version being one view, and the imperial version being the other). In some obvious location – perhaps next to the “print” button – there would be a nice little link that says something like “Click Here for Imperial Version.” Naturally, I would like to be able to choose the wording of this text myself. And of course I would like to be able to set the DEFAULT view in the plugin settings, but have the option to change it on a per post basis as well.

    Finally (icing on the cake here), irrespective of which view I set as MY default, I would LOVE it if my readers could have the option to set a cookie or something so that their computers can remember THEIR preferred setting.

    Thanks for listening!

    I have the same question.

    I’m having the same problem on two of my three sites. All three sites use the same custom theme (a custom child theme running under iThemes Builder). The site where I can see the Appearance>Widgets menu item properly is a brand new WP 3.5 install. The two sites where I can’t see the Appearance>Widgets menu item were upgraded to WP 3.5.

    Interestingly (and maybe this will work for you, mmarkym), I discovered that if I get out of the dashboard, the Widgets menu item DOES show up when I hover over my site name using the Admin bar. Kind of an annoying workaround, but at least I can get there now.

    And The Answer Is…
    The readme.txt file (inside your twitter-widget-pro plugin folder) has a TON of good information about using and styling this widget. Sample CSS snippets start on line 73.

    You can add custom CSS rules to style the widget right in your theme’s stylesheet. You can use style.css (assuming you’re using a child theme that won’t be overwritten). Or, if you use a custom css file for modifying your theme, you can use that.

    My personal practice is to simply create a section called /* PLUGIN MODIFICATIONS */ at the end of my theme’s stylesheet. I keep the custom CSS rules for ALL my plugins in that section. It’s very convenient for editing, plus having it all in one place means I never have to go on a time-consuming witch hunt for rogue code that might be hiding… anywhere… due to previous edits in other files that I’ve long since forgotten about.

    @owen984: Actually, this IS the “ideal solution,” and a MUCH better practice than editing plugin files directly. Why? Because any edits made directly to plugin files will be automatically overwritten every time the plugin is updated.

    Bonus Suggestion:
    If you don’t have the Firebug AddOn for Firefox (or Firebug Lite for Chrome), get it and spend an hour or so on YouTube learning how to use it. Seriously. It will save you enormous amounts of time and aggravation. Firebug can show you INSTANTLY exactly what classes/ids you need to target. It has live preview functionality so you can test modify your CSS rules directly in your browser without actually touching your stylesheet (thereby ensuring you’ll get what you want with no unintended consequences). Once you’re happy with your tweaks, it’s just a matter of copying and pasting the revised CSS from your Firebug window into your theme’s REAL stylesheet.

    Happy WordPressing!

    I would like to know how to do this, too.

Viewing 6 replies - 1 through 6 (of 6 total)