Lots of things easy to edit for many folks; but some things – as with all themes – require custom CSS to over-ride “styles” when changing the defaults.

For the sidebar; typically you would create a NEW sidebar, such as ‘categories’ or ‘homeside’ and then drag widgets to each custom sidebar, then select that custom sidebar and its bank of widgets for the template you want to use.

meaning, you can’t choose widgets per template; you can select a sidebar per template, and each sidebar can have any mix of widgets.

See the docs for how to build a new sidebar from the template edit page; then when you go to the wp admin > appearance > widgets — you would see new sidebar, and be able to customize widgets for THAT new sidebar. Then on home page layout, or categories vs posts, you could choose the new custom sidebar in place of default.

Hope that helped. TagDiv support back Monday, but thought I’d chime in if you were to the hair pulling phase yet 😉

Just some input; I’d be cautious with autominify as that has caused problems with various folks; in many cases auto-minify of HTML is fine (we use mod_pagespeed for this); but for CSS and JS, I personally have found it’s better to MANUALLY do that (see my sticky optimization post topic on how to); as this ensures you know it works, and it’s not an “on the fly” issue but static from get-go.

Just some input on that one item 🙂

Well… it works for some folks and not for others — no idea why. I ran into this same issue using mod_pagespeed (which has built-in lazy load function option) on our site 15 months ago, and chose not to use it for same reason. I’d see randomly no images loaded. Meaning, the top of page items might load, but if somebody waited then scrolled down, there would be no images at all … super annoying.

The trade off with lazy loading is that some browsers and some setups just don’t exactly work consistently since it’s kind of an ajax load on demand thing — much like some of those long parallax one page website sometimes just crash the web browser which is super annoying (most folks have given up on that, thankfully).

I’ve disabled it on all our sites for this same “inconsistent” issue.

TagDiv support might have better answer … but that’s been my WTF? experience 🙂

• This reply was modified 10 years by simchris.

This is a bundled version not a commercial version of plugin.
I think you can “request” the examples, if compatible with theme, from tagdiv…

I think it’s contact@tagdiv.com

Did you
a) increase default memory in your wp-config.php file ?
b) turn off all plugins except visual composer to try to debug what might be causing overload?
c) optimize site for fewer queries, optimized photos, pagespeed, etc.

(a) is best thing to start with.

Try the Twitter code in widget in the default theme… maybe the code you’re using is bad ? Or has un-escaped element when placed inside a text widget.

Sorry I didn’t have better answer 🙂

You would need to add them ideally to the post template you’re using from the /theme/Newspaper/ folder. So if you’re using style5 post template, you’d need to insert that code in the post where you want it. That is broad stroke on how to do it; tagdiv might provide more step by step with screen shot once they are back in their support mode 🙂

OH …
you can turn off the “lazy loading” images feature – which seems to impact some people but not others, and some browsers but not others … that may be why you see an image in the edit, but not live on the page when posted!

Find that setting in the theme admin panel and turn OFF.

No idea. Works for me. Just offering some suggestions 🙂

Are the images in the post set as “featured” image? There will be NO thumbnails without a featured image selected for each post.

Maybe make sure you have the GD library installed on your server; WordPress uses that to create new images/thumbnails from your image uploads. Then the ‘featured’ image in post gets used to create the thumbs found on indexes and home page, etc.

Might be issue with the plugin you’re using and twitter being overloaded/unreachable ?

Okay, so did you do the regenerate thumbnails option ?

Again, might not be your issue, just a thought.

Hi
that’s not part of the theme but a built in feature of wordpress …

WPMU tutorial
http://premium.wpmudev.org/blog/wordpress-press-this/

these docs from wordpress.com might help, although you’re using self hosted version of WP:
https://codex.wordpress.org/Tools_Screen

https://en.support.wordpress.com/press-this/

You don’t get all the images from the “demos” — as they are licensed images. Meaning you don’t get 100 free stock photos with theme; you get the demo “layouts” and CSS, and need to use your own images. The demo is to help you setup a look/feel for your site, not give you a ton of free content and photos.

So, this is normal practice with themes bought from ThemeForest — as the demo images were licensed to TagDiv and not to you.

If that was not the query you meant, and I mis-understood, please pardon my input. I don’t work here but have been using TagDiv themes for 2 years now, and run into various such things in my own travels. 🙂

Did you also increase the default memory allocated to WordPress in your wp-config.php file ? Visual Composer uses a lot of memory, and the default 40MB not enough. This is a very common issue with themes using VC, so something to try first if you had not already increased to 96MB or more (pref 128MB).

Exactly. I prefer to own my content, which the old FB setup didnt support … But double chevk on that as its been over a year since i went through this exact same conversation for our site revamp when newsmag came out.

We use built-in comments with Akismet on some sites.
On others with higher traffic, we use Disqus.

We’re testing an async plugin using Disqus API for faster loads, but I haven’t had time to finalize that.

