Sorry… I dont work here. Tagdiv support will be back monday to provide less humorous and more detailed support. Although you can easily find the answer yourself.

Well, that’s the most inane lazy answer to somebody trying to show you how to fish vs waiting for a fisherman to troll by and throw you free fish.

Why not go look, explore, and you will find.

I answered your question — I can send you a bill for more professional consulting to teach you how to use the internet, your PC, file folders, WordPress, themes, etc., but sadly you can’t afford me.

Have a marvelous day! And, you’re welcome 🙂

At least now you know where to look — but I bet you didn’t even bother to look.

I’m not obligated to answer in any specific format — my advice is free, take it or leave it. Cheers.

Why not go look?
Open the theme folder and notice the folder called “images” ?

Note the folder called “no thumb” – might be good place to start 😉

Never hurts to go exploring in your theme folder by opening it on your local hard drive. Good to know what’s there, where things are, etc.

e.g., /Newspaper/images/no-thumb/td_0x420.png

https://codex.buddypress.org/getting-started/customizing/

Did you delete the old /plugins/js-composer/ plugin folder before uploading the new one?

Best to unzip on your hard drive then FTP to the plugins folder manually; that’s what I do to ensure it always works.

Normally i see that error for clients if gd library not activated on server, but might nit be your issue.

Well, when i went to page video didnt show, and browser said do i want to load insecure content, i said yes, then video loaded. I did not look at your source code though, it might be the iframe wrapper loading video via http..vs https, but again i didnt look at your page source, and im presuming you already checked console for errors.

Double check source code do search for anything with http on page.

Because the video link you’re placing on the page is not https — so the browser blocks any non-https content when loading an https page — this is purpose of https; if everything on page not secure, then it defeats the purpose.

Make sure you use https URLs for your videos.

It doesn’t say it’s malware, it says “this file is not commonly downloaded” … which merely means Google’s caching system for Chrome hasn’t had a lot of hits to that specific file. You can simply click the arrow and select “keep” … or more info.

The language used here DOES imply “oh no, danger Will Robinson …!”
https://support.google.com/chrome/answer/6261569?p=ib_download_blocked&hl=en&rd=1

Apparently ThemeForest has had their share of bad eggs:

More info for software developers and website owners
To help protect users, Google maintains a list of websites that are known to host malicious downloads and a list of trusted software publishers. If you're a software publisher and your binaries are flagged by Chrome, learn how to resolve malware or unwanted software issues related to your downloads.

This is part of Chrome’s updated security which has a “threshold” for files loaded off the web and downloaded to hard drive, to stop malicious files being written to your HD when they are zero day files.

Several other files do same thing, like a u-design theme update, and woocommerce tabs plugin. Newspaper 6.5 does not 🙂

In case anybody was curious about that 🙂

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

Typically some type of java conflict; perhaps check in the console in IE or Chrome for quick checkup> Try disabling plugins except Visual Composer.

We use CSF/IPTables on Apache.

Been there … it’s a major learning experience ! 🙂

Right — as I noted you need to do a sitewide 301 redirect in your htaccess file — this tells Google the “NEW” location of an existing page has moved/changed

http://site/page >> new canonical = https://site/page

Google sees that *and* your sitemap you should be submitting from your webmaster tools account (!!), and “knows” what the new page is.

Again — you need to tell Google your site has changed from http to https in your webmaster tools account — see their HOW to.

You need to create new site in your account with https, submit your https sitemap, and then make sure the http site fully redirects to https — this tells Google to use the https version in your account vs the http version.

Yes, when you change name of theme — it’s like switching to new theme. A lot of settings need to be redone.

So, you would need to reset home page, sidebars, menus, widgets, etc. — just like if you switched to another theme; since that *is* what you’re doing.

The code I provide in my sticky optimization post has some code to use to try to hide the version?=123 stuff. Take a look at that if you want; it’s for the functions.php file.

