Disqus works for us. Also shows the comment counts properly since Disqus puts that into the WP system the same way default comment system does, and the theme reads from that also.

Only thing that did NOT work was the comment count on the “author” index, which is known issue with Disqus.

I simply commented out the comment count on the author template.
(Actually, reminds me I need to do that hack for the latest version…. doh.)

Theme is working perfectly with my install of latest WooCommerce.

Known bugs are the sitewide top banner message from WooCommerce (e.g., “we’re closed today”) settings can cover the top menu bar. Likely some custom CSS to push entire page down the 50px or whatever would be needed if that message is used.

One other oddity, was the columns fitting when sidebar active. I use sidebar left, and I had some custom CSS from tagdiv team to fix for iPad portrait.

NOTE: this bug still appear in the site demo, where sidebar is on right …

the third item in row of shirts in demo drops to second row and “runs into” the first item on second row, pushing it to right. The main item info also drops below the featured photo, vs showing to right side on the actual product page.

This was supposedly fixed in the new update, but I note the version on the Themeforest demo does *NOT* show the updated CSS fix.

FYI, I’ve found it better to actually edit the core files and keep record of what you edit; than edit the child theme. Child theme not always functional with all plugins, and some CSS and other stuff not always editable, and technically it’s a “redirect” which Google not fond of even though WordPress considers it their favorite thing in the world.

