Search Results for 'ssl'

Did you switch on the setting in the theme settings for posts, which expressly allows the featured image to be used in the posts vs the original placed images?

There is setting there to control whether you end up with duplicate images or not.

see
https://forum.tagdiv.com/post-templates-and-settings/

@sgoadmin
Not right now … trying to migrate an old ecommerce system from old platform (cubecart) to new platform (woocommerce) so we can switch mod_SPDY back on for the server, trying to install custom local copy of “piwik” on subdomain with wildcard SSL, and generally overloaded at the moment …. 🙂

• This reply was modified 11 years by simchris.

Hi
yeah. The only reason to use a child theme is if you plan on hacking things and don’t want to re-hack them on theme updates, which I actually prefer to do.

If you look at the theme activation page, you would only be running the “child” theme if you expressly activated it. If you didn’t do that and are running the “parent” theme, then this has no impact on what you’re doing at all.

Meaning, the child theme doesn’t work automatically, only if you expressly activate it from the WP theme panel. If you’re not using it, you could delete it, but if you ARE using it, you would want to switch back to main (parent) theme before deleting it.

For info on what child themes are all about, the WP codex/docs
http://codex.wordpress.org/Child_Themes

We’re running PHP Version 5.4.22 on our server and have been using Newspaper the past year without any issues related to PHP. Also running one site with Newspaper with https with zero issues.

It sounds more like a system setup issue on the backend as far as resources, memory allocation, caching, or possible DNS issue; and not the PHP “version” itself being the issue with the theme/WordPress.

While not common in the past, if you’re using one of the tricky *new* setups with SSL and a shared IP, that can cause some intermittent things vs dedicated IP address.

Seems like you should have the overall system checked, as not being able to access your WordPress login is generally a sign something more notable is wrong.

“Force SSL” can cause loop issues.

Ideally you should set redirect option in your .htaccess file if running Apache

RewriteEngine On

RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

Google wants ALL pages on a website to load via https, not just home page, as post pages are what mobile users follow from social media shares/links, and more likely found in SERPS, etc.

For the near term, Google is expecting a “transition period” … so, you will be fine if
a) you have changed your default wordpress structure to https (e.g,. via wp-config.php)
b) *all* your canonical links now say https://yoursite.xyz
c) you have SSL cert or pages loaded from CDN with SSL, so lock engages in browser; Chrome will do better job of warning about insecure pieces than Internet Explorer
d) you update your sitemaps with Google
e) setup 301 redirect schema from http to https (as in my example, or similar)
f) you put in a “site change of address” with Google to TELL THEM that the site is officially now https://yoursite.xyz and no longer http://yoursite.xyz

Thanks Shashank. I have not gotten into the functions.php file, but have already changed the settings in WP Admin and I have changed the url for the logo.

Do you have any specific advice for SSL-ing Google Fonts?

Philip

Hello,

I am SSL-ing my entire site and am running into these four open issues so far:

Insecure URL: http://fonts.googleapis.com/css?family=Amarante
Found in: https://tribyoot.org/

I’m not sure how to ssl the fonts. You would think this would be handled by the functions.php file (protocol relative links).

Insecure URL: http://tribyoot.org/Tribyoot/wp-content/uploads/2014/07/logo-tribyoot-300×1004.png
Found in: https://tribyoot.org/

The above image is determined in the Theme Panel, and the actual link to the image is https://tribyoot.org/Tribyoot/wp-content/uploads/2014/07/logo-tribyoot-300×1004.png, but my “WhyNoPadlock” scan is insisting it’s and http file and not an https file.

Insecure URL: http://tribyoot.org/Tribyoot/wp-content/themes/Newspaper/images/header/elements-menu.png
Found in: https://tribyoot.org/

In the theme files, the elements-menu file seems to be a blank file, but obviously it’s used and output by the theme on my page. How can I SSL that image?

Insecure URL: http://fonts.gstatic.com/s/amarante/v4/7QYOnlvGMVlAzj6iP9gUMPesZW2xOQ-xsNqO47m55DA.ttf
Found in: http://fonts.googleapis.com/css?family=Amarante

I’m guessing this is essentially the same issue as the first one of these four?

I hope you can help me find a way to secure them.

Philip

Nothing to do with theme. It’s an issue with Facebook. You can use the FB debug tool to check your META data. The OG tags are there expressly for Facebook.

FB had an outage just a little while ago, btw.

Facebook has intermittent issues where some days they won’t grab image; some days they grab image, and an hour later you have an empty box, some days they don’t grab image right away, and then it pops in 10 minutes later. Nature of the beast. I deal with this on a dozen of our sites every day, and a royal pain.

Upshot – learn to work around it, or try again later when sharing. Post direct link vs using share button, or paste in the headline and URL, the nit might grab stuff. It’s really inconsistent long term.

But, check your meta data in your page source to make sure you have all the correct OG tags in place; then run the Facebook debug tool on your post page to see if anything major. If not, then it’s just their twisted universe spinning out of control.

In case I didn’t include this previously:

In your WordPress Settings, you specify the WordPress address and the site address. Those are added in your database, and every time the developer calls it in the template, it is running a database query.

define('WP_HOME', 'http://www.wpsitez123.com'); 
define('WP_SITEURL', 'http://www.wpsitez123.com'); 
define('TEMPLATEPATH', '/absolute/path/to/wp-content/themes/active-theme');
define('STYLESHEETPATH', '/absolute/path/to/wp-content/themes/active-theme');

By adding these in your wp-config.php, you are reducing the number of database queries thus increasing your site’s performance.

These settings are also useful if converting your website to “https” once you have SSL cert installed as WordPress can ‘soft-redirect’ any query for http://yourpage to https://yourpage; and it updates the WP Settings general page showing URL, and YOAST SEO picks this up for writing canonical links for https.

In case anybody is on to the more hard core optimization of WP.