Any word on this, mehedi?

P.S. Looking at your live site again, minor CSS tweak suggestion:

.auhtor-twitter a {
  display: block;
}

This may not be necessary but it just drives me crazy when there’s a small spot you can’t click between the icon and the text 😀

Mine does work, and when I did “inspect element” on a working button I found that it’s not wrapped in <p> tags. On your live site, inspecting your button text shows that it is surrounded by <p> tags. But I’m not sure if those are there in your text editor or only because it’s not expanded in the first place…

I’m not sure what else it could be, sorry. :/ Official support will be back after the weekend.

The reason a WordPress shortcode isn’t rendered is often that it has formatting around it. Please check the shortcode in the text editor rather than the backend/visual editor and check which, if any, tags are surrounding it. Yours is bolded in that screenshot, which is a telling sign. Accidentally setting the shortcode as a header, or including it in an image caption div, could prevent it from being expanded.

Copying and pasting files is necessary but not enough to move a WP install.

WP is not just a bunch of files, as you might know. It’s a bunch of files organized by a database. In order to properly move your site, you need to find your database in your current host’s control panel, export all tables, create a new database on the new host, and import again, and then make sure wp-config.php is set to find the new one.

If you don’t know how to do this, someone here can probably walk you through it, but the first step might be to contact your hosting provider – old and/or new – and let them know you want to move a WP install. There are also many tutorials out there, including the official WP docs, but they’re a little hard to read on this point.

I’m just making that assumption that you might want that info, because the answer to this particular case is: featured images are not copies of regular image files (can you imagine the space they’d take up? :p). They’re pointers in the database, tied to each post. Specifically, the wp_postmeta table has the meta_key columns “thumbnail” and “thumbnail_id”, which tell WP which image is a post’s featured image.

But if you move your database properly, you don’t have to worry about copying and pasting individual tables. 🙂

I tried that with various values, and it made the desktop one usually break correctly, but mobile is questionable. I think I’ll just stick to default font size for now…

Thanks though!

I’m confused – style 5 already has no featured image. If you mean you want to have no feature image, and have the text be beside the sidebar instead of over it, you could use style 1 and not set a featured image.

If that solution isn’t appealling, hopefully official support can walk you through making a new template. 🙂

I think he means there are many users, each of whom will see it on their dashboard, and he doesn’t want them to see a message intended for admin like that. I’m not sure how to disable it for all users…

This is a very handy plugin for that sort of thing: https://wordpress.org/plugins/q2w3-inc-manager/ And there may be others like it that are more current, but this one was recommended by our ad providers.

Oh, gotcha. I thought you were hoping to get the lightbox working.

Not sure, will have to wait for tagDiv support…

Also, I hear bad things about some aspects of Jetpack, but its widget visibility component does make it easy to show/hide each widget on a per-post / category / date / etc. basis.

I was doing this recently and got that error when I had it link to attachment page instead of media file, or vice versa – can’t remember. Switching to the other option fixed it.

Hmm… I’ve never done this myself (create a new post template). Your blank page might have something to do with the content being loaded partly in single_template_#.php and partly in loop-single-#.php for each of these templates. Do you have all the parts you need?

P.S. If you’re going to repeat that code for each sidebar case, you can at least define a function in the same file. That is to say, have this at the top, in PHP tags:

function my_features_fields() { // No parameter because $post is still active

  // Update this list using the same format for all the field names you want
  $field_names = ['2g_network', '3g_network'];

  // Set up tabs
  $to_echo = '[vc_row][vc_column width="1/1"][vc_tabs]';

  // Set up features tab
  $to_echo .= '[vc_tab title="Features" tab_id="features"]';

  // Begin a list
  $to_echo .= '<ul class="features_list">';

  // Loop through the fields
  foreach ($field_names as $field_name) {
    $data = get_field_object($field_name);

    // Check if we have a value and set to a default if not
    if ($data['value']) {
      $value = $data['value'];
    } else {
      $value = 'No information on record.';
    }

    $to_echo .= '<li>' . '<span class="features_label">' . $data["label"] . ': </span>';
    $to_echo .= '<span class="features_value">' . $value . '</span></li>';

  }

  // Close the list
  $to_echo .= '</ul>';

  // Close the tab
  $to_echo .= '[/vc_tab]';

  // Close the tab group etc.
  $to_echo .= '[/vc_tabs][/vc_column][/vc_row]';

  // We have to filter the whole string to make WP interpret the shortcodes
  $to_echo = wpb_js_remove_wpautop($to_echo);

  // Output
  return $to_echo;
}

