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

Might be an https thing. I did have an issue with one element in the prior edition of Newsmag in the admin panel, which was fixed.

You might try changing anything with “http…” to “https…” in this file, just for testing?

/wp_booster/td_video_support.php

simchris
tagDiv Member

Try copying the post views code from one of the post page templates into your module template.

simchris
tagDiv Member

Not a bug in theme, we embed videos from both YouTube and Vimeo all the time.

These embed via OEMBED into a post, which is a built in function of WordPress inside posts, and with a wrapper for featured video, so that it fills the space.

I’m not sure why the line 109 in your setup would be trying to load an external website URL via FOPEN (which should be done via CURL anyway) … loading the proper VIMEO URL should simply do that in the normal iframe.

If you look at the actual line 109, it’s simply to get headers:

    function is404($url) {
        $headers = get_headers($url);
        if (strpos($headers[0],'404') !== false) {
            return true;
        } else {
            return false;
        }
    }

Remember NOT to put https in front of the shortcode URLs (youtu.be), only the full youtube.com URLs.

With Vimeo, be sure the video allows it to be used on other sites, depending on country of origin and copyright elements.

Not sure that helped. Just noticed this and had a thought or two.

You should update to 1.6, as it’s much better than 1.4 (lots of improvements). I was pleasantly surprised.

Use my upgrade guide for ‘best way’ to ensure clean upgrade.

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

Also, in your YOAST SEO setup for XML sitemaps — they *did* add option this year to NOT include authors by user role, so you can check the

EXCLUSE
[X] admin
[X] subscribers

this will keep out admin and subscriber posts from sitemap; and only those with actual editor, contributor (writers) roles in the sitemap(s).

simchris
tagDiv Member

Thanks again 🙂

simchris
tagDiv Member

Make sure you have your default “user role” in WP set to “subscriber.” A new user should not be able to have an “author” index, since a subscriber cannot make posts, only “view” posts. See the official WordPress CODEX on “user roles” for more information on that 🙂

simchris
tagDiv Member

I think this is function of WordPress … WordPress creates automatic pages for things like categories, tags, authors/users, etc. — the theme only changes the look of those things, it doesn’t create new pages, posts or tags for you, or users.

Whenever you create a new user, there is an index for that user under their username, and even under the user-id. It is basically the same as an archive, except has a custom template. Typically there would NOT be an index for a “subscriber,” AFAIK. But editors, and contributors, all get author indexes by default.

You can hide “empty” author indexes from your sitemap using Yoast SEO; which I do. 🙂

In things like author widgets (“featured authors”) you can hide un-used and admin authors by their author ID code.

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

Hi
just remember if you have

20 images x 40kb = 800kb

optimized

20 images x 25kb = 500kb

thumbnails

20 x 20kb = 400kb

20 x 8kb = 160kb

1200kb vs 660kb

what do you think will load faster ?

I see this on car websites a lot … sitting there waiting for all the photos in the gallery to load. Annoying!!! 🙂

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

I decided to leave the “note” icon alone, as I realized that this is the current defacto WooCommerce icon font element for “note” — and messing with that via FontAwesome also messed with the success icon and other elements, so rather than re-engineer all of that I instead gave each “info” or “success” box a backing color of #f5f5f5 with a thicker bottom border to offset it more clearly from the page.

simchris
tagDiv Member

Hi, Marius
okay the two buttons on the cart page look fine for iPad retina “landscape” but still not quite right for portrait. See two new screenshots:

cart page buttons landscape

and

cart page buttons portrait

simchris
tagDiv Member

@4lt3r
ideally you should use the 2014/5 “responsive” AdSense code vs the “fixed size” AdSense code for it to function properly.

simchris
tagDiv Member

maybe try contact@tagdiv.com ?

simchris
tagDiv Member

Use the Yoast SEO plugin to setup and control all the tags for Twitter and Facebook 🙂

simchris
tagDiv Member

HI, Marius
thanks for all of that; truly awesome 🙂

And yes, I did want to make the text larger for the “Proceed to Checkout” button at bottom of the cart page, so that it’s basically more prominent than the update cart, apply coupon buttons (put another way, kind of like having an h2 vs h3 … so people who have not used this checkout can SEE where to go NEXT more clearly).

THANK YOU!!!!!!!!!!!!!!!!!!!!! 🙂

simchris
tagDiv Member

Best way to install is via FTP, using just the theme zip only; do not try to upload the “all files” zip via WP panel – won’t work.

simchris
tagDiv Member

Actually, the toggle is fine for SEO purposes as Bootstrap uses this, as do many WordPress sites including WP VIP sites; so not a huge hairy deal since they fall under a “menu” class. We’ve had no SEO problems with that on our sites.

