You need to install an SMTP plugin to use actual domain email.

Most common method now is without the www, as it’s technically redundant (it means “world wide web”) — it used to be more necessary when there was anonymous FTP (e.g., http://ftp.myname.com), or funky mobile sites like mob.mysite.ttt etc.

So, you just need to pick one or the other, set it to “resolve” to just the one version, which you can setup with your A NAME/CNAME records on server, etc.

and then only ONE version should have working canonical tags in the meta to say which one is the “official” one, and anything else is duplicate so go to the real one.

Also, in dem olden days, SSL/https only worked right with www – which some sites are still doing (eg., https://www.amazon.com/ ).

Neither version is better nor worse for anything as TLD not used for SEO, according to Google, so as long as both work, but only one is the canonical, use whichever you like best (if your server only supports www for https then go with www).

Note the main reason most are no longer supporting the old version of Opera 12x is lack of support for modern TLS ciphers; basically SSL1,SSL2,SSL3,TLS1 are all insecure and are being deprecated over the entire web, and most have to stop using TLS1.1 at some point and *only* use TLS 1.2.

This means old version of Opera won’t work with *any* https site that is setup properly very shortly. Much like old versions of IE which can never be updated for new security settings.

You should be aware of this issue if you rely on Opera for your visitors, and may wish to setup a sniffer to popup notice to update their version of Opera, much like Firefox did once upon a time, and even Chrome.

Especially on mobile, since this is moving to https everywhere, including shared/free SSL certs with new versions of Plesk, Apache, Cloudflare, etc., etc.

Basically Opera 12 won’t work with anybody running modern https — and so should be abandoned as an insecure and obsolete browsing platform.

This is not 100% specific, and just general comment. You need to research the actual specifics on all of this, but you can also learn about this in the Opera forums.

Opera 27 and up is the solution for modern mobile and website support. Opera 12 should be deprecated asap.

(( I don’t work here; just been dealing with webdev for 22 years, and our sites are PCI-DSS certified and we have to deal with infosec crap on daily basis. ))

Chris S.

• This reply was modified 10 years by simchris.

may be helpful

https://codex.wordpress.org/WordPress_Feeds

The zip file is found in your ThemeForest account under ‘downloads’ …

This is a commercial theme, not part of WordPress.org – so you can’t update it from there. You need to update it from your ThemeForest account, the same way you installed it the first time. See the docs ( links right side of page) on how to update theme 🙂

Note that Chrome browser “caches” web pages on their CDN to load faster for web users, and depending on the time to live on your cache on your website you need to clear history in Chrome to see most updated page, especially if using mobile version on iPad, Windows desktop, etc. You can also use the developer mode in Chrome to force reload page.

Some CDN settings can be set too long for indexes which are updated daily/hourly, vs posts/pages updated weekly. This is unrelated to theme and impacts all sites regardless of theme or technology. Tricky!

Images working fine on home page and posts for me.

Try disabling the lazy load animation feature in theme panel.

Also be aware some reviews are from people who don’t know how to follow directions to use the plugin properly, and then like to whine about it on the plugin support pages. As with all plugins, one still needs to know how to test a plugin, then roll back if a new version has a glitch (common to *all* plugins, including WordPress!).

There is no penalty to trying a plugin out for yourself, as in all things. A lot of people hate Apple, too, but they still make great products, so reading some of the reviews for the iPhone and how it skinned their cat and ruined their marriage must be taken with grain of salt (e.g., be cautious in what people post, including those who make competing products!).

But again, just like choosing which type of cola is best for you, which pizza delivery service, etc., you need to decide for yourself. Try one, and if it doesn’t meet your needs, try another one.

I’ve been using YOAST SEO for many years now since we abandoned our in house tool which did many of the same things. It’s a little bloated, sure, but people keep asking for it to do something new and they add that in. However, they have also taken some things out, too. SEO changes over time, so too the plugin. It’s a fluid universe in webdev, so welcome to the circus! 🙂

Wordpress docs sounds like something you might want to read through based on all your questions here on the forum

https://codex.wordpress.org/Excerpt

Twitter does not always get the image. Sometimes it won’t show the image when you share, but when you go back it will have been processed and does show up.

You can test this with Twitter’s “twitter card validator” for any post you do, to ensure it’s setup properly 🙂
https://dev.twitter.com/cards/overview

Just a quick follow up for old timey sake, for those coming late to this party:

IMAGE COMPRESSION

QUICK TIPS:
Test a post page with GTMetrix.com — this will show you what you need to do to improve speed specifically, for example giving you examples you can download of optimized images for the post page you test to see how that impacts you.

Also, to compress thumbnails, you can change the default compression per my guide in your wp-config file, then “regenerate thumbnails” to make smaller versions. (AND: you should be backing up your site before you mess with it, obviously!)

Alternate advanced method of compression:
download complete image folder to your PC via FTP for backup then use one of the various PC software apps to compress/process all images, then re-upload via FTP. Here is one for Windows, as just one of many examples: http://icompressor.blogspot.in/

Or, if that makes no sense or is too difficult; make backup first, then try this nifty plugin, which is a PAID service after the first 100 images; but useful to test if it works for you:
https://wordpress.org/plugins/tiny-compress-images/

Test a post page with GTMetrix.com — this will show you what you need to do to improve speed specifically, for example giving you examples you can download of optimized images for the post page you test to see how that impacts you.

Also, to compress thumbnails, you can change the default compression per my guide in your wp-config file, then “regenerate thumbnails” to make smaller versions. (AND: you should be backing up your site before you mess with it, obviously!)

Alternate advanced method of compression:
download complete image folder to your PC via FTP for backup then use one of the various PC software apps to compress/process all images, then re-upload via FTP. Here is one for Windows, as just one of many examples: http://icompressor.blogspot.in/

Or, if that makes no sense or is too difficult; make backup first, then try this nifty plugin, which is a PAID service after the first 100 images; but useful to test if it works for you:
https://wordpress.org/plugins/tiny-compress-images/

Facebook will do this sometimes if there is more than one image; such as an optimized version being served for mobile, or a version converted by mod_pagespeed to webp format, or a background image and a featured image in post. Just pick one and move on with your life 🙂

Ignore the nag screens from Visual Composer. TagDiv tries to deactivate those, but the sneaky devils keep working in ways to have it pop up, much like Yoast was inserting settings update notices on first time installs of Yoast, which was dumb. Bundled version of plugin doesn’t need you to register it, insert key, etc., and the VC folks should be baking that in (see what I did there) to the bundled version license, but apparently not.

Upshot – it works. Theme works. But TagDiv cannot control all aspects of some of the bundled elements as those are built but the third parties. Kind of like the aribags in cars from last 10 years (so, am I comparing VC to Takata .. maybe I am, maybe I am not … you decide).

Have a wonderful day in webdev land! 🙂

( the ghost formerly known as Chris S. )

Useful to look at things like the wp-config.php file where you can specify the uploads folder for images, which all core functions then pick up automatically.

https://codex.wordpress.org/Editing_wp-config.php#Moving_uploads_folder

Wordpress official docs are great place to learn how core WP functions work. Most themes call standard core functions/paths and don’t set new paths unique to theme.

Also, you can set the explicit domain name in the wp-config file.

Note changing any of these does *not* change image paths already inserted into the posts or dbase. You must do a dbase search/replace to change that – it cannot be changed automagically anywhere else.

If an image was placed in a post at former domain, there isn’t any theme or WP setting to change that unless it’s dropping in featured image, where it *would* update. But anything “placed” into a post is there forever until updated in dbase.

Not sure that helps, just some pointers :-0

Most of the errors from post content that cause errors in AMP plugin can’t be fixed by a theme.

For example, if you use the “center” element in WordPress, that is an inline style, which should never be used in modern HTML, and only done with a class like <p class='mycenter">Sub Head</p> and not <p align="center"></p> … similarly, bad plugins which inject javascript into the AMP endpoint or “all templates” can’t be solved by theme, or AMP plugin, or cache plugins which minify the AMP endpoint template … these are all site issues unrelated to theme typically or the AMP plugin — only you can resolve that.

So, fault of AMP plugin “not working” is not the fault of plugin, but the content and OTHER plugins you’re using.

But again, most theme devs will *not* be adding AMP support as that won’t fix inherent problems with OTHER issues, like the ones you experienced and they don’t have time to help people fix their content for a $50 theme.

But, best of luck in your endeavors. This will be my LAST day posting in this forum, so cheers to all.

Peace out! (mike drop) 😉

Most of us have been using AMP plugin from Automattic with TagDiv themes since Nov. 2015; and with roll out of the AMP protocol. So, my pages are being served in AMP for several months now since it officially launched mid-Feb.

SO, why wait? You can enable AMP support “right now” with couple of clicks.

The official WordPress AMP plugin is working on 50,000+ WordPress websites NOW including WP VIP clients.

Since this is made by Automattic, who make WordPress, it’s the safest route to doing this and doing it correctly, to support WP posts.

This is why most theme devs are not adding separate AMP supportll just like it’s not necessary to replicate ecommerce or forums, when there are already WordPress-funded agnostic solutions out there, including things like a beta Facebook articles plugin, etc.

Just food for thought.

Hi
I am no longer active in this forum, but another person appears to have tweaked/updated the remove VC code for functions.php, which is outlined here:

https://forum.tagdiv.com/topic/disabling-visual-composer-makes-my-website-go-error-500/

and you can always ask TagDiv for the best way to do that with latest versions of themes, which continue to evolve.

Chris

I think my code was from over a year ago, and was actually used initially when I had visual composer on, but only for home page; then that got replaced by using the “shim” BETA, and then I moved to NewsMag for most sites … sadly I’m no longer really participating here, but I pop in from time to time after a theme update to see whassssup 🙂

I will link to this post in my old thread. 🙂

Security fixes for WordPress sites are fairly well documented online via changelogs for WordPress itself and sites like Securi which announce flaws in the base elements of WordPress, certain plugins, etc.

So, to stay on top of “what’s going on” it’s good to familiarize yourself with those and other resources.

Often if a security patch is listed as applied to a theme, it’s in response to one of those announced vulnerabilities, like a cross-site-scripting issue (XSS) or similar.

e.g.,
https://wordpress.org/news/2016/05/wordpress-4-5-2/

https://blog.sucuri.net/category/wordpress-security/

https://blog.sucuri.net/category/vulnerability-disclosure/

Generally the best way to ask about a specific detail not outlined explicitly in the changelog is to send a private email to tagdiv support and ask what was impacted. Often, looking at “which files changed” is a pretty good hint, in relation to things like the recent BBpress exploit announced this month or similar.

Disclosing a flaw in a theme publicly should never be done here.

Tip for switching site to https

a) add the explicit https URL to your wp-config.php file (see the wordpress.org codex/docs on how to edit/customize your wp-config.php file)

b) you will need to do database search/replace for old/existing images with http://sitename/uploads/image to https:// — if they are “placed” in the doc.

Good luck, it’s a process 🙂

Do you have gzip/deflate and TTL setup in your htacess file supporting woff font format?

See how to update from the theme docs, link is right side of page —->

"siteapps.com" is kind of a giveaway in the code.
Some plugin you’re using is calling content from that “app site”