And then just have this one line wherever you want to place your tabs:

<?php echo my_features_fields(); ?>

Good luck getting the rest working! I’ll stop checking this thread shortly, but it’s been good.

I have the same issue with relevance; maybe someday the theme could implement the relation-finders of other plugins that do the job, like YARPP, the way it works seamlessly with those avatar plugins…

Yeah, I’m finally realizing the pain of too many hacks, even in a child theme… If I replace enough of the files and functions in a child theme so it can survive updates, the effectiveness of an update is diminished anyway :p

Welcome!

The team doesn’t work on weekends.

Some of the gaps would be resolved via this CSS:

.td_block_big_grid {
  padding-bottom: 0px !important;
  }

.wpb_row {
  margin-bottom: 0px;
  }

Adjust px as desired.

The horizontal gaps are harder to remove because they’re part of the entire grid layout. I would recommend not bothering, but if you really have to, you could play with these values…

.td_block3 {
  margin-left: 20px;
  }

.td_block3 .span4 {
  margin-left: 0px !important;
  margin-right: 0px !important;
}

Use .home .td_block3 and .home .td_block3 .span4 if you only want these to affect the homepage.

TagDiv support can probably help you with the ads; I can’t.

If you want that space between the grid and the footer to be removed, don’t add padding on top of .td-footer-wrap! Use a negative margin for .td-grid-wrap. The extra space probably comes from .wpb_row .row-fluid in your image (used for blocks and modules and such), but adjusting that would adjust all the rows.

Well, then, just guessing:

Your footer is broken because td-grid-wrap is the same class used for the footer. What selects the page one is the .td-page-wrap container. What you should be doing is

 /* Using specific sides to avoid changing side padding */
  .td-page-wrap .td-grid-wrap {
  padding-top: 0px !important;
  padding-bottom: 0px !important;
  }

Adjust as needed.

If it’s not high enough or too high, there are other elements in the way. For example, the page title, as Steven suggested:

.td-page-title {
  margin: 0px !important;
  }

The footer’s td-grid-wrap is contained in .td-footer-wrap rather than .td-page-wrap, if you want to adjust that.

You can add negative margins the same way if you need to tighten gaps even further, but for widening them I suggest sticking with padding rather than margin.

Do ensure that the slider is turned off on the Suits & Style category and all subcategories in Theme Panel -> Categories -> Suits and Style, etc. Then clear your cache if you’re using one, and purge your CDN cache if you’re using one. If it’s not the cache, I’m not sure what it is and we’ll have to wait for support. 🙂

cstyn, if you link to your website, it will be much easier for us to come up with the exact css you need because then we can see it as we work. 🙂

Haha, that works. (Since we’re a student newspaper and have a lot of volunteer photographers, I made the ACF fields be user selectors — it makes for a very easy query of the posts each user has contributed photos to. But if you don’t need that functionality, Chris’s easy route is probably the smallest headache.) 🙂

It did make for a hilarious read, though, once I’d figured out what was happening to your text :p

I used the Advanced Custom Fields plugin to add a repeating photographer meta field to my posts, saved credits for all the post’s images in said field, and edited Newspaper’s single templates to display the credit with an icon. For example:

http://mediumutm.ca/news/pink-hijabs-raise-awareness-of-breast-cancer

But this is very similar to what tcdraper did in the first place :p And it’s not the best for posts with photos from multiple different sources, which happens to be a rare case for us.

Theme Panel -> Categories -> each category you want to disable it on. As far as I know, there is no global option.

(I just recommended that plugin since it fixes the problem for me (and I do use Yoast). :p But if it doesn’t work for the OP then my apologies!)