You could use my upgrade sticky post to upgrade from oooooold Newspaper version to latest.

Well, can you be more specific ? Are not your normal header and sidebar ads showing on your tag pages, just like on your category pages?

If you setup a custom sidebar for your tag pages, you need to actually put ad units in the appearance > sidebar you’re using for the tag pages, if not the default one.

My tag pages show my ads the same way they do on a post or category page, since they have the same header and sidebar.

You can control your OG tag settings with YOAST SEO, which is what we do here. You can also change the “title” tag for posts to remove site name from title.

• This reply was modified 11 years by simchris.

I think you have to make a category page template with visual composer, but haven’t done that myself.

WordPress cannot enlarge images due to stupid setting of the Automattic folks (who make WP).

You need to use the “Thumbnail Upscale” plugin which turns this function back on.

Your web server supports doing that, but the WordPress folks don’t like it as they think it “makes images look bad when enlarged.” (Really dumb.)

Try it … then do regenerate thumbnails (using THAT plugin). It’s like magic 🙂

See the theme docs on how to build home page.

You start a new page, and use the visual composer which loads automatically.

You add rows, and modules to a page, then that page can be set as your home page.

https://forum.tagdiv.com/homepage/

Can you be more specific ?

What kind of ad, which ad box are you placing the code into ?

https://forum.tagdiv.com/ads/

@faical

Try starting with the theme docs, right side of page.

https://forum.tagdiv.com/how-to-use-the-megamenu/

Try starting with the them docs, right side of page.
https://forum.tagdiv.com/how-to-use-the-megamenu/

Use the suggested recovery method from my post
https://forum.tagdiv.com/topic/how-to-guide-to-moving-from-newspaper-to-newsmag/

Those are generated by Google

use the YOAST SEO tool to edit how your search appearance will work.

You can also disable breadcrumbs from the theme admin panel.

The first example is better for SEO. You have to disable breadcrumbs in the theme admin panel to stop Google from doing that.

As I said, the “mega menu” can cause issues with Google as you’re “front loading” images and headlines “ahead” of the actual story headline and photo; and Google+ can sometimes grab that element as “first large photo on page” vs “first image part of post…”

We used to see this with self-hosted ad banners sometimes where the banner would show up as it was larger image than the post image. The OG tags “mostly” helped with that but not always.

So, it’s a trade off … you basically need to “tailor” the page load on how Google’s bot actually scans it, and often the way your mega-menu or other top of page content is setup can “confuse” that. Trial and error.

I would go back to 1.6, personally. 1.7 has a whole slew of issues which is why I reverted my test site back, and left the others at 1.6.

You can’t …. Google is not being paid to scrape your content, so they can do whatever they want. Same with Facebook.. I have one story from yesterday that FB won’t scrape… just sits there … no good reason for that. Nothing unusual about the page. They just hiccup on that particular item.

Only thing you can do is look at difference between the page they are not scraping properly and one they are, and try to make sure the “wrong” one is setup like the “right” one.

I’m using Newsmag 1.6, so 1.7 might have entirely different problem due to the lazy load problems.

If you come up with some “solution” to making sure Google grabs correct image/paragraph, would love to know. I’ve been trying to sort that out across 4 themes for almost 2 years without any clear “make it always work” solution.

We now have photos working right every time. But like I said, we sometimes trick them on that with ensuring the featured image is in the body and in the meta, and not using mega menu.

Sorry don’t have better answer.

Note WordPress cannot “enlarge” images, only make them smaller, so you need a plugin like Thumbnail Resize to add that function. The theme doesn’t re-render your original images, only make smaller thumbnails from the original image and crop them to maintain aspect ratio with the modules/blocks.

You can also set the compression ratio for the thumbnails as per my sticky post on “optimization” to make the thumbs more optimized for page speed on home page.

When you say “not cropping” — do you have example?

e.g., link to original image on your site,
and link to page where the thumbnail is that isn’t “cropped” ?

They have no set release date, as noted in the many posts on this subject in the forum.

They are “hoping” for end of April, but no set date.

Might be delayed due to a “hiccup” in the planned “lazy load” image feature which caused some problems with sister Newsmag theme. Might not.

Stay tuned. They will announce when it’s available 🙂

Google has problems with scraping and grabbing content sometimes.

As long as the proper image is showing in your meta data (the head of your post page), they normally “should” grab that image. But, sometimes they have bizarre hiccups unrelated to anything you’re doing. I have had this happen a couple of times, and it was usually due to using a “giant” image as a background behind the text without having the same image in the body someplace (I often double the image, once for the giant background top of page, then mid-point at normal full width of post, plus set as featured image).

Not really a bug or anything – just some inconsistencies in how Google “scrapes” the content from your page, and whether they go with your “hinting” or just run off the rails.

