Home User profile
tagDiv Member
Christopher is a long time WordPress user. Anything else you need to know is private ;-) I *do not* work for TagDiv, but I've been using their themes since late 2013.
simchris
tagDiv Member

Where are you entering the registration code?

There is no registration for Visual Composer, only for the theme.

If you use the version of Visual Composer included with the theme, it should work. If you have a version from a prior theme, that likely will NOT work with this theme.

Sorry if that did not help.

TagDiv support will be in Monday a.m. 🙂

simchris
tagDiv Member

also trying

.woocommerce #checkout .input button .alt{font-size:18px !important;}

and

.woocommerce #checkout div.place-order, .woocommerce-page #checkout div.place-order .input button .alt{font-size:18px !important;}

obviously stuck on this one ! 🙂

  • This reply was modified 11 years by simchris.
simchris
tagDiv Member

What code are you pasting into the post ?

Are you using the Vimeo embed code for WordPress ?

When you got to the video on Vimeo they do have a specific embed code just for WordPress, and they also have option to save custom sizes, but that video being loaded is coming from Vimeo and is only appearing on the post in an iframe — meaning what is “inside” the iframe is being loaded *from* Vimeo.

So, you need to get the right setting from the video share page to use on the post in WP.

You can also “view source” on your actual live post to *see* the size of the video being loaded into the frame, to see if it’s the right/wrong size.

You may have to change the “frame” height in the HTML when embedding the video.

One of those annoying things to experiment with. Hope that helped 🙂

:: NOTE: TagDiv support may have BETTER ANSWER come Monday, to use some custom CSS to change the default height of the iframe.

  • This reply was modified 11 years by simchris.
simchris
tagDiv Member

And one I keep forgetting until I do a theme upgrade; this really should have been part of 1.6 core update, but TagDiv helped me with this back on 1.2 or 1.4, which is for the thumbnails used at bottom of posts for “related” items. If you run various pagespeed testing tools, you might get the annoying notice about “not resizing” those images, which are actually 200×150 last time I looked. BUT, the theme resizes them from the 238x thumb vs making new one, when you have the 3 column related items as I do.

SO: here is fix for that; you need to edit /includes/td_config.php

(NOTE: syntax changed from 1.4 to 1.6 with API syntax; so if using older version copy one of the preceding elements and add the additional size).

So, around line 797 in v 1.6 you would need to add this:

td_api_thumb::add('td_200x150',
array(
'name' => 'td_200x150',
'width' => 200,
'height' => 150,
'crop' => array('center', 'top'),
'post_format_icon_size' => 'normal',
'used_on' => array(
'Related articles'
)
)
);

And then in the theme panel for the thumbnails, “activate” the 200×150 size, and sadly YES, once again run “regenerate thumbnails” plugin (since there are no 200×150 thumbs).

So, now when you load the “related” images at bottom of your posts, they will be 200×150 “actual size” and not “resized” 238×00 images.

Not a hyper critical item, but for those trying to get that last dot of speed rating, this is one of the action items.

Hope these all help folks “dial it in.”

🙂

simchris
tagDiv Member

Don’t recall. I’m using modules for my home page and not the blog loop.
I “think” that is controlled by one of the font settings in the theme panel, but not sure which (I don’t work here, just helping out since I’m using the themes daily the past 15 months!).

In other words, I think it’s controlled by the same size that manages the category titles, since it’s ostensibly the same loop.

Ideally, if you can’t find that, wait for tagdiv support on Monday a.m., or use F12 in Chrome (or IE11) to inspect the title element on your home page to see the CSS, and either edit in the style.css or add custom CSS override to the CSS panel.

Pretty sure it’s one of the category/blog title settings, possibly the H2 tag size?

simchris
tagDiv Member

Hi
most of the functions moved to the /includes/speedbooster/wp_booser/td_wp_booster_functions.php file

However, I think the image sizes are in
/includes/td_config.php

simchris
tagDiv Member

Yeah. I’m working on a WooCommerce setup for our main site this weekend, and little minor things with the buttons are annoying, and I feel stupid for not being able to sort the right CSS over-ride (just got up, cup of coffee in hand.. going to try again!).

It’s the little things.

On the other hand I *love* some of the updates in 1.6 (might have been in 1.5?), like the footer setup options in the theme panel now SHOW the optional layouts for footer !! That is really cool, as I just noticed that yesterday.

simchris
tagDiv Member

Additionally, I noticed with latest update that on the checkout page, the theme used the class “button alt” for the “Place Order” button at bottom, however this is a size smaller than the “button” class used on page, and if anything should be “button lg” (large). So, for example the button used in the info boxes to apply a coupon code or login is a size larger than the most important button on page to actually checkout.

I was trying to figure out to make this larger, and as usual I’m not getting the syntax quite right…

eg.

.input button alt{font-size:18px !important}

.button alt{font-size:18px !important}

any help on this one appreciated 🙂

( I am running Newsmag 1.6 )

simchris
tagDiv Member

Sorry, also for WooCommerce, it seems like it would be good idea to possibly have custom breadcrumbs if that is part of theme style vs WooCommerce default code.

Right now it seems kind of silly to have

cart
Cart

or

checkout
Checkout

about us
About Us

my account
My Account

for breadcrumb on cart, checkout and “pages” in store.

Not sure if it’s doable but something like

store > cart > checkout

store > cart

store > my account

store > how to order (for pages)

sure would be awesome.

  • This reply was modified 11 years by simchris.
simchris
tagDiv Member

looks like this happens to be:

div class="woocommerce-info"

