READ THIS:
http://premium.wpmudev.org/blog/keeping-wordpress-secure-the-ultimate-guide/

Well, it’s good to keep up on security issues, as WordPress continues to refine its core platform and will advise to update when security vulnerabilities are found (e.g., “cross site scripting” issues, or a problem with ajax/java, or comments injection, etc.). This is the nature of the Web. Technically “SSL” has not been “secure” the past 20 years, contrary to the term secure. SSL3,TLS1,TLS1.1 are all not secure. So, the web continues to evolve and mature in terms of learning to actually test for security problems.

Right now, both Newspaper and WordPress are as secure as “is known” if you have the latest versions of each.

You should also check for articles online for how to harden/secure a WordPress site (e.g., don’t let folks register, don’t have your admin username be “admin,” us a plugin like limit login attempts to block folks trying to guess passwords, turn off editing of files from the WP admin panel, make sure your web host uses a dynamic system like CSF to auto-block IPs probing your site, avoid OLD plugins written prior to 2015, etc.).

You can use tools like Securi to scan your site for known malware, and your host can do the same.

Note that Google massively changed their algorithms in January to deal with issues of content spam based on “brand names” and other things, so every site with lots of “brand names” and company names may have seen some major changes in SERPS.

Checking your Google Webmaster Tools/Search Console regularly and examining what’s going on there is also advisable.

Hope that helps 🙂

You need to wait for the theme update as the “bundled version” has to be tested as compatible and error free with the existing theme custom blocks and whatnot. You don’t have a licensed version of VC, so you cannot update from VC as you don’t have license with them.

Edit the footer section in theme panel, under “footer.”

See the theme docs, right side of page, which has a tutorial on getting started 🙂

Each plugin you add may load in its own custom CSS and Javascript calls. Not easy to “merge” all of that without some serious hacking.

For example if you know you’re going to use the same 10 plugins, you could open up the plugins themselves, and remove the loading of the css and js, then merge all of those into single css and js files and load in footer.

Of course, if you knew how to do that you likely would not be asking how to do it here.

Using the Speed Booster you can optimize some of that to load in footer after main page load.

Some plugins you can disable loading custom CSS and have it accept (inherit) the site CSS.

YOu can also hack the Google fonts to load Google’s CSS into your own style.css but that is also a bit advanced.

Anyway – just some feedback on what that all entails.

(Note: I am not trying to insult or belittle your opinion on this in any way; but as a 12 year WordPress user, and 2.5 year TagDiv user, I can tell you that you don’t need to “worry” about the versions of stuff included with TagDiv themes!)

Rule #1 is NOT to update all plugins as many times they have bugs, are broken and cause issues. It’s only wise to update to TESTED versions of plugins, and check the support pages for any plugin for issues PRIOR to install. Often the latest versions of VC, SliderRevolution, Yoast, etc., have introduced major major problems with new versions (Yoast often rushes out 5 bug fix releases the first week to fix “problems” which have done things like break sitemaps, demolish meta data, and break other plugins!).

So, good to perhaps plan a little better for how you approach “updates” as the “latest” is not always the “best” — it’s better to be wary, and savvy of NEW updates, and not fully tested/mature versions proven to actually work with WP, themes, other plugins, and best practices.

You can update plugins which are bundled for free with theme each time the theme is updated. Also note over past 2.5 years, TagDiv has been on top of releases patches/updates for every security issues raised.

You might want to look at things like the Securi WordPress blog and other resources which stay on top of all the vulnerabilities in WP and related tech.

Good to be wary, but it’s super safe around these parts! I’m an #infosec expert, so totally part of my daily routine around here. 🙂

Also useful to keep backups of your site periodically via FTP; for all your plugins, theme, and WP; export settings from theme and via the WP settings admin panel. Also learn to make periodic backup of your dbase via phpmyadmin (like WP warns you to do before upgrading WP!), so that you can easily “revert” back to a prior version.

It’s useful to turn off ALL automatic backups as frequently plugins like Yoast going to full dot upgrade, WordPress introducing a bug (like 4.1.1 did), or things like ACF4 not allowing copy/paste of Excel/tabular data in WYSIWYG boxes with their most recent update paired with WP 4.1x.

Any update can break a site!

Similarly things like WooCommerce, you need to review the changes with full dot updates (like 2.5) to see what you might need to change with theme files.

We use auto post thumbnail pro, but not sure if it works with flikr.
Also be sure to respect the usage rights for other folks albums which are nit in public domain.

The version included is a fully tested bundled version which is not infected by malware. The version included is way way past the old version which theme punch irresponsibly allowed it to have an attack vector. The version included free with theme download on theme forest right now does not have the old old vulnerability.

Its irresponsible to scare people without checking the changelog and version included ?

