jkshay

Kathryn-

Thanks so much for the follow up! I just implemented your suggested changes and reverted to the enqueued child theme method with no issues.

I really appreciate it!

Thanks, Kathryn. Removing the enqueuing method from functions.php and adding the @import line referenced above to my style.css DID fix the tiny icon issue and lets me keep the blue theme options color.

I’m interested to know what the developers might have to say. From what I understand, the enqueuing method is faster. Is this correct?

Thanks for the reply, Kathryn. Adding the priority 11 like you suggested DID fix the tiny post icon issue. However, it also completely overrides the Theme Options –> Color Scheme setting. Regardless of the chosen color (I use Blue), the theme only renders the turquoise color.

Any advice?

Thanks,

Jonathan

Aack! I spoke too soon. While I *did* get my main menu to begin appearing on category pages, I lost my members-only secondary menu. The secondary menu works – if I assign it as the secondary menu (non-members-only), then it appears. However, this menu needs to be members-only. Assigning this menu to “Secondary Menu – Members Only” does not cause the secondary menu to display when I’m logged into my site. I’ve removed the association between this menu and the menu location several times, hoping that it might eventually “take”… to no avail.

Any ideas?

After following the tips at this post with limited success, I started thinking about WHEN exactly I last saw this work properly.

I had recently made some changes to my site by installing a VideoWhisper plugin and a Wiki Lite plugin. I didn’t end up using either, and decided to uninstall both of them.

I first uninstalled Wiki Lite, and saw no changes. I then deleted Wiki Lite and saw no changes. I followed this with an uninstall of VideoWhisper – still no changes. Finally, I deleted the VideoWhisper plugin files. SUCCESS! I finally got my menu back on my category pages.

For the record, since I was not able to successfully resolve this using the aforementioned post, I completely removed any additions to functions.php and category.php made during that attempt.

I don’t know if it was the combination of removing both of these plugins, but I specifically thought about these plugins as culprits because I had a hunch that the issue was related to grouping articles by type (article), and both of these plugins created custom types.

I had the opposite problem as booth_1 – I wanted to hide the number of subscribers. I tried [jetpack_subscription_form show_subscribers_total="false"] based on inverting Jeremy’s suggestion above, but had no luck.

I modified the jetpack/modules/subscriptions.php file and added echo $show_subscribers_total; and saw that it was outputting a 1.

I then tried [jetpack_subscription_form show_subscribers_total="0"] and successfully hid my subscriber count.

Wanted to point this out in the event anyone else ran across this issue.

Vitaly-

I want to thank you for your prompt replies to my queries and the expeditious manner with which you produced both versions 1.4 and 1.5 of your plug-in.

I’ve implemented 1.5 on my site and updated my article accordingly.

Again – THANK YOU.

I took the liberty of converting this forum post to a blog post on my site evangelizing about Anti-Spam – I hope that’s OK.

You can find the article here.

Thanks!

ChrisColston-

I too made the same assumption that changing Settings–> Reading–> For each article in a feed, show… from “Full text” to “Summary” would produce summaries of my articles on my home page. I’m migrating from Drupal to WordPress and had this functionality on my Drupal-based site.

It has come to my attention that this setting is actually for RSS feeds, and therefore changing this value would not by default change the appearance of articles on the blog roll.

Regardless, glad to see you got a solution to your problem. I think I’ll be implementing this same solution.

IE was still ignoring the style setting, so I had to modify my table cell tag as such:
<td valign="top" class="home_page_table_text">

Using Chrome Developer Tools, I noticed that my table cell was inheriting a “vertical-align: baseline” setting from the parent theme’s style.

I added a “home_page_table_text” class to my table cell:
<td class="home_page_table_text">

and an appropriate entry in my child theme’s style.css:

.home_page_table_text {
vertical-align: top;
}

And now my text is properly displaying at the top of the cell adjacent to the slideshow.

Andrew-

Many thanks for your assistance with this issue. In straightening out my CSS, I realized that the sub-menu items had a padding-top and padding-bottom value being set. Overriding that value indeed shrank my submenu items as desired.

Again, thanks!

I only added the !important when it didn’t seem to work without it – as if it were set as !important in the parent theme.

Sadly, adding your suggestion as the last line in my child theme didn’t seem to take any effect.

I need to go through my custom theme settings, ensure that I’ve got everything ordered properly, then I’ll post my child style.css for analysis.

Thanks!

My apologies – after your last post I was changing my themes around so you may have experienced one of the undesired themes.

My child theme’s style.css is indeed in play (I assume) because I’ve successfully changed my menu’s font color, main menu item height, background color, etc.

Try again at https://www.lisakarenward.com/newsite2/wordpress and you should see white menu text on a black background with minimal space above and below the main menu items. It’s the submenu items under the main menu item “GALLERY” that I’m wanting to reduce in overall height.

And thanks again for your assistance! ??

My custom theme is a child of twenty twelve. If I remove my entire custom theme’s style.css contents, I receive a “theme broken” message. If I implement just the code to inherit the parent theme’s style.css, then my gallery submenu still appears the same height as in my custom theme. If I change my theme to the twenty twelve standard theme, then my submenu still appears thicker than I want, and appears in height identical to my child-theme’s style.css-driven submenu.

In a nutshell, it doesn’t seem like removing my child theme’s style.css made any change in my sub-menu appearance.

I’m no html programmer (C# .NET for me), but my understanding of css is that settings that appear lower in the css file are the most recently applied styles, and that adding !important to a style should apply that style, disregarding any settings it may have inherited with regards to that property – such that the last line in my custom style.css being

#masthead .main-navigation li.menu-item, #masthead .main-navigation li a, #masthead .main-navigation li ul, #masthead .main-navigation li ul li, #masthead .main-navigation li ul li a {
height: 30px !important;
line-height: 30px !important;
}

should override any inherited settings for these elements with regards to the properties in question.

Is my basic understanding of CSS wrong?