I have no idea. You could so a search of the folders for the theme on your local PC to locate that block of text, probably.

Are you using the AddThis plugin?

I posted a solution to this bug in the AddThis code which began on/about Dec. 20, 2014. Super annoying.

see
https://forum.tagdiv.com/topic/fix-for-weird-line-break-from-addthis-plugin/

• This reply was modified 11 years by simchris.

You should have Visual Composer “activated” as far as on the plugins screen, meaning it’s is “turned on.”

You don’t need to enter an activation/authorization/registration code.

You should make sure you don’t have something “on the pages” linking into the root folder for /Newsmag/ which is not normal.

You can also try adding the explicit path to the theme folder in your wp-config.php (see the WP codex on how to do that).

Note I had the same error on 12/29; but not since then.

wp-content/themes/gaga/ 500 12/29/14

It’s not technically a real error for old HTML practice, but perhaps a true error for modern HTML5 practice. Not all images/icons need an actual alt text, only must have the alt tag itself to pass CSS standards. So, alt=”” is correct for a spacer graphic, or icon with no semantic meaning where the alt text would not provide useful info when the image does not load.

HOWEVER
I am going to request Radu actually make that a value of “right” and for the left image add “left”

e.g. alt=”left” alt=”right” as appropriate, for modern site checkers and consistency. Or, perhaps the ASCII code for left bracket and right bracket would be more semantically correct.

Some discussion on this:
http://stackoverflow.com/questions/23526791/when-is-it-acceptable-to-leave-the-alt-text-empty-on-an-html-image-if-ever

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

Do you mean “Patch” files?

Those are for “patching” older version of the theme, such as upgrading from an earlier version to a newer version.

So, the “patch” file would be to “patch” version 1.2 of the NEWSMAG theme, to upgrade to version 1.3.

• This reply was modified 11 years by simchris.

You can pretty much *not* use the Envato plugin for anything, as it never worked right for me. WP can’t auto-update the theme as it’s not a free theme in the WordPress.org repository, so typically you always have to manually update a commercial theme, unless there is specific hook added by theme developer (Woo added this very recently, for example).

When I activated the theme nothing was sent to Envato, so I would not worry about it.

I manually update all my sites 🙂

Dunno. My category feeds all work correctly.

Could be caching issue. Perhaps try resaving your permalinks, as this sometimes needs to be done after updating WordPress to full dot version (e.g., 4.02 to 4.1).

Did you try the normal method with WordPress?
<!--nextpage-->

You may also find the theme documentation super useful; see the link right side of this page:
https://forum.tagdiv.com/how-to-create-posts-with-pagination/

Because Google is dealing with billions of things every moment in time. Same reason sometimes they only get the headline and not the full description. Nothing to do with your site/theme/content. Google just is not very consistent with it. Well known issue with all social media. LinkedIn has problems saving to groups consistently, Facebook sometimes won’t grab the image, sometimes gives you a choice of image to use, etc.

Basically you don’t have 100% consistent control over anything Google pulls from your site dynamically when using a submit tool. If the meta data is all there, Google will grab it “most of the time” but not all the time.

There is endless discussion of this on the Google forums.

Upshot: if it’s mission critical, sometimes you have to manually submit the story from your /posts/ page in G+; manually paste in the description, paste in URL, hit space, then see what it grabs from there. We have to do this routinely on different sites, regardless of theme, CMS, or content. Unfortunately.

Fact:
if you look at your meta tags and the correct image is listed for sharing in the OG tags, then Google will “normally” grab that image, most often this is your “featured” image.

Sometimes they don’t due to size of image, or inability to load that link, and will go for the first, largest image on the post that the bot can scan.

You can often try “fetch page as Google” from your webmaster tools to see what Google’s bot is “actually” seeing when it reads your page(s).

Ideally you would use the “suggested” plugin for the theme, “Contact Form 7,” or similar, to set the desired fields and how the information is emailed to you.

The default contact us page is just like the demo:
http://themeforest.net/item/newsmag-news-magazine-newspaper/full_screen_preview/9512331

The demo contact us page uses Contact Form 7: https://wordpress.org/plugins/contact-form-7/

Docs: http://contactform7.com/docs/

I think you can find my suggested pagespeed settings for the htaccess file in this thread someplace – perhaps do a search. (I added below 🙂 )

For the server side settings, you would need to test that as the actual settings tend to vary slightly depending on what OS you’re running, whether you’re using something like APC cache, etc.

Usually for the server side config, simply running with “all filters on” works (CoreFilters default) and you can also put in a config line to specify NOT optimizing the wp-admin folder.

We actually used this as a starting point, then tweaked
http://www.ray.45press.com/optimal-mod_pagespeed-configuration-for-wordpress-hosting/

If your web host doesn’t suck you should be able to request they setup the config file for a wordpress site.

Note the config for https is slightly more tricky, but if you’re just running http it’s not terribly complex once you try running with default settings on.

