We just edited the header.php file to add the meta tag for author.

Using Yoast SEO plugin helps too.

Might be a time out issue or redirect issue since your URL redirects to the https:// version of domain, then throws an error that not everything on page is secure.

Likely first step is getting everything loading on page to be https ..

Well on mobile devices “responsive” images have to be resized as there is now way of knowing what the actual thumbnail size might be if you have 3 images side by side in a grid; well the width of that grid might change depending on the device.

You *could* add more image sizes to your functions file to build those additional sizes; keeping in mind you might end up with 20 images per raw image (!). If you have the storage space or using CDN, might be worth it.

Or, consider using something like mod_Pagespeed with your hosting provider — which is what we do — if 50 people request a new image size, scaled from larger image — it MAKES ONE and caches it. Wicked cool.

Or, ignore that suggestion and go run the official Google PageSpeed Insights check and if they don’t bug you about those scaled images, just ignore it.

Limit queries on home page, but mostly on post pages …

e.g., limit loops used in sidebar; use only 3 related items bottom of page, not 50; don’t use loops/queries in menu bar, or only use one.

Turn off the comment counter on posts/comment it out.

Stuff like that … helps!

You can turn that off from the
theme pane > posts settings 🙂

I do that too … 🙂

Comments box still works.

example
http://musewire.com/paula-cole-announces-new-album-release-7-a-soft-and-soulful-review-of-a-7-year-life-cycle-8295/

Also note that Google News gets the last updated time from the XML news sitemap and not from the page itself, if that matters to you.

The main Google ‘bot should be getting ‘last updated’ from your main XML sitemap also; so good idea to check that is being properly added to the sitemap (eg., via Yoast SEO, or similar).

I was going to try the “woo sidebar” widget as we’re still using that on some older sites and it *does* work with Disqus. I have not yet had free brain cell to try that on Newsmag 1.7 yet, but will be doing so soon… was waiting to see what dust settled and if a 1.71 might be pending.

Yes – 🙂

I did try changing some users roles, and obviously authors, editors, and contributors all should be selectable. Although …. on on some sites if they have 200 authors that is going to kill that. Never a perfect solution there … perhaps adding a box for entering a single author ID would probably work best.

Thanks 🙂

Perfect. 🙂

I don’t think so …
obviously if you kept the files from your last install, that’s always best.

I think they can send to you if you email contact@tagdiv.com

So bizarre that some systems have issues, others don’t.
However I do recall going through this kind of thing with other themes over the years — where 90% of people had no trouble and for us every update broke their stupid custom “framework” which had to be updated separately. About five differnet big WP foundries just could not be consistent. Ended up just using Woo Canvas for everything for several years out of annoyance. “So far” we’ve been lucky with TagDiv as I think we are running the same kind of system they use for their demo site, testing — so, in our case we’ve not had all the wonky issues 10% of the userbase have seen. Sucks for those suffering these things. Totally been there.

Virtual hugs all around. 🙂

@fdiengdoh
me too! hate it (admin bar)! I used to add that, now I just uncheck the box in my “user” setting. That code is great when you have lots of users to make sure it’s not there. 🙂

Been too busy to add update here on how to optimize the Google fonts stuff. Will get to that eventually.

• This reply was modified 11 years by simchris.

Hm. Weird. I sit corrected. I wonder if new version has some issue with Nginx …
presumably you already updated your php.ini file to increase memory, upload size and execution time from the often insufficient defaults. That was my issue with VC initially.

Probably best to roll back to prior version of VC and see if that works?

Note the facebook sharing has nothing to do with the modules …. that only impacts what is printed on the site.

The Facebook sharing element — if you read the FB docs — comes from the “author” tag in the META data.

So, to remove that in FB sharing, you’d need to eliminate the author tag completely, or perhaps do what we did on one site which was hard code the author tag with the sitename, so it might print on FB ss

sitename.com | The Cool Magazine Name

Hope that helped 🙂

I think that is the issue with code used which does not work with ooooold versions of php on some servers.

For now roll back to older version and wait for 1.71 update of theme.

They are closed weekends so bumps don’t do anything.

Did you try editing the template files to remove the author slug ?

There is more than one template … so if you’re a specific template you’d need to comment it there too.

I think you can also try the “search” template. I always edit that with each update to remove breadcrumbs.

