My apologies again for being rude to anybody.

Chris

Use common sense: I’m not saying go someplace else if you don’t understand how the plugins and licensing and bundling work, I’m saying if you’re unhappy with the great support here, including from many other folk who chip in ideas and personal experiences, then yes, please leave vs complaining “not much support around here.”

But let me explain to you how the plugins, licensing and such work, since you may be new to this; I’ve been using WordPress since Jan 2006, and have run across this issue many many times:

1) you get a licensed version of the plugin, which used to be “embedded” into the code so you wouldn’t need to deal with licensing or anything as it was a licensed product by theme developer. And yes, sometimes there was a “stuck” note in WP upgrade saying “one upgrade available.”

2) NOW with last theme upgrades, you get a separate copy, *tested compatible with theme*, but as a stand alone plugin to minimize issues with WordPress updates which broke the plugin last time (WP 3.9) – not the theme dev fault in any way.

The version is included as tested for the theme, and is updated when the theme is updated not when the plugin is updated.

They have updated the plugin code for Visual Composer many many times since October last year if you look at the change log ?

3) the notice about a “new version” is managed by WordPress – not the theme. This doesn’t mean the new version works with the theme, and it’s not the bundled version — meaning a new version of the *commercial version* – NOT included with theme – is available.

4) So, you may see note to upgrade to new version of a plugin, which is not the latest version BUNDLED with the theme. You may be able to install a new version IF YOU HAVE A SEPARATE LICENSE, but there’s no guarantee it will work with the theme, and then putting in support tickets about it won’t yet be relevant to THIS THEME.

Please don’t bash the folks here for “not much support around here” as they try very hard to give folks support, especially when about 50% of the issues are the user, plugins, server mis-config, etc. — just ONE support incident to fix somebody’s server setup is worth the cost of this theme. JUst sayin. You’re welcome to say what you want, as am I.

Most complex theme developers use some kind of “framework” or have now chosen to use Visual Composer as it’s less time consuming, and many devs are now familiar with it cross platform.

And yes, unless you built you own theme, there is no guarantee any theme or plugin will remain compatible with future versions of WordPress, like 4.0.

Seemed like you folks were complaining about something which is self evident for experienced users of WordPress, then bashing lack of support here. Two staff members do wonderful work trying to support so many issues with the theme, when many of them are custom programming not included with theme, solving wordpress/server problems. They tend to prioritize real issues, and not these kinds of non-issues which should already be well known for experienced WP users like yourself.

Cheers! Sorry for any upset.

Simply use the latest “tested” version included with the theme. The commercial version is separate product and you would need your own license, and it’s not tested to work with the theme; the version included with theme is tested to work with the theme and is included in cost of the theme.

@Steven – lots of great support here, way more is given to the average user than the paltry fee charged for the theme. Don’t like it, go someplace else please.

How to install theme:
https://forum.tagdiv.com/installation/

To update to current version, simply remove the plugin (old) from your pre 3.7 version; then in the folder from Themeforest

Newspaper-tf/Newspaper/includes/plugins/js_composer.zip

decompress the zip file, and upload to your website/wp-content/plugins/ folder. This will give you version 22.04.2014 – ver 4.1.2

Not that hard.

serginial

1) scroll back up several posts (in this thread) to see my list – you may want to read through this thread which has a ton of info on speeding up your site before posting at the end of it, where most things people need to get going are already explained in detail 🙂

2) setting your permalinks is a built in feature of WordPress .. basically just go back to your wp admin > settings > permalinks — and then press the “save” at bottom again; this will rewrite your redirects in your htaccess file for mod_rewrite in case they got munched by another plugin or update or whatever

http://codex.wordpress.org/Using_Permalinks

murattopak01

you should fix everything else FIRST, then worry about the “render blocking” thing last. This is sometimes very hard to fix.

Fact is most sites need “some” elements to load first for page to render. You might visit the sticky forum thread on pagespeed to make sure you have expires heads, caching, fonts, external elements, all sorted first, as the render blocking only counts for a very few points — all the rest count for 20-25 points and easy to fix without using a cloud system.

Yes… but those are static ads (in the demo) and not coming from AdSense. Two totally different things.