Generally I’ve stayed away from the FB comments as originally that slowed our pages down and/or caused them to not even load if FB was cocked up — so if that is async now, might be okay — if you don’t mind all the cookies and spying related to that and if your main visitors are coming from FB (if you have a million followers on FB then you’d likely already be using FB comments on your site ….).

When using *any* comment system remember it’s best to use one which allows you to save/store the comments locally which Disqus allows, so if you decide to leave it, you don’t lose the comments. FB didn’t support that — they “own” the comments, which wasn’t cool for our purposes. If they lose them or you switch it off, you lost all of that — not sure if it still works like that.

Anyway, some food for thought.
Some sites are removing comments as waste of time and too many trolls calling Obama a muslin, or pushing anti-immigration agendas or praising jesus for making baby food taste better or whatever. 🙂

You can try to add your coding to the style template found in your /themes/Newspaper/ folder. Note there are different templates for each post style, like “style5” and then a loop file for “style5” which has the content loop. Usually when I go to move/insert stuff I will open up the file, and put in something like
<p>testing placement</p>

into a spot, then upload then go to the website to look at one of the posts.

I’m sure tagdiv will provide a better step by step, but that’s the broad strokes on how to do it. 🙂

I had done a tutorial somewhere once upon a time which I don’t think is part of my sticky, only because the locale moved several times between themes …

but best way to optimize fonts (broad strokes):
a) disable loading from the main includes/functions file
b) copy the rendered css from Google for the stylesheet
c) put the actual CSS at bottom of the main style.css

this way you’re loading the fonts, but *not* the actual CSS sheet which is just a redirect loading the fonts from Google (so this saves loading the external style sheet, essentially)…

working on an ebook to cover all this stuff in detail but a bit behind ….

Hi
setup a custom sidebar for your home page if you don’t have one; add a text box widget from the appearance > widgets section in WP admin panel.

If you’re using visual composer for custom home page, see the how-to in building home page; create new horizontal “row” at bottom of all the other content. If you can’t do that, simpler to use a text widget in sidebar.

See the docs for how to create a new home page sidebar; you can then set that sidebar to be used in your home page layout.

But those are the broad strokes — worth playing with a bit to experiment.

Note you can make a new home page layout and mess with it, preview, etc. without actually making it live.

TagDiv support can likely help with more step-by-step; this was just an overview of one way to do it 🙂

Google doesn’t accept you based on the originality, importance, or type of content you’re publishing. Nothing to do with the theme.

You might try some of the forums online related to issues with Google AdSense acceptance.

Basically if your site has a lot of “copied” content from other sources, has questionable content topics against their policies, is located in certain countries, has misleading or confusing URL/domain too similar to a brand, if your site is nothing more than YouTube videos, etc., then they don’t feel you should be showing their ads.

In other words:
a) original content
b) images not taken from other sites
c) some youtube videos along with original content; not just parroting videos from elsewhere
d) content which is not too short — meaning, one paragraph does not make a post
e) remove any affiliate, text links, or inserted content which leads elsewhere or is masked, popups, etc.
f) make sure no hate speech, racism, attacks against anything in particular

You need to carefully read all their requirements in depth, see examples, look at other sites in relation to your own, remove copied content taken from other places, copied photos from other sites, avoid lots of video posts with no content other than video, etc.

They are not obligated to let you in their program, so you actually have to have a site they think is useful in some way.

Hope that helped.

This is very common to be rejected due to being a “splog” (spam blog) for example — not saying you have one, but one example.

Posts have h1 tags.

Home page you can simply either create a new row, which can be at bottom of page, or you can even create a text box at bottom of a home page sidebar.

For instance you could do what we do, add text box widget and then in that box put h1 wrapped short description of the website for SEO. Works. 🙂

If you want a custom text/color you can make a new class and do something like this in a text box/widget

<h1 class="homeyh1">Snazzy SEO description of my fancy coolio whacky website here for SEO and search. Love me, why won't you love me?</h1>

Hope that helped!

Normally a static page designed to build custom home page is not intended for public, but only for system builder to use as framework for loading the main page …

meaning for home page you want people to go to:
yoursite.vvv

not
yoursite.vvv/homepage

so it’s correct for “homepage” not to be linkable or loadable —

you instead make the link which SAYS “home” or “homepage” in menu link to just the actual home for web, which would be yoursite.vvv …

did that help ?

Maybe I’m not getting it either 😉

Try resaving permalinks, turning off any new plugins — if something “suddenly” stops working, it usually comes from a plugin update that no longer “plays nice” — a caching issue, or issue with CDN/similar.

Try
a) resave permalinks
b) clear any/all caching
c) turn off all plugins except Visual Composer.

See what happens.

Might or might not help. I’ve also found naming the static home page something other than “home” works better, like “homepager” since the static page isn’t supposed to be seen by anyone — it’s just for building the page which gets loaded by the theme as the default home; so nobody should be going to yoursite.zz/nameofhomepage

• This reply was modified 10 years by simchris.