Well, you need to take the child theme from v8, then apply any customizations you did with v6 to the v8 child theme. So, let’s say you put a custom footer in your v6 child theme, you’d move that over to the v8 child theme.

So, you might use file comparison software and compare the v6 theme with the v6 child to see what you changed; then move over any edits to the v8 child theme. Only reason to use child theme is if you made changes to the files (I personally just hack the main files, and keep track of that; stuff like removing the pingback in header, or removing comment count from the author block page element for author index, etc.).

Basically if you use v6 child theme to “over ride” the v8 theme, then of course stuff will be broken as the CSS, various functions, etc. are different. So, it’s like over-riding one theme with totally different theme — won’t work.

Main issue is you can’t use old child theme (v6) with new theme (v8) as too much has changed. Ideally you’d migrate child theme from v6 to v8, then test that with the current theme version.

Almost everything from WordPress had security issues back then, as many XSS security issues were found that impacted themes, plugins, WordPress core — basically any verison of WordPress prior to 2018 isn’t secure either, so folks not updating their core WP would also be subject to possible injections/etc.

I don’t work here, just some feedback. We went through that in going from newsmag 1.6/7 to NM3. Now looking to move to v4 (and hoping v5 doesn’t come out while we’re doing that!) 🙂

Yes, you need to set the secure port, properly depending on server (your hosting provider is often good source of help on how to actually connect to the server, by the way) …

On my server I have to, on
GENERAL tab
host IP, port blank
protocol ‘SFTP – SSH File Transfer Protocol’
Logon type ‘Normal’
User NNNNN
Password XXXXX

ADVANCED tab, server type “Default”

I set the root path to my public root
Default Remote Directory
/var/www/vhosts/MYSITE.com/httpdocs

TRANSFER SETTINGS
[x] default

On main menu, under server – I check ‘force show hidden files’ so you can see
.htaccess

Not sure that helps … but I have modern server setup with TLS1.2/SSH/SSL/ HTTP/2 and only secure connections allowed on all ports.

You may find this useful:
https://forum.tagdiv.com/topic/tutorial-good-basic-security-practices/

I still find FTP the best way to install, to be safe, as you can also take backup of existing content and wp-config, htaccess and all that at same time.

The shortcodes are different — not same plugin. So, if you have the TagDiv builder in place of WPBakery VC, you’d need to redo your page using new plugin …. or just keep using old plugin.

Technical glitch with Envato, they are working on it. Please stand by!

Themeforest has glitch. Updated version pending, appatently.

Bug on themeforest … 8.8.1 should be live soon.

Two different things… normally you would use either or page builder app not both…

Depends on the style element. If you have old inline styles like a center style on paragraph tag, you will need to search and replace that and replace with css class using phpmyadmin on your mysql dbase.

If its a theme style, try to find out where that is to let the theme devs know.

You should test any of your pists reported as having errors with goigkes amp tester to see what the errors are to fix.

You do NOT need to add nofollow to any internal site links, only external site links.

There was an old worry about too many same site links, but that doesn’t apply to news portals where elements like the ‘date’ are identified with microdata as the date, and not a spammy attempt to be a search result for the “date” (which would not work anyway).

Similarly links to internal articles from indexes and blocks don’t need nofollow links as you “do” want them to be followed to the canonical version of that content.

I use breadcrumbs navxt plugin on our site for breadcrumbs everywhere

🙂 been there !

Check your page source for the open graph image — whatever image is in your meta data is typically the one which will be ‘shared’ — unless it is too small, wrong format, can’t be loaded directly due to permissions, or if another image was already cached for your home page.

If a random image being pulled, likely means the image is not actually in your meta data, so best to check that first. If it’s there, it’s entirely up to the social site to pull that image — and usually will unless one of the reasons I mention.

I don’t work here, just some feedback.

Main ways to optimize your site for ‘speed’ include optimizing images, proper caching, fast server with multiple access points, limit number of thumbs loaded per page in modules, limit number of external sources, consider next gen tech like PHP 7.2 with opcache, mod_pagespeed and HTTP/2 support. Obviously anything you can do on your end like not using external fonts (use web safe browser fonts), avoid “query to external source” stuff like how many social shares, weather, jetpack, etc. — all impact “speed.”

