Home User profile
tagDiv Member
Christopher is a long time WordPress user. Anything else you need to know is private ;-) I *do not* work for TagDiv, but I've been using their themes since late 2013.
simchris
tagDiv Member

Ah, I thought perhaps you’d done a proper dbase update prior to installing new theme.

That way if your dbase got messed up or something you could revert back, and revert back your theme to prior version, which would put everything back “as it was” prior to new theme update.

I don’t work here; but that’s what I do.

simchris
tagDiv Member

theme has zero to do with your sitemap, sitemap indexing, or Google search console.

have you checked your site with Search Console for errors?

Have you checked your sitemap works?

simchris
tagDiv Member

I think there is a plugin out there for ‘guest posts’ with that kind of add-on.

Maybe Gravity Forms with their paid add-on?

simchris
tagDiv Member

Did you also revert your DB back to the version saved prior to doing the NP 8 update in your PHP / MySQL panel ? This is likely useful in this case.

simchris
tagDiv Member

Also try testing one of your posts with GTmetrix.com to see if you still need to optimize your server setup, htaccess, time to live, image compression, etc.

simchris
tagDiv Member

In theory you could simply use the raw code box, and put the PHP function there? Worth a try. 🙂

simchris
tagDiv Member

Works with WP 4.8 just fine.

There is no *certification* for themes to work with WP versions.

WP 4.8 was primarily bug fixes and house cleaning and not a full big version update from 4.75. Meaning anything that does work with 4.75 should work with 4.8 just fine. 🙂

Not sure that helps. But it works with 4.8 🙂

simchris
tagDiv Member

It works for me and many others.

Likely a paths issue with your staging setup, just as the error states.

Does your wp-config.php have the staging path explicitly set? That can often be issue in that it’s trying to load the mobile theme off the domain and not the sub domain path — but dunno. Don’t work here.

Obviously if you still have the mobile theme setup from newspaper 7, you’d need to fully remove all of that, clear caching, etc., before enabling the mobile sub theme in NP 8.

Food for thought anyway. It does work on ‘normal’ domain setup, but perhaps not how you’re doing it.

simchris
tagDiv Member

You likely need to be more specific. All the theme does in place the AdSense code on page, and has zero control over WHAT ads are shown, if any. Meaning, sometimes ads break, timeout, are wrong height, are blank, etc. — nothing to do with theme.

I don’t work here — just comment.

simchris
tagDiv Member

PHP 5.4 is really slow and a dog with Visual Composer plugin; it would spike our old server processes from .09 to 70.0 (!!!). With TDC and PHP 5.6x we’re running at .05 (!). Note PHP 7 is also good choice from 5.4 and below. Next version of WordPress won’t even work with PHP 5.4 and below, I believe (or is coming soon). 5.6 is the “in between” old moldy tech and PHP 7. (5.6x is kind of like the PHP ‘6’ that never came to be.)

However, some old hosts including GoDaddy, still do 5.4 as it’s compatible with any OLD tech, but *not* very well suited for new tech (e.g., after 2013!).

Simply moving to TDC vs VC for your page builder will do wonders right there.

simchris
tagDiv Member

Add to the footer.php file.

simchris
tagDiv Member

Wpion is different theme from tagdiv, uses td composer only. A little cleaner and simpler, more like newsmag. I use all three themes.vgreat stuff.

simchris
tagDiv Member

Some people seem to get this and only thing I’ve been able to figure out — and I don’t work here — is Envato may be blocking some IPs for abuse, or too many activations vs number of purchases — but don’t quote me on that. I only had this issue once in 5 years and it was due to my local ISP having issues with connections to the backbone; could not reach Amazon either.

The manual way worked in that one instance for me, however.

But TagDiv will follow up, soon, I’m sure.

They likely need to make some kind of “what do do if….” section in the theme docs for activation on this. Usually you can also try to contact Envato tech support via the help links on the ThemeForest website, too!

( again – I don’t work here and don’t speak for TagDiv, but have been using their themes for several years, and longtime Envato/ThemeForest customer, too … )

simchris
tagDiv Member

Also – just as a tip, you can run these kinds of compliance tests against the ‘demo’ versions of themes before purchase to test in advance 🙂

simchris
tagDiv Member

Did you try to install the theme zip and not the ‘all files’ zip which won’t work?

Did you try install via FTP if your system times out or has permissions issue?

You are able to send login info to their contact@tagdiv.com email, and have been for many years now, to not post sensitive info here.

Don’t worry … TagDiv does great job helping folks. Hang in there! 🙂

( I don’t work here. )

simchris
tagDiv Member