For best speed and compatibility, I recommend editing the core files, and just keeping track of that (e.g., folder/file/line #, before/after code, etc.).

I’ve found that child themes are often an issue on our server, partially due to the CSS redirect. I try not to EVER use them anymore. It did cause issues for us, on multiple themes, not just this one.

Not sure this impacts you, but the other things that killed our server was a bot from Ukraine hitting our login panels over and over. “Limit Login attempts” plugin helped, and then in our case we had to block the entire country of Ukraine for abuse (!).

Optimizing the wp-config.php file helped a lot, too, putting in the actual paths to domain and also the the theme folder, to cut down on those queries for high traffic spikes. Couldn’t hurt 🙂

Easiest way to do this is actually using the YOAST WordPress SEO plugin. That’s what we use. Also allows you to insert verification elements for Bing, Alexa, etc., and manage the title and description tags for all the category and tag pages. Much easier than doing all that yourself.

Alternately you could try editing the header.php file in the theme folder and insert the code there.

eg. put it right after this line
<link rel="pingback" href="<?php bloginfo( 'pingback_url' ); ?>" />

If you use GoDaddy with that big “clear cache” button on the admin panel for WordPress … with a client project I found I had to hit that puppy twice to actually clear cache after doing any major changes to site.

On the “welcome” tab for theme panel, note options at bottom “install demo data” and “import theme styles.”

Demo data typically for working on blank site (not mixing with existing live site content), while the styles import custom CSS to change layout colors/fonts.

Maybe just get a refund and get on with your life?

Love the personal insults. I feel special.

• This reply was modified 11 years by simchris.

Weird. I’ve been using theme for 14 months and have not had this issue.

So, obviously…. I am no help whatsoever! 🙂

Sorry about that.

@deanhankin

“sarcasm isn’t smart by the way. It’s arrogant.”

Have a nice day.

@nelito
I never said anyone was wrong for complaining.

We didn’t need to modify anything on the server to use the theme.

Normal server optimization of WordPress is theme agnostic. TIME magazine had to optimize their severs for WordPress, regardless of the theme they are using.

@deanhankin
VC’s so called “limitation” only surfaced with the most recent version. After almost 2 years of use by TagDiv with tens of thousands of happy users, I would venture it wasn’t a bad choice for a visual platform. The visual editing is the main reason many folks bought the theme — without a plugin like visual composer along with all its prebuilt and custom modules there is no other simple way to do this kind of layout.

That being said, we here are playing with a “lean framework” again, and testing stuff like this: https://wordpress.org/plugins/siteorigin-panels/

For some of our sites, we are looking into “lean layout” again vs “complex layout” where high demand news site doesn’t need a fancy “magazine” layout where the look/feel is a factor in audience hanging about and returning. For example, one of our oooold sites, running Canvas: CaliforniaNewswire.com — not as pretty as FloridaNewswire.com, but very lean by comparison, and not really optimized at all.

As to arrogance… it’s up to you to research and learn the tools of the trade. Hopefully you’re learning from all of this 🙂

In any case, I will shut up now. I am not “defending” the theme (or VC) against your issues, I am simply saying that not everyone has the issues you may have had. For some it’s a one click install process and a site can be completely switched over in a few hours. That’s pretty powerful for a $50 investment.

Things change with all WP materials. WooCommerce updates, breaks stuff. Waaaah! Not the theme’s fault. Revolution Slider has security vulnerability. Waaaaaaah! Not the theme’s fault. WP 4.1 breaks plugins. Waaaaah! Not the theme’s fault. People expect a hell of a lot for $50 these days.

Cheers.

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

Well, it does say it uses Visual Composer. And it’s only been a couple of weeks since the latest version of VC kind of went off the rails. We’ve been using it with the Newspaper theme for 14 months without any issues at all, aside from one other bad version we skipped.

Hundreds of themes use Visual Composer, so it’s not unique to TagDiv.

And not everybody is crashing their server using it. Only some, which is where the problem comes up.

Obviously smart folks should research any framework or plugin a theme requires in advance if it’s mission critical; test usage then rollback if not functional as needed. We’re still running LAST version of VC (except on one test install) due to this issue.

Hopefully next iteration of VC will be more “CPU/RAM friendly!”

Caching problem. Not related to theme.

You will need to fine-tune your caching setup; check online forums for W3 cache. Also note some versions of Chrome cache the site from last visit and then update when it detects new version.

Caching is usually the problem. We went through this with Amazon CDN, where my brother in Washington state would see diff. version of page (old CSS).

Ultimately during development we don’t use CDN or anything, get site working, then do anything with CDN/caching, etc. as “last mile” of the dev process.

Theme works great for us.

We waited on using the new Visual Composer, as I always “wait and see” with any new major upgrade to “related” products.

We deployed one site in a weekend (floridanewswire.com) … which was switchover from a 2009 WordPress theme which was basically falling apart as no compatible with WP 4.1.

As with all things where you have interconnected elements, web server, php optimizations, WordPress optimizations, theme, and plugins all interact, and it’s a process to “fine tune” that for your use case.

Obviously very high traffic sites should not be using Visual Composer, sad to say. A pre built “easy to use” theme such as this and the many others using VC are designed for quick deploy as we did with FloridaNewswire.com or Ga-Ga.com — it’s not “lean code.”

For high traffic sites, ALL good developers know you need to look for cost saving on queries for php management and/or use good caching to serve static pages with minimal live data calls, so that the new content is taking brunt of traffic and legacy content is not as rich in data push/pull.

This is why it’s a tradeoff — you can’t have “one click easy” and “lean code” … just like you can’t have 100 things on a page and have it be fast. You either need to have 50 items, or faster system (e.g., we have 1GB switch for our server vs normal 100/base; super high demand systems get dual 1GB, or 4GB connections, or 40x the average 100/base port on typical server or VPS which is shared among 4 containers).

Ironically, I am pondering going back to “lean code” vs “overload code” as the current VC is easy to use, but wow, they need to figure out a way to “design” then deploy a snapshot. Just like you don’t give somebody Photoshop file with 50 layers, you give out a “flattened” version for actual use. VC needs to implement a “snapshot” deploy version of its code to allow development side then live use where the code isn’t such a burden on the system. Not a fault of the theme, obviously.

As always, your mileage may vary. Just some thoughts for the day.

On your downloads page on themeforest check the box for notifications.

You might have to also use some kind of comment removal system or plugin; we use mod_pagespeed for that.

Note however the style classes are somewhat unique, so a savvy person could figure out which theme you’re using from that.

• This reply was modified 11 years by simchris.

The current version of Visual Composer is a memory hog. Not directly related to theme.
Hopefully next version will be better.

Ironic how so many people were whining about not getting the latest version of VC the moment it was released, and now they have it, it’s not that great.

My site has 95 speed rating without modifying the speed booster file, using all my recommendations.

Render blocking css/js are not a deal breaker for the web. If you can fix everything else you’re good.

Of course, I’m spoiled with 12core XEON and 32GB RAM.

Simply rename the theme folder, and edit the style.css to your new theme name.

This is described in the WordPress official docs (codex) which are a great resource for learning how WordPress works. 🙂

REF:
http://codex.wordpress.org/Theme_Development#Theme_Stylesheet

Again: don’t ask questions here! Post a new thread for support. I won’t answer any question posted to this thread !!!!

Additional important suggestion for site optimization

CLEAN HOUSE ON PLUGINS
1) REMOVE all un-used plugins. Not using revolution slider? Get rid of it. Not using animated GIF image capture? Ditch it.

CLEAN HOUSE ON THEMES
2) REMOVE all old themes. Moved from another theme, and know you don’t want to go back; save/download old theme folder; remove from server. Remove any other test folders. One site of a friend I looked at had 8 old theme folders going back to 2009, including one with an insecure version of Timthumb (pre fix). Still have the ooooold WP default, and twenty-ten themes ? Ditch em. Keep *one* of the stock themes (e.g., twenty-fourteen) and remove the rest.

All that crap can slow down site, but also potentially compromise it, if an old theme has some vulnerable code in it.

my ears were burning 🙂

SEE:
https://forum.tagdiv.com/topic/tutorial-chriss-custom-optimizations-for-functions-php-etc/

I’ve seen that happen with gallery layouts. Not really a bug, as page is loading “what it can” vs waiting for everything to load first.

• This reply was modified 11 years by simchris.

WHERE are you trying to place the license key in your setup?

That’s a decent hosting plan. I have dedicated server with SoftLayer but some of their pricing has gone up since IBM bought them. And of course it’s bare metal, meaning they don’t provide support for apps or any software, only the hardware.