Example link would be helpful 🙂

@giovanni114
again, theme does not control what FB picks up – that is based on the OG data.

However you can use Facebook’s developer tools to “test” one of your posts for errors.

Note you cannot change something once FB captures it, but you can try to do a “refresh post attachment” from the share on your FB timeline.

Should be.

Most often due to using the Photon plugin with Jetpack.

Better to use the built-in thumbnails, and change the default compression setting in wp-config.php to something like ’70’ (default is 90). We use ’45’ for best page speed for small thumbs as they are intended only as placeholders.

Also note any images with a lot of RED will never resave and look as good due to the inherent inability of JPEG compression to handle REDS at high compression (small file size) settings using *any* compression method for speed.

Use the clear caching option once per day manually to solve that, or move to a better host (sorry).

See
https://www.godaddy.com/help/flushing-your-cache-with-managed-wordpress-12444

Yes, as you’ve learned some plugins inject funky javascript into pages into odd places, and some will need to be updated by plugin author to more gracefully interact with pages. Some also put non-standard class names or rel tags they just “make up” which may not be proper modern HTML5/CSS3.

It’s an adventure 🙂

Export your settings from site 1 and use on site 2. QED.

Simplest way is to edit the single post template(s) you’re using to remove the element that loads the reads.

Yeah. Our main site online 16 years, and #2 site 11 years. So, right there with you! 🙂

Of course, we turn VC “off” and use the “Radu Shim” — so not quite the worry on that, more a worry with some of our legacy stuff.

Checking the changelog for Visual Composer is good place to check on compatibility with PHP7.

As of January, there was still the issue with VC and PHP7:

A problem related to this piece of code:
PHP Notice: Array to string conversion. in that line of code:

$param_value = isset( $$param['param_name'] ) ? $$param['param_name'] : '';
that code used in a lot of files in js_composer/include/classes/shortcodes/ folder.

I’ll be moving to PHP7 in May/June and will have some feedback then, also. Others seem to already be blazing the trail with TagDiv themes, so maybe a sticky on this might be useful.

Also note — you *can* clone your setup (make full backup of mysql dbase, etc), then switch on PHP7 and see if it works or not. Most modern hosting platforms (Plesk, cPanel, etc.) allow you to “choose” a PHP version on a “per site” basis for compatibility with 5.4, 5.6, 7, Meaning, you could make full backup, turn on PHP7, see if it works, if not, roll back to 5.6; if broken, do restore; back in business.

(IN your hosting panel, for PHP, there should be option on modern systems to use drop down selector to specify which version of PHP to run for the specific domain; same place you’d set max upload file sizes, etc.)

I’ll be doing that very thing soon. We’re debating an OS reinstall on our servers to get http/2 for Apache, and PHP7; both of which will combined speed up WordPress sites by potentially 30% (!) — or more — or just getting new servers. Pain is reinstalling or migrating sites.

Summer vacation ? What the hell is THAT ? 🙂

• This reply was modified 10 years by simchris.

AMP works with TagDiv themes “right now” — and has passed validation since November during beta.

So, there is no “AMP ready” version of the theme — it’s already AMP-ready. Much like the theme won’t build in its own ecommerce system to replace WooCommerce, etc., it makes no sense to make custom version of theme for AMP, since AMP is designed to load fonts and dependencies off the cloud, and only local content and images from your site. And there is provision for AdSense, and there is provision for CPTs, and there is provision for customizing the template. So, that is available NOW, and no reason to end up with 20 theme updates in the coming year just for AMP, Apple Publisher format, or Facebook Articles — all of this SHOULD be done with actively updated and supported plugins and left agnostic (not part of) the theme.

Many of our sites have been indexed the past month and the only issues are strictly content related, such as bad inline CSS from WordPress like stupidly using the center align tag on a paragraph several places.

I have a thread about this here, which you might find useful. The official AMP plugin is the only way to fly as its theme agnostic, and its being actively developed for WP VIP clients like TIME magazine, etc.

SEE:
https://forum.tagdiv.com/topic/tutorial-getting-started-with-accelerated-mobile-pages-amp/

(( I don’t work here … ))

Note that bright reds will never look good when resaved — “red” is the one color that JPEG is not well suited for and also why red light submarine shots in old DVDs look so bad.

Even in Photoshop to avoid “noise” in bright reds, you need to maintain at least a quality factor of 52; anything below that will introduce distortion in reds — there is simply NOTHING you can do about that as there is no “smart” way to say “red – use higher/better level of compression; everything else make smaller with more compression….” with built in compression/resaving of files in WordPress.

So, you either have to leave your default compression in the WordPress wp-config to default of “90” (and not set to 50/60 for better optimization of all OTHER image thumbs); and you also may not be able to use certain plugins, Jetpack, etc. which don’t have compression level settings.

