Search Results for 'ssl'

That is just a simple hit counter and only counts main times the page was ‘loaded.’

You should always use something like the stats included with your hosting panel to see “actual traffic” to your site.

And as I stated, Google is changing how they show sites in search results.

So, good time to
a) check your pagespeed score with Google PageSpeed Insights
b) make sure your content is mobile friendly
c) consider using https vs http; your host should be able to give you free open source SSL/https cert
d) check your Google Search Console for messages about any issues/problems with your site
e) if using AMP, note the page counter does not count AMP views of pages

Not sure that helps; but all our sites traffic went down since the election in U.S., regardless of theme.

Theme doesn’t control inbound traffic to your website.

Thank you very much Catalin! The solutions to #1 and #4 work flawlessly.
For #2: I am referring to the padding on the left and right side, not the top and bottom. No matter what options I use in Visual Composer it won’t stretch all the way.
For #3: The search icon is now hidden from my header. However I need to move the categories to the right to align with the rest of the content, instead of an empty space where the search icon was.

Update to help others:

I tried everything. Reinstalling, switching themes, deleting folders manually, uploading manually. Switching from SSL to non-SSL. Eventually, this worked.

Added this to wp-config:
define(‘FS_METHOD’,’direct’);

AND, disabled Rocketloader on Cloudflare.

Hi,

Actually, after Googling for a few min, we found this in the 7th search result:

This is the needed code:

<form method="get" id="search form" action="/">
<div>
<input type="text" value="" name="s" id="s" />
<input type="hidden" value="22" name="cat" id="scat" />
<input type="submit" id="search_submit" name="Search" value="Search"/>
</div>
</form>

And it works flawlessly:

Even applying the theme’s style:

cheers

Hi Chris

I give the [TUTORIAL] some thought.

Actually I think you might know about the Speed Boaster plugin. Am I right is thinking with some of the modern browsers it is redundant? I seem to remember it’s when the site is running SSL. I think I saw you said you did not use it anymore?

The reason for mentioning it is that 3 of the compatibility errors where in that plugin!

Like you we can just switch php version on will. It may be on my test of Newsmag theme (can’t remember for sure) I found it was only really fully compatible up to 5.4 (caused by one error).

It is possible to write php so it will work with versions of php 5 AND php 7! They are not mutually exclusive.

ALSO note that many hosting panels can do basic http > https redirect at the hosting panel after the SSL/https cert is setup.

In practice however, what I have found on CentOS/Plesk/Apache with “Let’s Encrypt” that Chrome still continues to allow, and the server, continues to allow loading via http, and so it throws up errors in Chrome for mixed content.

As always, after doing all these shenanigans, test your site in a web browser to ensure you do have ‘lock’ on all pages/posts; keeping in mind the errant AdSense ad might throw an error you can’t do anything about unless you opt for text-only ads.

I updated the older SSL/https thread also with code examples ! 🙂

See
https://forum.tagdiv.com/topic/moving-to-ssl/#post-140870

As an update to this older thread; most hosting providers worth their salt are now moving to support “https everywhere” initiative with free SSL certs for https via “Let’s Encrypt,” even on shared IPs. Note using this type of cert will mean OOOOOLD web broswers might not be able to access website at all since they can’t support modern secure standards — and, really, should NOT even be used on the web. SO, some kind of ‘sniffer’ to say “hey, dummy, update your browser to Chrome…” is worthwhile.

you should also add a block like so in your htaccess file above the #wordpress stuff…

e.g., (note; this example is using pretty permalinks with post name; so don’t use my wordpress code unless you want to; this is just example of how to put in the EXTRA stuff ABOVE the #wordpress stuff!)

**this presumes APACHE server.

<IfModule mod_rewrite.c>
RewriteEngine On
    RewriteCond %{SERVER_PORT} !^443$
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
</IfModule>

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

ALSO: in your wp-config.php file, this is useful:

define('WP_HOME', 'https://SITEHERE.com');
define('WP_SITEURL', 'https://SITEHERE.com');
define('WP_CONTENT_URL', 'https://SITEHERE.com/wp-content' );
define('WP_PLUGIN_URL', 'https://SITEHERE.com/wp-content/plugins' );
define('FORCE_SSL_ADMIN', true);

Finally, in some setups you might find this more useful to put at top of htaccess than my first example — basically a slightly different way of doing it:

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,QSA]
</IfModule>

*updated : Oct. 27, 2016 / 12:19pm PDT.

• This reply was modified 9 years by simchris.

Note you do need to setup global redirect to https for your site in htaccess file; also useful to add explicit link to site home/URL as https in your wp-config.php file including force SSL line (See WP ‘codex’ on editing wp-config.php for more info.)

You may also need to do a search/replace in your dbase via mysql/phpmyadmin in your hosting account to make sure all links previously noted as http are setup as https.

Also remember you need to change logo links, any anything like link to RSS feed, in the theme panel to https vs http manually.

After doing all that, be sure to resave permalinks, force reset sitemap XML by turning that off/on in your plugin for that, and if using any secure form, make sure you go to that “page” in your web browser, and do F12 in chrome to see if any http vs https mis-match which cause (!) in browser vs [lock].

I’ve actually just been doing this for our news sites with Newsmag theme.

AND: remember you need to submit https version of site in your Google search console as new site, reconfirm, then resubmit site maps for https version to Google.

And, if using “Let’s Encrypt” SSL cert vs paid version; I found it’s useful to check the box to allow both www and non www access, for some odd reason.

Hope that might help in some small way.

Update, this caused too many issues for my users and I had to disable SSL across my entire website. As soon as I did that the login on mobile started working flawlessly again. What could be the possible fix?

Thanks

Here is the screencast

http://www.screencast.com/t/PTium2cDYVFc

Also, do you think then wordpress has any limitations? Because at a lot of places we read that wordpress can support only upto 500 pages seamlessly

Hi

You have a resource called from http and if your site runs over https the browser may block it. Basically if you’re using ssl all resources must be loaded trough https. It also could be an issue generated by server side cache so you can try to contact your host provider and ask for more details in this regard and also if can be turned off.

Thanks!

Thanks for your work on this, but the JavaScript still doesn’t render, although the boilerplate does. The script works on the staging site, but not on the live site.

Could it have something to do with Flywheel’s server-side cache? Or the Let’s Encrypt SSL? Baffled.

• This reply was modified 9 years by Fasmon.