How about the custom ad box ?

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

Not my theme;

I think you can delete in the “header.php” file.

If using a plugin like Yoast SEO, it’s managed by that plugin.

SOLUTION TO ISSUE OF WORDPRESS NOT GETTING ENOUGH MEMORY…

This assumes you have already increased the default memory allocated to php for your domain/hosting/site via normal hosting panel and/or php.ini to at least 128MB and likely 256MB ideal.

YOU SHOULD ALSO:
increase default php memory for WordPress in your wp-config.php file to 256MB. I’ve found, oddly, that for some reason, on some setups, changing the amount of memory via theme panel and php.ini does *not* actually increase amount of memory WordPress will actually use … adding the setting ALSO in config file makes difference. WordPress still thinks it will only use 40MB max by default, even if you have 256MB “allowed” on server — in our case, it doesn’t seem to SEE you CAN use up to 256MB unless you add the suggested line to your wp-config.php file.

*also note when dealing with memory settings to use “M” and not “MB” (!)

eg.

define( 'WP_MEMORY_LIMIT', '128M' );

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Addendum to my prior item above; this issue is actually resolved by using the TagDiv BETA “SHIM” which Radu has invented to deal with the PHP CPU issues related to Visual Composer. Expect info about this option at some point, possible in next update in June 2015; this likely will also be an option with Newspaper 5.

Last gasp … is

(assuming you tried deactivating your other plugins first; some people having issues with YOAST latest edition and conflict with Visual Composer 4.5 on some servers; issue with those plugins not theme — see the support threads on wordpress.org for yoast, for more info)

1) increase default php memory for WordPress in your wp-config.php file to 256MB. I’ve found, oddly, that for some reason, on some setups, changing the amount of memory via theme panel and php.ini does *not* actually increase amount of memory WordPress will actually use … adding the setting ALSO in config file makes difference.

https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

or

2) fully delete the js_composer folder, reinstall either the latest version from theme, or install version from prior theme version.

Facebook will always try to insert a “by whom” after the } and tends to fall back to the website name unless there is an explicit author listed; and may generate error in some places if *no* author specified.

Best thing is to make the website the defacto author, as that is in fact WHO is publishing the item being shared.

So, if you set the author to be wow-news.co … then that is the solution in most cases for what you’re trying to do 🙂

Hi
a) not illegal on adsense unless only thing you’re making sticky is wall of ads; topic covered many times; search forum if curious

b) you can disable the sticky sidebar from the theme panel; under post settings (smart sidebar)

Again, go to bottom of the theme control panel, at bottom .. Import styles, choose classic blog.

Great, no more help from me, good luck ….

If things “suddenly” stopped working, undo what you did to break it.

Or, try clearing cache – both server side and in your browser.

Try disabling any new plugins you activated.

Try different web browser to save settings.

See documentation rights side of page on how to update theme.

To set your theme style to classic blog, note the import settings bottom of main theme panel.

Also see link to documentation, right side this page.

• This reply was modified 11 years by simchris.

Um, that doesn’t look to be the NewsMag theme (as of 11:38am PDT 5/9/15) – site says you’re using “http://independentpublisherdot-me/” ?

Perhaps you’re in the wrong support forum?

============

With NEWSMAG:
If you’re trying to change the CSS for blockquote maybe try

blockquote

I do this with mine:
blockquote p { font-size:20px !important; line-height:26px !important; text-align: left !important; padding-left:20px;}

• This reply was modified 11 years by simchris.

Been there … have a great day 🙂

You need to change your settings in the theme panel > footer
to disable the “default” theme settings for the footer.

I think the top right elements are using a custom font, or png files.
You can probably look for the module for the social iccons in the theme folder, and perhaps try to edit that.

Virtually no site on the web uses the “official” graphics from the social sites as they are often not same size or “style”; most use the official logo but with custom iterations for consistency — e.g., TIME doesn’t use the official social buttons, nor does CNN, etc. Many now use the font awesome font set which has all the social icons and load faster than individual graphics. Others use sprites vs individual graphics for better pagespeed rating.

So take those issues into account if hacking the design elements 🙂

Tagdiv support back on Monday.

• This reply was modified 11 years by simchris.

Turn off the extension blocking update.

Try updating via FTP; delete old js_composer folder; upload new one (don’t “over-write” old one).

Well… reading the documentation for Yoast SEO might be good place to start 😉

Also good to look at your “page source” to *SEE* what is actually being populated into all your meta tags and open graph (og:tags) tags. [ it looked okay to me ! ]

You can also click the link in the sitemap tab of Yoast to see what the XML sitemap index looks like. Assuming you already did that.

You can also use the “test sitemap” button in webmaster tools to see what it says.

You get multiple sitemaps because of taxonomies and also a 1,000 item limit per index file. (So, a site with 4,000 items would have 01, 02, 03, 04 pages …. and “index” tells Google what maps are part of the overall site “map”.) Author sitemap might just be list of authors; tag sitemap might be list of tags. Mobile sitemap on some sites identify which content is mobile ready, vs what is not; etc.

Yoast basic online docs:
https://yoast.com/articles/wordpress-seo/

Arcane docs on Google sitemaps:
https://support.google.com/webmasters/answer/156184?hl=en

Basic issue with WordPress – not theme related.
You can Google the issue; some people make a “search” page with 404 template.

Basically there isn’t anything on site that should be linking to yoursite.xyz/search/

but hackers try to ping that location, and will generate the error in webmaster tools. Old known issue with WP.

Technically searches are done via
yoursite.com/search?query
(http://www.bintmusic.it/?s=mountain+bike)

so http://www.bintmusic.it/search/
will generate a 404 error since there is no page with that name or an index file in any folder by that name.

You can generally ignore that in your webmaster tools if there is just one of those and “mark fixed.”

If you are getting them constantly, then check your logs to see WHO is pinging that location and block their IP.

It’s possible that the search box, which starts with blank element
yoursite.com/search#

might somehow translate into a 404 — but that doesn’t show up in your XML sitemap, and Google is smart enough not to follow that deadlink in the search box (placeholder) — if they did you’d have hundreds of 404 errors per month.

Sorry if I’m rambling.
Generally it’s nothing to worry about.

The latest version “compatible with theme” is included in the download from ThemeForest.

This is a normal wordpress setting —

wp admin > settings > reading

SEE:

https://forum.tagdiv.com/topic/newsmag-1-7-1-killed-our-server-again/

What are you using to create the sitemap?
Might check the settings of the plugin you’re using to generate sitemap.

Theme doesn’t create or manage your sitemap XML file; that is built by the plugin you’re using (e.g., YOAST SEO, etc.).

You likely want to turn OFF the “lazy loading” feature if using CDN.

Well, you might try adding excerpts on your pages where you’re just using other’s content …

like your example link above – you have no actual content, and so FB tries to load the video you shared …

e.g. — look at your page source:

<meta property="og:description" content="Share on Facebook" />

You need to actually have something in your og tags for FB to scrape properly.

The theme doesn’t manage your Yoast SEO settings, nor does it manage Facebook. With actual content on your page and proper og tags populated there is not an issue sharing on FB with v1.71 of theme aside from the inherent inconsistencies of how FB scrapes material.

Does your example page “share” to FB properly using the twenty-fifteen theme ?

Use console f12 in chrome, select element to find the css class. I often use this but sometimes end up having to wait fir tagdiv support to point out the right class. Still as they are closed weekends you might try that to experiment.