Graphics hosted on your own site or ad platform which are graphics can resize with responsive layout just like a photo, as that is exactly what it is.

AdSense loads in an iframe or container built by AdSense in the spot where you place the code. You have no control of the boxes being loaded externally from Google, etc., which may contain graphics and text and even video elements.

SO, the demo works differently since those are different ad units based on static graphic files. If you host your own banners locally and load them in those spots, as in the demo, they would behave the same way.

You’re comparing apples to watermelons and not apples to apples.

Hope that helped 🙂

• This reply was modified 12 years by simchris.

HI, Peter
I had suggested the config and htaccess as those sometimes get setup to point at a local WAMP setup for testing and then folks forget to change to point at the actual domain name 🙂

Glad it was something you could sort out.

Google doesn’t automatically resize ads when resizing browser, it only shows ONE size per session, for the initial ‘viewport.’ If you change browser size, you must hit refresh to get new session and get new ad to match updated viewport. This is Google serving the ads, not the theme.

Those are not codes I use, so can’t really help, sorry except the suggestion:

You should usually do a “resave” of your permalinks structure after every major WP update just out of paranoia, has been my experience. This redoes the rewrite of the WordPress specific code for your htaccess file specific to your site.

You might try my expires code found in this thread, instead. 🙂

Not having any of those issues on our sites.

You will likely want to double check your WP config file, htaccess, etc.

Or, Amazon CloudFront.

To fully “optimize” the .css files, you would need to learn how to “minify” them to make them smaller, if Google is suggesting that.

One trick is to use GTMetrix to scan your site for speed rating, as they can then give you optimized versions of your CSS files (downside, you would need to do this for every time the theme is updated… but this is part of the ongoing admin process for speed).

See the tips and info for your page here:
http://gtmetrix.com/reports/telsetnews.com/Upm34LMy

This is a recurring problem with Facebook and NOT your site, your theme, or any plugin. From time to time with Facebook one or more things happen:

1) Facebook system for “grab” overloaded, and cannot pull the information from your site; basically it “times out” and then just shows URL. Sometimes if you try again in a few hours, it will work properly. I see this every other day for our news sites. I sometimes just trick them by grabbing title, first paragraph, URL as my “post” on FB, then manually upload the photo from story to go with it, when finally disgusted by their timeout issues.

2) Facebook has already had somebody else share your page, and they are moving to a “one share” function where often they won’t let two people share the same page and choose different thumbnail, for example. Or rather, they take the first share, and then all following shares must be identical to the one they have “on file.” This seems to be an on/off/on/off thing. I’ve seen the “URL only” issue more often when somebody beats me to sharing the page before I do (some of our news posts before I’m up in the morning).

3) Your server firewall (CSF/iptables) may block Facebook’s IPs because they hit your port 53 for geolocation server checking for every post … so it can look like port scans/floods from Facebook since you might see 25 pings to port 53 from 20 different IPs all owned by Facebook (this one was driving me nuts last year until I figured out what it was).

Not sure that helps; but that is what happens to us 🙂

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

Also, btw; if you want to keep subtitles as part of the post, vs in a data field, you can simply use <h2>My Subtitle Here</h2> in html/text not visual editing mode on post page, at top of your actual post, where the sub-head would typically go below the photo.

h1 tags should always be used for the de-facto title of the story and match the title tags in meta for Google, Bing and Yahoo.

Technically there should only be one h1 tag for the title/block title; however in HTML5 there is support for multiple h1 tags in sections/containers.

For other tags, there isn’t a necessity to have a h2 show before an h3 unless you have these defined for nested semantic purposes and have such defined for the “semantic web.”

So, (inside main or article semantic containers)

main
h1 – title
h3 – subhead

h2 – giant sub section in body
h3 – subhead for subhead
p – explanation for information
h4 – definition heads
p – explanation for information
h4 – definition heads
p – explanation for information
h4 – definition heads
/main

would be perfectly fine

h2 – h5 can really be addressed as merely headline “sizes” to show priority as a “section head” vs simply a paragraph starter in strong/bold. Put another way, it is best in a story to use a h4 vs simply a strong/bold sub-head for, say, new chapter sections of a book serial. Anything with an h tag is identified semantically as a headline of some kind.

