Search Results for 'update'

The point about it being easier is true. But just in case having original box is strongly desired… 🙂

1. Find the ID of the user you want to hide by editing the user and looking in the address bar. E.g. you might see “http://yoururl…/wp-admin/user-edit.php?user_id=940” in which case the ID is 940.

2. In the Newspaper theme files go to includes/modules/module_modifier/td_module_blog.php.

3. Find the function that begins with:

    function get_author_box($author_id = '') {

        if (!$this->is_single) {
            return;
        }

        if (td_util::get_option('tds_show_author_box') == 'hide') {
            return;
        }

        if (empty($author_id)) {
            $author_id = $this->post->post_author;
        }

4. Add this after the part I just quoted:

      if ($author_id == '940') { // Replace with the ID you found
           return;
        }

That’s the if statement Kronos means and it just returns nothing for the author box if it’s the author you want to hide. Save and/or upload the file and check an article where you don’t want to see it.

P.S. That file can be modified in a child theme to survive theme updates automatically.

• This reply was modified 11 years by TheMediumUTM.

And a final note, but this is just because I’m a little obsessive:

If you’re going to have a lot of these tabs, you could automate the adding of each field. You would replace from // Simplest possible example of getting ACF data, sub in yours to // (You could wrap each block in an if to skip a tab if the data is empty) with the following code:

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

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

  // Set up tab 
  $to_echo .= '[vc_tab title=" . $data["label"] . " tab_id=" . $field_name . "]';
  
  // Check if we have a value
  if ($data['value'] {
    $to_echo .= $data["value"];

  // Default message if no value entered for the field
  } else {
    $to_echo .= 'No information on record.';
  }

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

Then whenever you want to change a field, you would just change the $field_names list and it would be much simpler. For example, if you had a field named ‘4g_network’, it becomes $field_names = ['2g_network', '3g_network', '4g_network'];

Hope that helps :p

That’s about it. Of course there are situations when an upgraded plugin requires some changes to the theme that may delay the upgrade of that plugin even there are theme updates available. For example, VC recently updated from v2.x to v3.x and we got three or four theme updates before they upgraded the VC plugin, because of the changes in the theme required.

So yes, as far as bundled plugins, go with tagDiv’s updates and rest assured they’ll keep all features within Newspaper copacetic.

Exactly! A lot of theme developers work this way by including a “bundled” version vs making you go buy a copy, but the the new version adds some wonky thing which might break the theme. So, this is a good way to do it, but kind of annoying at times, if you’re easily annoyed by the “updates available” notice in the WP login screen 🙂

At least WP stopped the stupid email thing they had for a few versions … “email: you have updates available; I tried updating, but it didn’t work …” …. automatic updates not a great thing, in my book. (I turn them off in my wp-config.php file, actually.)

I think there have actually been more problems with YOAST SEO than any other plugin in recent memory. Three updates in one day sometimes … x1, x2 (OOPS DON”T USE IT), then x3 to fix the messup in x1 they didn’t fix right in x2, all in one day. Upshot: never install the new version of YOAST unless it’s to fix long standing bugs, as they often have a panic fix later on.

Sorry … didn’t mean to editorialize so much … 🙂

That’s VERY helpful! Thanks for the clarification and the speedy reply! So, if I understand you correctly, there’s no need to update any of the bundled plugins because they will automatically be updated when the theme itself gets updated. Is that right?

If so, it sounds like an excellent safeguard against “breaking my site.”

Yeah it bugs me too, especially when VC updates and there’s no new update on the theme yet. The phantom update notice and all.

But licensing prohibits tagDiv from giving out a license to VC, which would allow you to update the plugin directly, and the VC plugin has been well customized by tagDiv for seamless integration with Newspaper. If you were to get the plugin update outside of a Newspaper release, things on your site would break because features missing, added, and altered from the core release of VC.

Have a good one.

You might want to read the documentation. The plugin is a “bundled version” which is included with the theme. It is updated when the theme is updated, to ensure the theme is compatible with new version. Generally speaking there are no new features in the latest dot revision not showcased in the theme demo on themeforest, so you’re not “losing anything” by waiting for a fully tested update that won’t break your website.

You may wish to peruse the theme docs, note link top right of this forum “documentation” and this page specifically:
https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/

Hope that helps 🙂

Had no idea about that issue. Come to think of it, lost my primary hard drive last week and had to install win7 64bit on my secondary and then again on the new HDD that arrived Sunday. Updates ran and IE is at 11 (Windows copy is from 2 years ago) and had no issues. I’ve yet to so much as select recommended settings for POS11, but that’s covered already.

I wouldn’t even hesitate to stop calling it “mobile first” since that’s not what it is anymore. That concept started with smartphones and has grown to include all sorts of tablets that act as much like a computer as anything but a computer can. Resolution is the issue, of course.

I’ve been blocking IE6 browsers from loading my sports site since 2008 lol The cast of Hackers called, they want their browser back.

And you know I meant to also say … really good question!!

I know lot of folks stuck on IE8 because they got that with Win7, didn’t update to IE9, and now when they try the IE10/11 upgrader/updater it crashes and they have to roll back. (ahem, my mom…. finally got her to use Chrome v37!)

But yeah, IE11 is pretty nice. But BS3 takes the “mobile first, damn the old folks” approach, which I admire, but not practical for a lot of people “yet.”

Anybody still using IE6 needs to join the future! 🙂

• This reply was modified 11 years by simchris.

It also screwed up my menu icons and social media icons after I updated the theme

Hi Lucian,

I will wait for next update, not a big problem for us now.

Thanks for your help!

Hi, i have updated the version and now all is going back to normal with speed booster active. Thank you 🙂

I keep a folder with copies of the files I hack each update so I can remember them at a glance, a text file with my additions to put at bottom of functions.php and note as to which section by line number x-x to remove; and a text file with cheat sheet of the search/replace for the style.css file. Not too painful. Kind of started when I had existing read/hit counter and needed to update the module to load the existing “field” vs the one used by Newspaper for hit counting. Then it was uncommenting the author byline each time in the main post file. Then it was the custom font loading. Well, there you are. As long as I have my local “cheats” folder, I can usually open two windows with both old stuff and new version of theme and then just top to bottom change stuff in new update folder, and then upload to server and it’s like nothing changed for the stuff I modified.

And, benefit is the style redirect issue that Google doesn’t like with child themes, and much easier to deal with any custom css over-rides as well as issues with tagdiv’s in house speedbooster plugin, etc.

At least this has been my experience 🙂

You are so right. I’ve been using the child theme so that my styling won’t get messed up or lost during an update. Might need to rethink that one.

Thanks again!

Suzanne

This has been asked a couple of times recently, so you’re not alone. (I would love something like that too.) TagDiv has said that they’ll add it to their feature requests list and consider it for a future update.

Demanding support won’t help. Sometimes folks need to second guess what you’re asking, or research past answers. Or, nobody else has had the issue, and so it might be local problem.

Two things I’ve seen, which may not apply to your case
1) javascript caching corrupt in your web browser; try clearing cache for browser
2) make sure you have enough memory allocated to PHP/etc., which ideally should be 128MB and not the default 16MB on some cheap hosting companies
3) make sure no automatic updates run on your install, as that can crash your admin sessions if something being updated in background
4) 404 error implies “site went away” which is common with either PHP or MySQL being overloaded; check with your server ERROR LOGS as this will TELL YOU what caused the error.

Hope that helps. Perhaps not.