Search Results for 'update'

See:
https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/

Yeah, I ended up doing it that way since I was manually putting in a copyright notice for the author’s work (e.g., for a fiction piece, or book serial), as well as link to the author’s page to “read more by this author” …); and sometimes link back to “read chapter one” … just made it the simplest solution vs “wrangling” custom stuff.

Advanced Custom Fields is cool way to do it too, but I’m already doing too many hacks per theme update, and skipping every couple of theme updates (waiting on 4.3.1 now!), so one more thing to drop into templates was a bit much, so the manual way kind of worked since I can put the dates on the copyright more easily than trying to do query, and doesn’t add yet another data field to dbase, etc.

I think in an environment where you have multiple authors posting their own stuff, a custom field is great because you could make it “required” so that it’s always there, and remind people it needs to there, etc.

Thanks, First i will updated the theme, to the most recent version.
I’m running on a older version.

Thanks for your info,

Actually, don’t bother reading above, things have changed since then, I will re-post the update. Thanks.

If using the version included with the theme, you don’t need to put in a license as it’s a “bundled version” of the plugin which works with the theme.
https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/

• This reply was modified 11 years by simchris.

Heya,

First of all, I’m far from the most brilliant guy on tagDiv. If I were, we wouldn’t have spent have a dozen posts correcting my tiny mistakes 😉 I’ll give that title to Chris to avoid favouritism among the actual staff…

Your ideal setup definitely requires some custom work that I don’t have time to provide at the moment. I would go to http://studio.envato.com, as tagDiv recommends — or you could do some learning, just like I did, and do it yourself 😀 But I will make a few comments:

Having content in these tabs that differs from post to post means you’ll either need to make extensive use of custom fields, or you could use Visual Composer settings to build the post itself. The question is what are you using the regular post content for? A comment on the phone, for example?

The first option would mean that you’d insert code similar to what I’ve been giving you, and have it appear on every template, using custom fields to determine the content. For example, as you probably know, ACF has a WYSIWYG editor field that you could use for your review. The buy now would not be as easy to automate through such a field, in my opinion (but you may already have a solution and just be looking for how to use tabs for it?).

The second option is that you’d construct these posts in the editor itself using Visual Composer, and then perhaps use custom shortcodes to display the content of your fields.

Or a real developer might suggest some much more sensible solution. :p

But I will give you one last thing, namely a basic tweak of my above code just for your “Features” tab.

The idea is the same. You’re opening up a vc_tabs, you’re opening up a tab, and then you’re looping through features-related fields. It could look like this, with lots of extra comments and line breaks to make it clear for you:

// 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
echo $to_echo;

My note above about only needing to change $field_names applies to this as well.

If you were going to put other tabs in, you would modify the lines that open and close the tab groups, and use those in a similar way. I realize that this is just a simple list and not a table like you wanted — more research would be needed for me to construct a way of getting the label of the field group and such…

Hope that helps. I do think what you need isn’t just “support” but custom work, although it will be fantastic if you can figure the rest out by research, trial and error.

Best of luck!

Hi,

Thanks for the reply, i have uploaded the old version of the theme. Issue is still there with the new theme update.

Thanks

Thanks for the update. I’ll take your advice and disable the Yoast plugin for now.

Thanks for letting me know so quickly! I’ll wait for the updated version of both.

Cheers,

Probably need to contact the plugin developer since changing the names of images, may not actually change all the links and instances of the indexes with the images, especially if you’re using any kind of caching.

Presumably the plugin would rename all your core image files based on the size you had originally? Ideally you could then simply regenerate thumbnails for all the news sizes from the renamed MAIN images and they’d be built with new name.

However since you’re using a plugin to change the NAMES of the files, one might assume it also updates all your posts to reset all placed, featured images with the new name also?

Obviously you would need to line up the changes to your posts to have the NEW image names in the posts so that the proper thumbnails are being built for that module.

Not sure if that helps, but not really a theme issue, specifically.

And of course, many of us have (ahem) requested since last November, that the author byline on post pages be “on” by default, and “comment out” to turn off, since all real newspapers have bylines for stories and the theme is called “Newspaper.”

Consider this a reminder “poke” that most of us would prefer the option to be “on” by default for a newspaper site, not an option which has to be hacked every update.