I think this is covered in the theme docs for the article ad spot.

Yes, WordPress finally fixed the bug they introduced in WP 4.4.1, which they fixed in 4.4.2 — the pagination issue was *not* related to the theme, but a bug in the core WP files.

So, where it says, for example:
<!-- Your NON AdSense code here - this ad will show only on phones -->

You would put in normal html, where you wrap an anchor link around an img link — and replace that commented item, of course.

Basic html is something like
<a href="http/link" rel="nofollow" target="_blank"><img src="mysite/images/image.jpg" width="NNN" height="NNN" alt="" /></a>

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

Bug in forum, when you post code with anchor links to images, it tries to load the HTML the first save, and then you have to resave in forum even if wrapped in code for it to actually render as code.

Andrei just pasted in the exmple from the theme docs, as fyi.
https://forum.tagdiv.com/newsmag-using-other-ads/

let’s see if I can get this to render 😉

<div class="td-visible-desktop">
    <!-- Your NON AdSense code here - this ad will show only on desktops -->
</div>
<div class="td-visible-tablet-landscape">
    <!-- Your NON AdSense code here - this ad will show only on tablets in landscape orientation -->
</div>
<div class="td-visible-tablet-portrait">
    <!-- Your NON AdSense code here - this ad will show only on tablets in portrait orientation -->
</div>
<div class="td-visible-phone">
    <!-- Your NON AdSense code here - this ad will show only on phones -->
</div>

seems to work.

• This reply was modified 10 years by simchris.

Exactly, CDN is best for edge hosting (being able to load frequently loaded content at a closer locale). A CDN is also useful if you get periodic traffic surges (e.g., featured on Reddit or something), as it allows you to get a big overload without having complex load balancing (we’re talking something like jumping up to 1 million views in a week or something … this happened to us once and holy crap!). And it can be useful for some common stuff like jquery as it gets cached in browser so is not reloaded if everybody is loading it off Google’s server.

Also note that some CDN setups don’t properly gzip/deflate everything unless you set that up — some are managed, some are just like your own site meaning you have to manage TTL, CORS, expiration of content to refresh, gzip/deflate, headers, etc.

Frankly http/2 is going to be more mission critical with hosting services, and http/2 + mod_pagespeed is very powerful.

WordPress cannot enlarge images; so consider adding the “thumbnail upscale” plugin which will allow stuff to enlarge and crop to fit the theme image sizes (you may have to do regenerate thumbnails also).

Good luck!

Not theme related.

You should specify the proper www vs non www URL in your WP settings panel, and/or explicitly set that in your wp-config.php file.

You should set your site to serve ONLY one version of your site, either http://www.yoursite.ooo or yoursite.ooo and *not* both.

You should let Google know which version is the primary, preferred version in your webmaster tools console.

If you have mixed versions of the URL in your content, consider doing search/replace via your mysql phpmyadmin to replace all versions of the “wrong” iteration of the domain.

If you explicitly specify the URL in your wp-config.php file, then WP might automatically redirect any requests for one version to the other.

Hope that helps!

Make sure you tell Yandex, Bing, Google which *version* of your site you will be using, and update your settings to match. Only YOU can do that. Theme doesn’t manage the URL.

Just one domain per license. You can see the license from your ThemeForest account as part of the downloads.

@larceny
in my case we have dedicated high speed server in Class-A datacenter. So for us, using most CDN stuff doesn’t help us. We tested this thoroughly, hence the effort to optimize “in place” vs relying on external resources.

For whatever your situation is, you will have to A/B test how it works for you and your content, layouts, hosting plan, etc., as that varies from site to site.

WordPress cannot enlarge/crop images. Try adding the “thumbnail upscale” plugin (free).

Might be a plugin for that ? Check the WP theme repository?

Or you could create a custom commenting form for site and call that data into a custom taxonomy/category, then build custom page from those data fields.

Or, you might be able to build a custom page layout based on calling the comments form data in database.

Might need to hire a developer for that.

bumps don’t do anything, btw

• This reply was modified 10 years by simchris.

Note that unless you use a plugin like Yoast SEO, the title tags for pages in indexes like page 2, 3 for a category (e.g., if you had 10 posts per category/archive, and 30 posts = 3 pages). Stupidly, WordPress defaults to having same “title” for each page — e.g., “Category Name Index | Site Name” …. so a plugin like Yoast SEO has addition of inserting a “page number” to make the title AND description diff…

e.g., for page 2 of a category index

title = Category name index page 2 | site name

description = Index of category name page 2, on my cool site

==
not sure this is your issue, but common WP issue not theme issue 🙂

Some bad plugins really mess things up and should not. Always read the reviews and support threads for a plugin on wordpress.org to make sure it is bith safe as well as compatible with wordpress 4.4x