I think v4 of theme is included in the current “all files” download, but not sure if it’s 4.2.2 or not.

Check the page for java errors if FB says no errors.

If the OG tag for image is set correctly, then they should grab the right one. You can look at your page source to verify the right image is set.

I often have issues with FB and have to use the ‘force refresh’ tool on each post at least couple times a day. Super annoying.

Not like we’re paying them to grab our stuff, so support is non-existant, sadly.

I know there was an issue with duplicate “image” tag in some versions of theme, so again check your page source for what is actually there to ensure no duplication, missing item, or bad file name, etc.

For example FB would have trouble with “my%20file%20name.jpg” —
they also have issues with png files it seems.

Ummmmm….
why would you deny access to your sitemap ?

Purpose of the sitemap is so search engines can read it to index your site. Unless you allow it, then it serves no purpose.

If all your pages are https as default, if properly set as site level and your wp-config.php then ALL pages will have proper canonical URL of https://pagename

The 301 redirect tells Google things have moved permanently so you won’t have 2 copies of the same pages being loaded or if they are, only the https is the “canonical” (official) version — that’s the point of that.

You should read the Google guide to moving to https if you have not already as it’s very step by step on what you need to do including updating your listing in webmaster tools (search console).

Generally yes. See the theme docs on how to do updates, as a good starting point.

Since it’s a bundled plugin and not a separate license, you cannot “update” it from the publisher of the plugin or via the WordPress repository as a commercial plugin.

I generally don’t use the Envato toolkit myself as it sometimes breaks things.

FTP is really important to learn to use for WP, as it’s often the only way to do proper backups, edit files, edit htaccess, set permissions, etc.

I use duplicator to make clone of my site on my live server, then download the backup file to my PC from the site. Works flawlessly even on 10 year old sites.

You can always do a repair/optimize on your dbase first, which you should be doing anyway with at least things like the wp-optimize plugin.

You can also try to repair dbase or optimize via phpmyadmin.

Make sure you have enough memory assigned to php to run the tool; make sure your timeout isn’t too short for Duplicator.

That may not help, but it’s been my own experience.

(not theme related, obviously … )

See the update instructions in the theme docs, right side of page.

ThemeForest themes are not part of the WordPress repository, so they generally need to be updated manually, typically via FTP is best way.

Also some great tutorials online for how to update WordPress themes.

(I do not work here …)

• This reply was modified 10 years by simchris.

Try the FB debugger tool.

You need

a) specify your explicit domain is https in your wp-config.php file
b) setup 301 redirect in your htaccess file to redirect all http requests to https
c) edit your WP dbase to replace all instances o internally added images embdeed into posts to change domain from http to https.

Hi
point (7) is for people who have “contact us” forms, which allow people to put in an email address, type in message and then hit submit; they can put anybody’s email in there — not theirs – and send spam from your contact form. So, “auto respond” bad idea there.

Obviously for “lost password” you need to have it send email to the person, but it should be smart enough to only send the email to the pre-existing account, right? So that negates somebody using that to send email to a third party.

Imagine the “chain of email” when a form is filled out … in the case of contact form, it’s problem; in case of somebody who lost their password – the email can only go to the person’s pre-existing email account.

For account “setup” that is different use case, such as “sign up for free account” — but even then, newsletters should be handled offsite (e.g., Mailchimp, etc. — not from YOUR site). and for ecommerce like WooCommerce turn off pre-order account setup, so account is auto-created on first order.

Be as paranoid as you can possibly be.

For all signup contact forms, be sure to consider the latest Google “I’m not a robot” captcha, and additionally use a plugin which interacts with known RBLs to stop anything being entered from bad domains and/or IPs.

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

You can see this from the changelog for the plugin from the download file from ThemeForest, simply look in the plugins folder, decompress the js-composer zip, then look at the changelog file included.

Or, if already installed you can see it from the plugins page in your WP install.