H1 on homepage – this is typically not a huge issue with newspaper sites as there is little or no original content on the “front page” .. it all links to the content pages on the site, which is what you want found when spiders show deep-link content to searchers. So, what exactly gets optimized on the front page? You can end up fighting your own content if you’re trying to get your home page to rank against “awesome motocross videos” versus the actual index on your site of all the motocross videos – both can’t be the best choice for the site.

If you’re running a store/shop, then h1 on home page is critical for branding and bringing folks to home page — if there is substantive original content on the home page.

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

this may be useful:
http://wordpress.org/support/topic/wp-admin-you-do-not-have-sufficient-permissions-to-access-this-page

It’s really something which should be built-in to WordPress, as they now use the ImageMagick library vs GD libs. They (Automattic) are just “philosophically” opposed to image enlargement as they say “it makes things look fuzzy.”

Hence the hacks (plugins) which basically just do the call to the built-in server image processor to over-ride WP turning that off.

For instance there is no real reason tagDiv couldn’t adapt the code found in “Thumbnail Upscale Version 1.0” for use with the theme.

Timthumb works great, but most “modern” theme developers won’t use it, in favor of the built-in WP image processing (basically “select a featured image to make a thumbnail or go away”).

We’ve been using Woo Canvas for some news sites, but have waited to switch to Newspaper due to the image upscale issue. Some savvy themeers use BOTH methods and give you a choice, but most do not, as here. Nothing wrong with that, it just seems like theme devs need to adopt the workaround for accessing server image tools already being accessed by WP anyway, and then over-ride the upscale limitation. Ideally WP should have function for this, but noooooooo.

Next step is to take a legacy site and convert over and see what happens 🙂

about 20 lines of code!!!

class ThumbnailUpscaler
{
	/** http://wordpress.stackexchange.com/questions/50649/how-to-scale-up-featured-post-thumbnail **/
	static function image_crop_dimensions($default, $orig_w, $orig_h, $new_w, $new_h, $crop)
	{
	    if(!$crop)
	    	return null; // let the wordpress default function handle this
	
	    $aspect_ratio = $orig_w / $orig_h;
	    $size_ratio = max($new_w / $orig_w, $new_h / $orig_h);
	
	    $crop_w = round($new_w / $size_ratio);
	    $crop_h = round($new_h / $size_ratio);
	
	    $s_x = floor( ($orig_w - $crop_w) / 2 );
	    $s_y = floor( ($orig_h - $crop_h) / 2 );
	
	    return array( 0, 0, (int) $s_x, (int) $s_y, (int) $new_w, (int) $new_h, (int) $crop_w, (int) $crop_h );
	}
}

add_filter('image_resize_dimensions', array('ThumbnailUpscaler', 'image_crop_dimensions'), 10, 6);

Basically the same code I’d posted previously, from Stackexchnage, made into a plugin.

I wonder if just appending this to functions.php would work?

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

Well, color me amazed. This actually worked.

1) plugin: Auto Post Thumbnail PRO 1.3 by By Tarique Sani (commercial plugin)

2) plugin: Thumbnail Upscale Version 1.0 By Stanislav Khromov (free via wordpress.org)

My media settings
Thumbnail size: 326×159 (because our old small images were 300×250)
[x] crop thumbnail

Medium Size 700×357 (max width x height)
Large Size 745×483 (max width x height)

Did regen thumbs on old posts, and the slightly smaller article headers were enlarged and properly cropped to fit the home page 4-box slider big pic (745×483), and the category indexes with featured image (700×357).

Did new post with image size of 700×406 placed into top of story, hand selected as featured image, and then it properly zoomed it on front page slider.

So, for me (so far) this combo solves multiple issues/needs for our various sites. How freaking awesome is that. Still need to test on some legacy stuff, but seems to work.

example:
enlarged/cropped thumbnail for category featured image
http://ga-ga.com/gogaga/lifestyle/

Original article with legacy content/image size
http://ga-ga.com/492/growing-older-in-a-youth-oriented-society/

So, for the “older folks” here, this now seems to do what timthumb used to do, although at the moment with “all thumbs on” – this makes 8 thumbs per photo, even smaller pix put as supplemental images. So, a story with 2 images, has 16 image files.