I then “dial in” the settings I want in my htaccess file per site, also so I can turn OFF mod_pagespeed to do site updates (!).

So

<IfModule pagespeed_module>
ModPagespeed on
ModPagespeedEnableFilters collapse_whitespace
ModPagespeedEnableFilters remove_comments
ModPagespeedEnableFilters rewrite_images
ModPagespeedEnableFilters insert_dns_prefetch
</IfModule>

and then switch to

<IfModule pagespeed_module>
ModPagespeed off
</IfModule>

when doing major updates such as WP version, theme update, or changing any logo file with same file name, or regenerating thumbnails.

Hope that helps. Don’t freak out if it crashes your site the first time. It’s a learning process and the Google docs kind of (totally) suck.

We also use “thumbnail upscale” plugin to make some of the smaller images a tad bigger, since we had a lot of 300x and 500x images and wanted them to fit 640x sizes. Fun 🙂

And of course “regenerate thumbnails” to get it all working right.

Had couple of ooooooold websites with same issue. The auto post thumbnail pro really saved the day for us. 🙂

Had same issue; we used Auto Post Thumbnail PRO from CodeCanyon; which will generate featured image from first image in the post. Doesn’t help with captions as far as I know. This at least allows the thumbnails to work site wide on indexes and modules. Then leave the setting in theme to NOT use featured image on POSTS, so you don’t have duplicate images at top of pages. Means you cannot use couple of the full width photo layouts, but this is one way to do it.

Or, you could figure out some tricky dbase hack to assign the custom fields to main dbase fields used by WordPress for featured image and importing all the images into the media manager somehow.

This is outside the realm of support for the theme, so you might have to consult a php programmer conversant with advanced hacks to WP dbase.

Make sure you’re setting up mega menu for the menu which goes above content, not the very tip-top of page.

Best bet is to setup working project on a website, such as
yoursite.com/wordpress/

then when you go live, move to yoursite.com
(directions on the wordpress.org show how to do this)

This way you can see what actually works on a real web server vs localhost, where things do NOT always work as expected, particularly plugins and optimizations for speed (caching, expiration headers, image optimization, etc).

Best to setup your site without demo data, which is really only useful for showing to a client. Best to start with CLEAN site, and import a “style” then put in your own original content, since the demo content cannot actually be used for anything in the real world.

Might try the WordPress codex (official docs). The “featured image” is a WordPress built-in function, not managed by the theme.

http://codex.wordpress.org/Function_Reference/wp_get_attachment_thumb_url

http://codex.wordpress.org/Post_Thumbnails

FYI, your site may get lower PageSpeed/Yslow score when using Google fonts (e.g., “open sans”) vs default fonts, as they need to load off Google’s server and that slows page slightly. With GTMetrix, note that it will tell you *why* your score is lower, when testing things – so pretty obvious to see what does the damage.

Are the plugins designed to work with responsive themes and are they updated to work properly with WordPress 4x (not all are)?

Many plugins use their own CSS for their content, and it that content uses fixed elements, the theme cannot magically make them responsive, such as tables, or fixed pixel widths set in the CSS loaded by the plugin.

Of course if the plugins work properly in the default responsive WordPress theme (did you try that?), then you would be more likely be able to massage them to work with the theme.

There is a solution in the forum for the occasional weirdness with the font, having to do with either being loaded via CDN, and needing CORS entry for CDN (see your CDN for help if using one); or you can re-render the icon font, this seems to work for some people who can’t see the icons. Do forum search for the icon font issue, as it was a lengthy thread couple of weeks back.

Should have been added to the docs as a “can’t see icons” solution, but I don’t think it was.

You get an error when you change themes or sometimes update WordPress.

Or, if somebody tries to access your theme folder directly, which is not normal.

Typically, click the “fixed” button. And if it happens again, look at your web site error logs to see what is being done to create that error.

This is more common when you load the demo content which isn’t real content and only for “demo” purposes not for a live site being managed in Webmaster tools.

In almost all cases it’s simpler to use an ad management system supporting shortcodes, then place the shortcodes into the appropriate spots in templates.

Oh, cool! That does work 🙂

Be sure to upload visual composer to version 4.3.5 from the all files download from themeforest. Visual Composer “broke” with WordPress 4.1. So, you need VC 4.3.5 to be able to use the custom editor.

If you simply cannot edit anything at all, that is different issue, often tied to perhaps a different plugin not working with WP4.1.

1) make sure you have Visual Composer 4.3.5
2) turn off *ALL* other plugins
3) make sure you can edit posts/pages
4) turn on plugins and figure out which is the problem.

Be sure to clear all your caches on site, CDN if used, and in web browser.

I always download the “all files” just because it’s easier.

I think the tagdiv folk were in such a hurry to upload a fix for WP 4.1 they missed that the first time out. Doh! 🙂