You can add AMP right now; we’ve been doing it since it was in BETA end of 2015, with TagDiv themes. Use the AMP plugin from Automattic, as it’s from the same people who make WordPress, and developed for pro clients on WP like TIME.com etc.

PWAs are primarily to serve data in separate app, which is not really part of normal ‘website’ theming. Generally you should decide if you want to serve an AMP version of the website or a PWA. But unless you have special use case, for “most” people the AMP version and a quick, clean “responsive” website, or mobile friendly sub-theme as with NP works very well.

See: https://www.smashingmagazine.com/2016/08/a-beginners-guide-to-progressive-web-apps/

Google will rank your site better ON MOBILE with AMP, as it provides option for mobile users with compatible devices (but not all) to see different version of site streamlined for the mobile environment. It doesn’t get seen by desktop users and the viewer must be using AMP compatible device/browser.

Responsive works with everything. Mobile sub theme works with all mobile browsers (aside perhaps from some micro browsers).

A PWA — in theory — can give you a multi-level platform to serve a mobile app outside of browser, then fall back to AMP, then to mobile sub theme, then main responsive theme.

Presumably this will take some planning and research to implement.

But you can get AMP setup in an hour. So, I’d start there 🙂

simchris
tagDiv Member

Your site, or your PC might have malware.

Did you scan your site with Securi site scanner?

Did you scan your PC with anti-virus/malware/windows defender etc?

Is your version of WP up to date?

Delete old un-used plugins and themes?

Change all your passwords?

You have a *lot* of social plugins running, so likely one of those; try disabling them all one by one to see what gets rid of it.

simchris
tagDiv Member

Probably need to read up on some tutorials on how to do that properly as not related to the theme itself, but your WP install and paths.

Did you put explicit path in your wp-config.php file?

Did you search/replace anything in the post meta with old paths, like images?

Did you fix any paths in the admin panel like link to logo, rss feed, etc?

Did you disable then re-enable any plugins which look for /path/to/plugins

Clear all caching?

simchris
tagDiv Member

WP Maintenance Mode is very popular, worth a look; and similar items.

Worth looking in the WordPress.org plugin repository for “coming soon plugin” or “maintenance mode” plugin; as lots of choices to try out to see what works for your use case.

Good plugins are theme agnostic and work with any WP install.

  • This reply was modified 9 years by simchris.
simchris
tagDiv Member

Helps to use PHP 5.6 and higher which has opcache built in as good starting point.

WP SuperCache works well for most because you’re loading static pages, which is preferred by “most” hosts as if you have 1,000 domains on a box, if they all use too much memory, not enough memory to run all the sites.

If you have your own server, consider using Varnish;

OR: also nextgen tech like https + PHP 7 + http/2 is the “new way to fly” as the entire page is compressed into one packet, not a bunch of pieces, and THAT gets cached by server.

The main issue with CPU, is to switch to using TD Composer vs Visual Composer. Seriously.

simchris
tagDiv Member

Well, how can it be responsive then?

You might try making a custom class with a size like maxwidth="99%" or similar and wrap your code in that div, or find out the class applied to the ad code.

Basically if the ad isn’t responsive it will break the layout. Theme can’t do that for you.

simchris
tagDiv Member

Basic HTML – use anchor links.
Lots of tutorials online for learning HTML.

e.g.,

<a href="URLforadtogo"><img src="/mygraphic.jpg" /></a>

Just create a custom ad, or simple text widget and put your HTML in there. 🙂

etc.

( I don’t work here. )

  • This reply was modified 9 years by simchris.
  • This reply was modified 9 years by simchris.
simchris
tagDiv Member

Isn’t there an option on the page to enable “no duplicates” — as also found in the docs? I think we switch that on when on the ‘page’ we build for a home page.

( I don’t work here. )

simchris
tagDiv Member

Generally the only way to eliminate the render blocking with Google fonts, is to move the CSS into top of your style.css to load fonts “directly” vs loading the .css sheet off Google’s CDN.

You can also try adding your custom CSS to bottom of style.css vs adding to theme panel.

Finally, you can also ‘view source’ on your page to see WHAT is actually loading at top/bottom of rendered post pages.

Not sure that helps or not.

simchris
tagDiv Member

You might have to recreate that as photo licenses generally not included with themes, nor are fonts. So a copy of that PSD on layers would not have the font, as you would need to have the font installed on your PC. Probably simpler to recreate that with a royalty free licensed image for $10 and use a comparable Google font or similar to make your own?

( I don’t work here. )

Viewing 25 posts - 2,351 through 2,375 (of 9,335 total)