This is very common issue the past 20 years (!), and not new. Only thing you can do other than setting a high quality factor in your compression tools/plugins, is either custom build your thumbs manually for “high red count” images, or live with it.

Point being — theme does not control the “compression” level of jpegs.

Welcome to the Web! 🙂

• This reply was modified 10 years by simchris.

Obviously issue with your hosting if neither work, or wp install. Did you increase default memory for wp? 40mb not enough for visual composer.

Look in your image folder. Make sure you have imagemagik or gd library on your server which is needed to make images.

Or possibly … create a custom ‘featured category’ which is just summary of each story, leading to full story; then have that cat not show up in sitemap (noindex no follow); then you could adjust each featured item’s date, newest to oldest, regardless of “actual date” — sort of a featured date, then sort by that custom category. Obviously this would just be for something like front page, NOT each category — which would be nightmare of logistics probably.

just some ideas …

You would likely need to create a custom module where you have it do a query for different custom tags like ‘featured1″ ‘featured2’ etc. then you’d need to tag the stories you want in each spot.

Likely need to hire developer if you have no idea how to do that.

Most modules are based on needs of “news” sites, where the grid would shouw items based on date range, newest item in the big spot.

Could be wrong — somebody might have better answer.

No way to do that “out of the box …”

You need to set up Open Graph tags for FB, and Twitter Tags for Twitter.

Use plugin like YOAST SEO or similar to accomplish this.

I think you need to actually have ‘sub categories” … so, you need to actually make some categories …

e.g., for you to see sub-categories of “life” — there has to be a sub-category for THAT category with actual content in it. Blank categories don’t show on menus in WP typically.

A main category would be something like “entertainment” then you might create a sub of that like “books” and another like “movies” and then those sub-cats would show on the menu for entertainment, if you have the option turned on.

Obviously you need to build out some categories, and remove stuff like “uncategorized…”

Example link ?

Likely won’t be on YouTube … very few videos for how to do this stuff. Usually on one of the many WordPress help sites (wpbeginner, etc.), or stackexchange.

Not theme related, but there are some tutorials on the web on how to redirect the /author/ slugs to the front page; usually done with a plugin or with custom rewrite rules in the htaccess file.

For those who want to ‘speed tune’ for fastest page load time, separate from any pagespeed insights score, removing Google Fonts is a must ….

————-
I love OpenSans …

however for our new project (not using this theme), we actually chose NOT to use any Google fonts for page speed, not “rating” but actual page load time.

I’ve been tuning one project down from 1.9 sec with default theme, to 1.1 seconds (so far), with image, with https, with mod_pagespeed, but not yet using caching plugin …

for this project I’m using a web safe font stack like so in place of (sigh) Open Sans:

font-family: 'Segoe UI', Frutiger, 'Frutiger Linotype', 'Dejavu Sans', 'Helvetica Neue', Arial, sans-serif;

for the “alt” font, using this stack
'Franklin Gothic Medium', 'Franklin Gothic', 'ITC Franklin Gothic', Arial, sans-serif;

I’m “getting used to it …” 🙂

For those interested, nice roundup of web safe “font stacks” here:
http://www.cssfontstack.com/

I love OpenSans …

however for our new project (not using this theme), we actually chose NOT to use any Google fonts for page speed, not “rating” but actual page load time.

I’ve been tuning one project down from 1.9 sec with default theme, to 1.1 seconds (so far), with image, with https, with mod_pagespeed, but not yet using caching plugin …

for this project I’m using a web safe font stack like so in place of (sigh) Open Sans:

font-family: 'Segoe UI', Frutiger, 'Frutiger Linotype', 'Dejavu Sans', 'Helvetica Neue', Arial, sans-serif;

for the “alt” font, using this stack
'Franklin Gothic Medium', 'Franklin Gothic', 'ITC Franklin Gothic', Arial, sans-serif;

I’m “getting used to it …” 🙂

For those interested, nice roundup of web safe “font stacks” here:
http://www.cssfontstack.com/

You can load the fonts CSS directly in your style.css file which will speed them up a bit, and then unhook the loading from the main theme/includes/function file — this is a bit advanced. Lots of tutorials online how to do this. (Basically you capture the actually CSS off Google’s server, then put that in your style sheet which loads the actual fonts off Google CDN; which cuts out a step in the chain — still loads the font files themselves off the CDN.)

Check Google’s terms of use, to see if you can download and use the fonts directly on your server. TagDiv doesn’t own the fonts, Google does. You would then need to do the same thing as above, unhook the loading from the main theme functions, then add the font calls into your style.css.

If none of that makes sense, you would likely need to hire somebody. This is very common practice for speed tuning.

For fastest speed, don’t use ANY Google fonts and use “web safe font stacks” which are entirely loaded from browser and modern OS.