Obviously I need to audit the sizes actually being used and trim a couple of those, maybe 3 sizes out including xxxxx-1074×483.jpg.

🙂

• This reply was modified 12 years by simchris.

Well, with a dedicated server with 12 cores (XEON), and 32GB of ECC RAM, RE4 RAID 5, blah blah, we should be able to generate images locally using image tools already on board the system (e.g., ImageMagick, old GD Libs etc.).

For our purposes creating external accounts to handle image creation and placement across multiple news portals is needlessly complex for our needs if we can do it “on site.”

So right now we have a plugin which will create a local “thumbnail set” per theme and media sm/med/lg, and then set featured image from both locally hosted ftp images inserted via relative URL (not using media manager) and will post to media manager; will do the same with external images placed inline, but pulled from the main news hub (not locally hosted); and will also not interfere with locally created articles which have images uploaded via media manager and placed inline at top and flush right within body text.

Testing the next step, which is separate element/task which takes the featured image set either automatically or manually, and then creates the zoomed/cropped/enlarged versions and saves to media location so that theme can pull that size for the featured images on category pages and home page. This also uses the server side built-in image processing horsepower without any external I/O.

Once posted images are further optimized by mod_pagespeed and cached server side.

Stay tuned 🙂
I am testing this momentarily, in fact (Fri. May 2, 2014).
Expect either happy face or frowny face once I try this.

Also installing upgrades to our ecom system which is always a barrel of monkeys (for those of you old enough to remember that). 🙂

• This reply was modified 12 years by simchris.

BTW: Radu A

the word “Support” still says “Suport” in the English version of the support forum, top of each page:

tagDiv community / Private: Newspaper

Skip to content

Suport

Our portfolio

Newspaper documentation

Would be nice option to have as choice from panel.

But here was my old post
https://forum.tagdiv.com/topic/adding-page-background-site-wide-not-using-theme-panel/

From Radu A

http://screencast.com/t/kinWT9k1

body  {
  background-color:blue !important;
}

div.td-header-bg {
 background-color:#00ff00 !important;
}

div.container.td-logo-rec-wrap {
   background-color:#ffffff !important;
}

div.td-menu-background.affix-top {
 background-color:red !important;
}

div.container.td-menu-wrap {
  background-color:#ffffff !important;
}

Hey ‘Big K’ ! (popping in just to check on bugs for new update) …

I asked about this previously. Because the layout “below the full width navbar” is in three sections for advertising option:

[left] | [mid-body-mid] | [right]

you would basically need to apply a background image to the left element, and the right element to achieve that.

And so to do a gradient background top-down to cover full width, you’d pretty much need to apply gradient to [left] [mid] [right] as three sep divs/sections. Or, to leave center area alone, you’d apply a background to the two divs, sort of like manually applying an image in place of adverts to those two divs – outside the theme options; using custom CSS.

There is answer from marius/radu on this topic on how to do it now, if you’re interested in hunting that down. Sorry I don’t have it handy.

It’s in the main zip file with ALL the content for theme, which you download from themeforest, the same folder with psd files, documentation, etc. — note the folder “plugins”…

This is in the zip file you download, not on your web server. These should be in your project folder on your computer.

Newspaper-tf > plugins > td-speed-booster.zip

always good idea to “explore” the folders and files you download after purchase before upload to your own website.

Thanks again for kind words 🙂

Stalk me on twitter: @tophersimmons

• This reply was modified 12 years by simchris.

I should likely mention, I *will* be following up on my existing posts that I’ve got set to email me, as time permits – jut not new stuff.

( In case somebody was thinking “hey, didn’t this guy just say he was not helping out any more?” 🙂 )

• This reply was modified 12 years by simchris.

You got it 🙂
If you had some stuck categories in your XML sitemap; go check the sitemap online and see if the categories are there. If not, Google likely had them cached from a prior scan when they did (oh like if you imported the default content for theme?), and you can resubmit sitemap, and then in Google Webmaster tools you can check the “fixed” boxes, and that should take care of that. Also, in Yoast you can kind of force a better rescan of sitemap by changing the number of pages to break XML sitemap into, from 1000 to 999. I do this once in awhile then switch back to 1000. I just like messing with ‘bots … 😉

• This reply was modified 12 years by simchris.