I was also curious how this will play out with all my various licenses “support ending” next month.

Note there *is* a discounted extend support option found on the download page for theme in your themeforest account.

In the docs, it recommends YOAST SEO. 🙂

I was waiting for my site backup to complete and doing my “quick zoom around the web …” including here to see if anybody blew the place up yet (kidding) 😉

I’m trying NOT to poke my head in here anymore, but keep having these little windows of time to kill …

Yay!

Stupid plugin!!! 🙂

See the sticky post about the bug in WordPress 4.1.1

I guess you could try both methods …

I use that line in there as it changes the default setting from 90 to 50 (although 45 or 55 works better for some folks depending on size of thumbs) as used by WordPress generated thumbs — if using a plugin that calls on GDlibs/ImageMagick on server directly, then the setting wouldn’t impact that.

I’m not sure if EWWW or Smushit call the server libs directly, but one would presume so. I’m using the default WP setup plus mod_pagespeed for optimization (including on the fly conversion/caching to WEBP format), so not using any plugins.

Idea behind that is that thumbs don’t need very high image quality as they are just pointers to the post where the good full size image lives. WordPress presumes every image should be as beautiful as possible at every size, which is kind of dumb in the real world.

Good idea to disable automatic uodates on your website in wordpress!

Maybe the bug in wordpres 4.1.1?
See the sticky post for more info.

Usually you can see those kinds of errors by using F12 to get console view in modern web browser like Chrome which shows rendering errors on page 🙂

Technically you can’t very easily … since they are child categories and designed to show the child and child’s child.

Not a theme issue.

In theory, you could create a custom template for the two parent categories with custom loop to EXCLUDE the nth child category in results, but likely need to get programmer to help you with that.

Might want to read up on the WordPress docs/codex on how categories work — as it’s common with all themes as that is part of WP and not the theme.

See – https://codex.wordpress.org/Taxonomies

• This reply was modified 10 years by simchris.

See the sticky post about the bug in WordPress 4.41 regarding pagination.

Ideally you should only be serving one version of your website, either http or https and not both. If setup as https, you should have 301 redirect for all http requests to https version, per Google guidelines. Adding implicit https URL in your wp-config.php settings also helps.

For those who find this in search; this is managed from the USER setting in WordPress; not part of theme.

As I said, this happens if Google pings your site while updating — if it tries to load a page or something where only half your theme/wordpress is there during update/switcheroo, it generates a server error as it’s supposed to. Note it *is* a problem if you get this every day, multiple times a day, dozens of pages, etc. But this WILL popup couple times a year.

As noted, you can just “mark as fixed” and save. Done. 🙂

Regardless; not all themes are the same. Some themes are just text, like the default ones with WP; some include complex page builders like Visual Composer. If your theme has 5 options it doesn’t need much horsepower, with 50 options it does.

Only you can optimize all the problems with your site from the GTmetrix and Pagespeed Insights reports. You’ll have same issue with any big complex theme like this.

But once you optimize your site, it works great.

20 sec page load is an issue with all the problems listed which impact how “fast page loads…”

If you’re loading large images vs compressed, if the page elements are not gzip/compressed for browser, it takes 3x as long to load.

You will have to follow the guidelines to optimize your site for ANY complex theme.

Ideally you site should serve only one version of site, and have the other version redirect to the single version you’ll be using. (eg., setup site to redirect non www to always use www). Otherwise any caching system you might be using can get confused, as it’s two different sites, technically, with some elements.

I think you can remove that from the particular post template(s) you’re using. Requires editing the post template in your theme folder to remove that little element on the post.

You likely will need to change your settings for WP super cache per the theme docs.

Since hitting refresh on the page does not show an increment when page is reloaded, it’s not working properly due to your caching setup.

You have some errors on your page:

Given URL is not allowed by the Application configuration: One or more of the given URLs is not allowed by the App’s settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App’s domains.

Note that only you can optimize your own site/server — no theme can optimize problems with your site setup such as caching, time to live, image compression, gzip/deflate, external tools like Jetpack that slow things down. You will have problems with all complex themes unless you learn to make the optimzations needed BY YOU to speed up your site/server/hosting account setup. This is true of *all* WordPress installs, regardless of theme.

(I don’t work here; just been using WordPress for over 11 years …)

You might try testing one of your posts with GTMetrix.com which shows the better examples of the things you need to fix with examples.

Again — site optimization is theme independent!

Note:
a) not all plugins are fully updated for WordPress 4x
b) not all plugins work properly with the bugs in WP 4.4.1
c) not all plugins fully follow proper WP modern plugin programming guidelines (‘the law’) as laid down by Automattic..

So if one or more of those is true a plugin might not work at all with more complex themes.

Main trick generally is to turn off all other plugins except visual composer, clear all caching, turn off any minification tools, check to see if the plugin you’re using works, and check the console for errors (F12).

Check the plugin has been updated for all the recent changes to WordPress. if the plugin has not been updated in a while it likely will stop working.

I should mention that adding a copyright notice to your images and the META data, using very unique filenames (which is what we do) and using something like DIGIMARC to watermark the image is useful for tracking theft.

Not really. My company used to make some software to trick browsers over a decade ago, but other than the pokey Artistscope software, problem is anything that loads on your screen is in the graphic buffer and can be captured with stuff like Snagit, or the simple print screen function in Windows.

You can add the meta tag for noindex for images to keep some search engines like Google from not archiving them.

You can also make sure your RSS feed is excerpt only with no images.

But if your page is on screen, the image can be captured. Period.

When switching themes in WordPress if Google happens to ping your site while it’s happening, it will generate 500 error. This is normal. Just marked fixed and get on with your life 🙂

(admin – another one to add to FAQs page at some point! )

Here is how to get the ‘error console’ in Chrome browser on Mac:
https://developer.chrome.com/devtools/docs/console