The MAIN issue I’ve found is when you top-load the “mega menu” with links and images for your posts, and that can throw off the G+ scraper as they may go for the “first large image” on the page. Which is why I don’t use the mega-menu on posts (among other issues, like speed, etc.). Also, using “large” images in the sidebar, especially those using a “left” sidebar.

Not sure that helps, but that’s been my own experience with G+ weirdness.

I’m still trying to figure out why some posts they grab the whole first paragraph and others they don’t.

Mashshare….
Install plugin. Activate it. Done.

Luckily you can turn it off/on with one click. 🙂

Feel free to disagree.

We have a large ad network and dedicated senior rep with Google AdSense. In our sites we are using a wide variety of content in our sidebars including search, relational content, and the ads are not the primary element, so while this is stated

Drawing unnatural attention to ads includes placing Google ads in a floating box script that causes the ad to appear in a “sticky" position on the page as the user scrolls down. This type of ad implementation is not permitted.

The meaning of that text refers specifically to a floating sticky AD, not your entire sidebar; meaning, it is a direct violation to have sticky ad similar to floating social buttons.

But specifically:
They have looked at our sites numerous times and said it’s not an issue in this context. If you have nothing on your sidebar except an ad and cause just the ad to stick — THAT violates the TOS. If you have 10 things on your sidebar and ONE of them in the middle is an ad, that does NOT violate the TOS as you’re not specifically “drawing attention to the ad” — you are “keeping content visible” which would otherwise disappear on scroll — meaning, it’s the same as having a “short” page vs “long page” … you’re drawing attention to content, and there happens to be ad as smaller part of that … so in a 300×1400 block, a 300×250 element is only a fraction of the “content” and so you’re not targeting eyeballs with just an ad.

Doubleclick actually allows ajax reload of ads on the page, which is different of course (look at mashable home page right now to be assaulted by Star Wars ads…!). This is NOT the same thing.

So, note that keeping your whole block of content visible is one thing, keeping an ad visible to draw attention to it is a different thing.

We got approval and getting paid every month across our network of sites. Your mileage may vary.

No luck involved on our end, we KNOW this is okay and have it approved. But do what you want.

(FYI: above a certain payout amount or number of sites they *do* check your sites once per year, based on our experience the past decade.)

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

For those specific folk using mod_pagsepeed

you may start seeing some oddities with Pagespeed Insights, where Google now telling you that stuff like a .js file or .webp file doesn’t have an expiration header over 5 minutes; where basically MPS is “intercepting” the file to serve on page build, and so a few oddities ignore the .htaccess file TTL settings (!).

The fix I discovered yesterday is adding a config line to the master pagespeed.conf file, and looks like this:

ModPagespeedImplicitCacheTtlMs 604800000

Basically this will over-ride the MPS default time to live (TTL) from 5 minutes to whatever time you want, such as a week. Note that the number is in msec not seconds (!). So, typically you need to work out that time using online converter (Google has built in function for that … !).

This was driving us nuts the other day, and this was the solution.

Depending on your server you might also need to actually add the webp MIME type to your apache mime setup file.

Hope that helped somebody!

You would need to do a new install of WP in the folder … or do a complex “multi-site” setup. See the WordPress codex for that.

Tip: when learning WP you can often do a google search like

WordPress Codex edit post

and find official docs for post editing. 🙂

I believe you can change that in the visual composer under the “edit” block, there is a field to set your own custom title like “Book News” or similar. 🙂

It’s actually better to start from scratch and NOT use the demo, and simply refer to the online demo site while playing around with your new test site. Otherwise when you actually decide to use it, you have to go in and clean house on all the categories, menus, starter demo ads, etc. — it’s much simpler to learn to use by having blank canvas and “build it up” with some test content, even if you’re using the same image on each test post to try out different layouts, etc.

Just an opinion….

Having an adsense ad in a “sticky” sidebar does not violate their TOS. This is not new content rendered by ajax load/reload, it’s simply bootstrap “affix” where the “rendered” DOM has a section of the page which using CSS “sticks” on scroll. The page doesn’t change, reload or otherwise render new ads, nor does it instantiate new ads or popups. It’s still the same page, it’s still the same sidebar, same div, same “session ID” for the person seeing the ad, with same cookie and tracking for the ad(s) in the sidebar.

Having an ad in any element which refreshes or reloads is a violation; that is not what is happening here.

Simply having a section of the site “stick” and not move does not violate TOS, per my own conversation with them last year.

Keep in mind the “sales reps” don’t make policy.

They will contact you if it does. They will also contact you if you promote ads on your pages which promote software that defeats any Google DRM tech (like ripping YouTube movies or Android hacks), and they will contact you if you use the word “sponsored” near your ads(s) vs “advertisement.”

We’ve been working with Google since they launched AdSense, and trust me, you’re fine.