Yup, exactly!

The posts have the image set as featured image and not just an image in the article?

Show featured image is turned on under post settings in theme panel?

Cache is cleared?

• This reply was modified 11 years by TheMediumUTM.

If you mean the footer widget area itself, right above the copyright bar at the very bottom, the footer section of the theme panel gives you a full-width option.

If you mean above the footer widget area, you could add a row in the visual editor, and then add a widgetized sidebar element (without splitting it into columns). Create the sidebar (https://forum.tagdiv.com/sidebars/) if you don’t have one.

Unfortunately, this is on a page-by-page basis and I’m not sure how else you could do it, since you can’t have the footer widget area be split up and full-width at once.

Hope that helps!

I found that when my big slider wasn’t working, it was one of two things: (1) I confused “last 7 days” with “latest” and ended up with too few in posts eligible to be displayed, or (2) I had divided the slider’s row. It never displayed for me when it wasn’t in a 1/1 row; not sure if it’s supposed to. Anyway, that might help.

+1

Any idea whether this is possible?

P.S. Similarly, right now I’m organizing the homepage as a large featured area on top, then individual category blocks scrolling beneath that. I don’t care if the posts are unique between the featured area and the individual category blocks. But if I want to have two different blocks making up that featured area, I do care if the articles unique within those. I can’t use offset if I set it to random, and I can’t use unique because that would affect the whole page. So another feature request would be to have articles be unique between a given set of blocks… 🙂

Did the latter, problem solved 🙂

Oh, I … I see … it’s associated with the meta key td_post_theme_settings in a serialized array value, e.g. a:1:{s:11:”td_subtitle”;s:25:”some subtitle text goes here”;} … Welp, I’m lost.

I guess I could just alter my various single pages to use my own field instead, right?

• This reply was modified 12 years by TheMediumUTM.

I too am in favour of hex colours in shortcodes 🙂

Until an option is added to the theme panel, you can style it yourself via custom CSS. Either do this through a child theme (https://forum.tagdiv.com/child-theme-documentation/) or through the custom css part of the panel.

Using “inspect element” on a widget reveals the classes involved. For the titles it looks like it’s .block-title. The class of a widget’s text often varies from widget to widget, and I’m guessing from stack to stack. In blog-stack, for example, a text widget’s content is class .blog-stack .textwidget.

For the second one, note that when looking at a row in the visual editor, the tab that allows you to divide it into columns also has a “Custom Layout” link in which you can enter your own ratios: http://www.screencast.com/t/maAkRnRv2

For the sidebar by the text box above the footer, breaking the row into two there and making the right side a widgetized sidebar is also an option.

Meanwhile, this custom CSS(or that for a similar menu, not sure if it varies by stack) would allow you to vertically adjust the height of the text in the menu:

.sf-menu {
padding-top: 5px;
}

Change the 5px, of course, to whatever works. Note that line-height (from custom typography menu in theme panel) would also work but would not change the search button height.

For spacing you can add padding to the list items:

.sf-menu li {
padding-right: 15px;
}

You could use custom CSS, in the theme panel, for the stroke. A quick “inspect element” check suggests that the logo area is td-menu-background. A stroke would be a border. In the blog-stack style I find this class actually has “border-top 1px solid #ebebeb” already. Just change or add that class to have a border-top of whatever colour, style, and thickness you want.

Thanks!

Well, I’ve created custom fields with the plugin and displayed the values in a theme, so I’m somewhat comfortable with it. But when I found the above code yesterday and created a custom field with fieldname td_subtitle, it seemed like it didn’t actually update when I saved the post. I guess because the post settings box is also saving the value? Or something? Maybe this is the difficult part…

Perfect! Thank you so much!

Fixed by switching to a different theme and back.

Video demonstration: http://youtu.be/rOFd4siBrXw

On the same category as the dropdown you’re looking at, both text and background of the dropdown are the same colour. What might cause this?

For the second one, this plugin might be helpful: https://wordpress.org/plugins/list-pages-shortcode/

Thanks! I’ve been playing around with these settings, but there’s still some unusual behaviour. It seems to be when looking a parent category archive page, and clicking the dropdown for that category, you get the background and link colour being the same. Here it is with some ridiculous colours for testing:

http://building.mediumutm.ca/jj/colours.png
http://building.mediumutm.ca/jj/dropdown.png

When you download the theme, inside the zip file is a folder called “plugins” which contains the speed booster plugin. To install a plugin by uploading, go to Plugins -> Add New -> find the “this page” link in the first sentence -> upload the plugin zip.

I guess you have to try to recover your Envato account for the other question… since you’re able to log in here, at least your licence number for the theme is stored in this account somewhere, I hope.

That’s the big slide format, which is one of the options when you’re editing a post or page, in a box called Post Settings or Page Settings or something. The big slide takes the latest posts from a category and automatically formats them like that.

This is sadly out of date now that 4 is out, I think.

I wish there were just some easy guide like this:

“So you want to use Co-Authors Plus to have as many Newspaper-theme author boxes as there are authors.

1. Go to your theme editor.
2. Find the file …
3. Find the lines …
4. Replace with / add the lines …
5. Profit!!”

Yup, that’s how child themes work. They inherit from the parent theme except for what you’ve added in the child theme files. Updates to the parent theme are still reflected and everything, but your child theme modifications will still survive updates. 🙂