Speed has been a factor for quite some time now, it’s not entirely new.

Have you checked your posts using Lighthouse and checked what you can do now to address issues with your site? Good place to start.

Hi
welcome to webdev.

If you mean these:

code.jquery.com (http://code.jquery.com/ui/1.11.4/themes/smoothness...)

pagead2.googlesyndication.com (http://pagead2.googlesyndication.com/pagead/js/ads...)

adservice.google.fr (https://adservice.google.fr/adsid/integrator.js?do...)

adservice.google.com (https://adservice.google.com/adsid/integrator.js?d...)
s.w.org (https://s.w.org/images/core/emoji/2.4/svg/1f641.sv...)

All Google ads have to load off Google’s server (obviously). To fix, turn off your ads, then test.

The emoji will load off the WordPress server if you are using emojis. You can disable that with a function. There is also a weird bug I’ve run into when pasting MS Word docs into the post editor, with some entities like (TM) getting converted to an emoji that ends up loading off the WordPress CDN — but nothing to do with the theme.

I also don’t think that version of jquery is loading from the theme but maybe a plugin of some kind, as normally any element like that would load locally from the site in the theme /js/ folder or whatever.

Generally you should test GDPR with plugins *off* (other than page editor), as the theme cannot control the GDPR policy of any third party plugin that works with another site (e.g,. Jetpack is not part of theme, as one example).

I don’t work here, just a webdev dinosaur since 1994/5.

TIP: turn off all the plugins that didn’t come with the theme, and anything not part of theme; then retest.

• This reply was modified 8 years by simchris.

What external requests, specifically?

Best bet is to simply do it old school way and simply put the various favicon formats in your root folder. Browsers look for them automatically and have done for many a year.

Generally best to update via FTP as you can make backup of site at same time (which you should *always* do prior to any upgrade!!). The Envato plugin sometimes fails to update everything properly, in my own experience. This can cause stuff to break.

Sorry that doesn’t help. But FTP always best way to install stuff with WordPress like theme upgrades, as you need to also update any plugins as well.

link works for me

https://forum.tagdiv.com/how-to-install-revolution-slider-v5/

https://forum.tagdiv.com/import-revolution-sliders-on-demos/

Depends on hosting plan with GoDaddy as they roll that out…

with dedicated or VPN, see:
https://www.godaddy.com/help/install-a-lets-encrypt-ssl-apache-20245

Shared/managed hosting:
If your hosting setup on GoDaddy uses cPanel with GoDaddy, you can install the Let’s Encrypt SSL cert for free, however as of last look it needed to be manually updated every 3 months as the auto-update option was not yet enabled with the cPanel plugin.

Or switch to one of the many top hosting providers who *do* support it 🙂

Obviously GoDaddy makes a lot of money off selling validated SSL certs annually, so they are not going to kill that business — but they need to support LE as it’s being pushed by a lot of big players like Google, etc. who are basically forcing everybody to do SSL/HTTPS/TLS or get a warning sticker.

Of course; none of that is related to updating site content for ANY https/TLS environment.

Cheers. I’m no longer on this board as of Feb. 17, so take care all! 🙂

All good web hosting providers now offer Let’s Encrypt SSL certs for free, so ‘free’ certs is not a main element for choosing a solution for https.

However, you still need to search/replace content in your post meta which has http such as placed images to be https. And any theme panel elements like social links for RSS feed, logo links,favicon link, etc. need to be updated.

We’ve done about 50 conversions from http to https since 2014 with WordPress. The way I outline above is recommended, but simply dumping stuff onto a CDN won’t fix all that either.

Lots of choices, obviously. 🙂

Also note you will need to fix existing errors in site content such as using the old ‘center’ option for elements, or any other inline html needs to be removed (e.g., need to use style class vs style=”table:width” .. or things like that inside of posts).

You need to
a) update all settings in theme to show https vs http
b) update WP admin panel settings for https
c) do search/replace in your mysql dbase for all placed files and links in posts from http to https
d) useful to explicitly include https URL to website and theme/plugin folders in wp-config.php
e)resave permalinks again in theme panel before / after any changes
f) setup redirect for all content from http to https version; but this can also now be done with most hosting panels (Plesk/ONYX, CPANEL, etc.)

No ‘plugin’ can do all that for you, unfortunately.