After a period of internal testing, the blog officially launched full-site https.
It has been almost a year since I established the website, and I have always wanted to build an https, but the original host does not support SSL certificates, so there is no way.
The host was about to expire recently, so I changed to a supported server.
People have always told me before that the blog can no longer be accessed from time to time. I wonder how it will fare in terms of speed and stability after upgrading to a better server this time.
Then I upgraded my emlog version. Although it is only a beta version of 6.0.0, the background management interface is much better than the previous 5.X version. It still uses the Bootstrap UI library.
(Note: The picture below shows the background management interface of the emlog 6.0.0 beta version. The third-party template setting interface is missing. The template management in the upper right corner of the picture below was added by myself)
2. The whispers disappeared
When emlog first added Weiyu, I felt that it was unnecessary and rough, but after everyone became familiar with it, I removed it, which was a bit a bit awkward. . .
In fact, this can also be written using a third-party plug-in, and it can be used by those who need it. . . Anyway, I didn’t whisper much (lazy), so I discarded it.
Of course, it is still very troublesome to implement https for the entire site. Why should I upgrade emlog? The reason is here. Only versions after 6.0.0 fully support https. If you use the previous version, it will have to be changed to death. . .
In addition to emlog, the large front-end template I currently use does not support https.
In fact, the main reason why the big front-end does not support https is Baidu’s sharing function. Baidu sharing is used on the article page, resulting in the mixed use of http and https, and the cute little green lock is gone.
“Baidu Share has not been updated for two or three years, and the information update on its official website is still in 2012. It has not been updated for such a long time that many Baidu products are now HTTPS-based and Baidu Share still does not support it, which is very troublesome for developers. If the website has enabled full-site HTTPS, there will be loading problems after using Baidu Share, and the core JavaScript of Baidu Share will be blocked.”
After searching on the Internet, I found that someone has already solved this problem, so we can just do it directly.
Github address: https://github.com/hrwhisper/baiduShare
- The mobile version page of the default template has been removed (it is ugly anyway). Anyway, the current template is adaptive and is not needed.