simchris
tagDiv Member

Well, it’s below the content, it’s just that the zemanta plugin puts itself “first” before the other “under article” content. If you turned that off, or moved/changed its priority to run LAST in the footer, you’d be fine (see zemanta support for how to change that in their plugin).

Then all you’d need to do is apply some CSS to the footnotes, such as matching the width, and smaller size.

Or, you’d need to manually insert the shortcode for plugin at bottom of the single post template(s) you’re using …. which might even be the simplest thing. So, I would try that first.

simchris
tagDiv Member

Not sure if this helps…
the theme has default 1px border as part of grid; if you change the color to white to hide it, the 1px space is still there. In theory, looking at the screen shot, if the background is black, you might be able to make the border-right color 1px #000 (black). While leaving the other borders on page white.

I don’t know the exact CSS for that, unfortunately.

simchris
tagDiv Member

@jtbaker1971
hi – that has nothing to do with “forum fonts” …

please create a *NEW* topic for help with your question, please 🙂

simchris
tagDiv Member

Often the problem with a robots.txt file is that it can, by default, block areas of the WP install which actually have the elements needed to render the mobile version, such as the theme folder, or similar. However, this is usually done by a developer, or an automatic file created by server side hosting WP auto-installers, etc.

The theme is responsive, which means the same theme is being loaded for desktop and mobile devices, and only the CSS changes for the “viewport” … meaning, the same style.css file is loaded by either device, but the mobile deice “reads” the part of the CSS that pertains to that size (“viewport”).

Technically, if you have an issue in your robots.txt file, you can actually open that and look at it; and remove everything except any special blocking you might have in place for an abusive content bot, or any directive to Google to NOT index something like a /members/ folder, etc.

Put another way, simply empty your robots.txt file if you feel it’s blocking something! WordPress technically doesn’t use it for anything.

Old school folks might want to put link to their xml sitemap for those spiders which don’t know how to find it (e.g., Google and Bing – you should be submitting that in your webmaster accounts); and again might want to put in some directives for certain bots to not scrape content — but bad bots ignore those anyway.

  • This reply was modified 11 years by simchris.
simchris
tagDiv Member

I used to use pagenavi, but on “most” things this site uses the same code, just built-in; so on things like a directory/archive, or bottom of a blog loop on home page, it works exactly the same way.

Presumably you could locate the pagehooks in all the templates, but no idea.

Sorry, not an answer just an opinion that I found I didn’t need to use pagenavi plugin anymore when I moved to this theme.

simchris
tagDiv Member

Hi,
note – always best to use Google to find support for basic WordPress issues, unrelated to the theme.

FYI – videos embedded in wordpress posts are managed by the wordpress oembed function, not by the theme. Meaning, ALL wordpress themes/site can place videos into a post — and has nothing specific to do with the theme.

So, if you “google” this issue it’s very common.

One solution was to lower the height of the video code you are embedding to remove the height which is taller than aspect ratio of the video, hence the black bars.

e.g., try changing the height of the embded

width="500" height="281"

If this is a “featured video” post format, then you might need to edit the theme template for this issue. But it looks like you’re just placing video as per normal practice into the post.

FYI: On Vimeo, You can adjust the size by going to your video > click the share icon at the top right hand corner of the player > click ‘Show Options’ > adjust size and embed.

  • This reply was modified 11 years by simchris.
simchris
tagDiv Member

Sorry 🙂 WordPress by default doesn’t show tags on “pages” as traditionally one doesn’t want a “tag” page to compete in search results with the “actual page” … meaning, if you had an “about us” page, having a tag “about our company” would be redundant.

Obviously with certain cases, it could be useful, but this is a WordPress “standard” methodology — and not unique to this particular theme, hence no built-in support for that. There might be a plugin for adding tags to “pages” … as I think that has even come up in the forum before, but for Newspaper theme.

simchris
tagDiv Member

I don’t think you can do that with Newsmag, as it’s a fixed width layout. I believe the doc you refer to is for Newspaper.

Obviously, a 728px ad cannot fit into a 630px space.

simchris
tagDiv Member

Problem with install.
Best to start with clean install of WP on new server then move dbase over along with image directory.

Or, simply do a clean install of WordPress except for the wp-config.php file, reinstall the theme.

simchris
tagDiv Member

Well… I prefer rev slider, and changing to newm slider as base would cause existing sites to not work, and there would be fee to upgrade as tagdiv would need to buy new license agreement. Not likely.

Best bet is to work with tagdiv on a consistent way to integrate flex slider for your needs.

Just an opinion.

simchris
tagDiv Member

I don’t think there is a “tab widget” with Newspaper ? I don’t see one, nor in the demo?

There might be something in Visual Composer, where you can add something.

You can also use the WooDojo plugin to add a tab widget, but I’ve not yet actually tried this (it’s on my to do list …). 🙂

Sorry if that didn’t help much.

simchris
tagDiv Member

You should get your site working with proper paths using the default WordPress theme first and follow the directions on the WordPress Codex.

Once your paths all work, THEN switch to the new theme.

The theme has nothing to do with WP setup or server paths.

simchris
tagDiv Member

I’ll be the first to admit I need to actually DO the update prior to answering some questions ’round these parts. 🙂

simchris
tagDiv Member

You have to wrap any HTML in “code” here.
However, some things don’t work, as I’ve learned also. Try removing the < > brackets if using that in this forum. Tricky!

simchris
tagDiv Member

Use the version that comes with 1.6 if using 1.6

Viewing 25 posts - 6,876 through 6,900 (of 9,335 total)