Just an opinion.

Arguably adding “rel=nofollow” to the mobile menu might be good solution if that was your concern.

BTW: if you use Google’s “fetch as Google” you will see “what the spider sees” — where they look at the rendered page, and are not stressing about informal code not rendered on page.

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

Somewhere in forum is the email to send link to the tagdiv support. I don’t have link at hand.

I *do* recommend trying my “how to upgrade …” option. I upgraded site from 1.4 to 1.6, and other than the usual issues with some of the sidebars going wonky, or the shortcodes that changed for home page layout with 1.5, it all works fine.

However I don’t use child themes due to the inherent eventual doom — !
Went through that with Canvas, Genesis, etc. .. never again!!

simchris
tagDiv Member

Not “my” theme; I just have been using the TagDiv stuff the past 15-16 months on daily basis, and WordPress for 10 years, so often have some insight from personal experience. 🙂

simchris
tagDiv Member

To disable all your plugins, see my upgrade theme guide.

FTP in, change plugin folder name temporarily to

xplugins

then login.

If theme borked also …. delete theme folder;
WP will revert to its current default “twenty-whatever” theme.

You can then login normally.

simchris
tagDiv Member

Yes! The compression level setting (from my helpful optimization guide) only impacts thumbnails created by WordPress via server imagemagick/GD libs. — it does NOT change the images you upload —

so if you upload image at 40k full size
normal thumb at smaller size, might be 10-14k
set compression higher, thumb might be 7k

No real visible difference — a thumb is just supposed to be an image “hint” to the full page/photo — not presentational anyway.

Kind of like in Photoshop, the diff. between the “10” setting and “7” setting makes the photo half the size, with no real noticeable difference (except with images that have a lot of “red” — ). Jpeg is a “lossy” compression method no matter what (hence why DVDs with low bitrates look like crap also!).

Some people prefer a setting of “60” … but I’ve found “50” works fine unless it’s a portfolio site or something. OR, images with a LOT of “red” which is the bane of jpeg compression.

Try it… set compression to “50” (or “60”) — anything better than default of “90”! Then regenerate thumbnails.

For your full size images you need to start with better compression — or, use something like smush.it (if you can get that to work), or something like mod_pagespeed which will optimize then cache for you.

Anyway, that’s been my experience.

Glad to help 🙂

simchris
tagDiv Member

One solution is to use a “lazy load” function, however this runs risk of some items not loading at all, if browser memory/cache times out.

What really sped up our use of such was using mod_pagespeed … this optimizes images including conversion to webp for Chrome, etc., caches with opcache if setup properly, etc.

And of course make sure the thumbs are highly compressed (like using the “50” setting in your functions.php vs default 90, etc.).

Better optimized images to start with helps also;
this image is 41kb and could be nearly half that, especially since B/W/greyscale:
http://dev.promicabana.de/wp-content/uploads/Justin-Bieber-21-Geburtstag-6-559x420.jpg

I’m sure you know all that … just chiming in as I tend to do. 🙂

simchris
tagDiv Member

Note Visual Composer and JetPack have long history of on/off/on/off problems, including images, the sharing tool, publicize, etc., and nothing to do with the theme itself. Sadly TagDiv cannot “fix” any issue with VC and other plugins.

You can try going back a version on Visual Composer, as that will sometimes work.

Alternately, consider that you may need to “freeze” your setup in between versions while compatibility issues between things “catch up” to changes.

So, “go back” to what works, then wait a dot revision on everything and test again.

If you’re using a high value production site, you can also consider making a test install someplace, such as a sub-domain, or even a sub-directory of your site, and test the plugins work together after version changes — then don’t propagate to the production version if one plugin doesn’t work well with another.

The great thing about WP is having the hooks and plugins to extend what it does; the bad thing is that all you need is one “bad actor” to load jquery wrong, or use a common class name, or something else, and it breaks all the pipes.

I’m sure you already know all of that, but just some input on this which I’ve had to suffer myself with 10 years of WordPress shenanigans.

simchris
tagDiv Member

Also note …
never a good idea to post LINK to that section of your website as anybody who clicks that will generate one MORE error for you.

TIP: wrap URLs to any non public thing in code here in the forum to avoid that 🙂

simchris
tagDiv Member

I also highly recommend …not… Using the envato updater.

Use my upgrade guide and it should be painless not counting and special plugins.

simchris
tagDiv Member

Wordpress has inherent problem of losing sidebar widget settings when changing theme. Not theme specific. Saving your settings from the theme panel helps.

Viewing 25 posts - 6,826 through 6,850 (of 9,335 total)