look at the header.php file in the theme folder

paste before the closing head tag.

Or, if using YOAST SEO plugin, there is a box in that plugin to paste in your confirmation code.

I actually found it easier to download the verification html file and ftp that to my website root, so you’re not tied to any theme or plugin for that. 🙂

4.4.3 with 1.7 is working on my site.

Just built new home page.

You might TRY deleting the old js_composer entirely
uploading new version via FTP.

Use Chrome and not I.E. (if doing so). Clear all caches first.

Try going to your page, then click “save” (update) right side.
Then try adding new item.

Seems to work okay … but VC is a very persnickety plugin, it seems!

I went from 1.4 to 1.6 with zero problems last week.

Last night I upgraded site from 1.4 to 1.7.

Only issue I had was NORMAL issues of some of the sidebars getting reset (meaning some of the widgets didn’t save); and had to “resave” the homepage just to reset it. All settings normally carry over due to the built in “transient” settings of WordPress. Everything else was exactly as I’d left it.

You should also be regularly doing backups of your site, theme settings, etc.

If you made custom changes to the core files (e.g., style.css etc.) you would, of course, need to apply those changes to the new files.

1.7 works fine with couple of minor issues, depending on if your hosting co is running old php tech which is really somewhat deprecated.

So far only bugs I’ve had are one spacing issue in a stock WP recent posts widget, and the modules in Visual Composer won’t let me filter by any author except myself.

Everything ELSE is working fine for me in 1.7, but SOME people are having some weird issues which are common with all WordPress site changes/updates like this. Main issue is the use of some code in the theme which is not playing well with OLDER versions of php (we are running PHP Version 5.4.22).

So, check the version of PHP you have … if 5.4.22 or newer, should be ‘mostly’ fine.
OR: wait for a dot revision of 1.7.1 next week, I’m guessing.

Don’t know if that helped or just re-peated the other posts, but my two cents anyway. 🙂

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

Then likely you have some other issue with caching, or didn’t make the page you built public, etc.

If you can preview the page when editing the “page” and it works, then make the home page the static page — that is managed by WordPress and your .htaccess file being writable.

You might try resaving your permalinks?

Clear your website cache if you have one.

I did some house cleaning on one of our bloated dbases, for a site that went live in Jan. 2006 using WordPress 2.0
— I’m actually migrating it “right now” on my other monitor to Newsmag 1.7.

Current dbase size : 189.1 MB (!)

So, I feel your pain 🙂

Supposedly it’s a minor code incompatibility with some web hosting companies still running old/outdated versions of PHP code. We’re not having any issues with our server which was deployed as of Dec. 2014.

Basically, your hosting co is running some ooooold code still for client compatibility, which they should be forcing their clients to move to “modern” codebase for performance and security.

NOT your fault !

Supposedly you either have to
a) roll back to prior version of theme
b) edit couple of files temporarily to use 1.7.0
c) wait for 1.7.1 to be posted / and approved by / ThemeForest …

I don’t work here, just what I’ve gleaned from the replies from Marius for those having issues when many are not having issues at all on the basic upgrade/install procedure.

(I’m actually doing this “right now” for one site I just updated from 1.6 to 1.7 but wanted to change layout …)

Hi, typically you need to
a) setup a page, create layout with visual composer, preview
b) go to WP settings > reading > first section
change to using the page name you created for home page
front page displays
[x] static page
>> page name

Hope that helped 🙂

Often what I do is just do a simple 2 column layout with something like

[ 2 col ] [ 1 col ]

in left column use block 11 for latest
in right column use widget area, temp use the default sidebar

make that live so home page works

then I create second page to mess with layouts until I like it, then swap the static page used for home page and delete the first page.

Hope that helped 🙂

See the other post related to how to disable lazy loading of images. This is a great feature for mobile, but can have some unpredictable results with “some” setups. All major news portals are implementing this, as it makes the mobile experience faster, and long pages load more quickly, but I have also seen this kind of thing happen when I tested this myself with the Newspaper theme a year ago and chose NOT to use “lazy loading” … as sometimes it ended up being “no loading at all.”

It’s a great new theme feature, and SHOULD be there, but no way to one click turn it off.

You will need to edit a couple of files to turn that off for now, it seems.