Web Design Blog

I recently switched a client's site from HTTP to HTTPS (SSL encryption) and needed to come up with a solution to their "social sharing counts" resetting to zero.  This is not a flaw or bug, it's working as it was intended.  

Here is how it works.  When you share a page via social media, it uses its URL:
http://www.yoursite.com/the-page-you-are-sharing

When you switch to SSL / HTTPS, your URL changes, similar to if your domain name changes altogether:
https://www.yoursite.com/the-page-you-are-sharing

With the new URL, you lose all of your social sharing counts, a source of major pride (and potential profits).  

My wife and I have been avid iPhone users for a decade.  We recently switched over to Android and I wanted to write up this post to share my thoughts and findings.  

First, Why?

We recently learned about these new Huawei phones and did some research on our own.  We wound up purchasing matching Huawei Honor 8's.  First, the specs are great.  They stand up spec-per-dollar wise when compared to iPhone 6s, which was going to be the iPhone that we went with if we stayed in Apple's ecosystem.  The iPhone 7 doesn't have a headphone jack and that was a deal breaker for us.  The Honor 8's have a 'full' 1080-resolution screen squeezed into 5.2 inches.  This basically means that the screen is a little larger than our old phones, but the clarity is amazing.  Huawei has openly stated that they intend to compete with Apple and Samsung, head on.  I personally believe they will be successful.  

This article was originally posted on SearchEngineLand.com

Google often provides useful information to the SEO community, but columnist Nate Dame argues that ultimately, the company's advice is in their best interest, not yours -- so make sure you understand the nuances.

Last month, Google released a video detailing best practices for hiring an SEO company, and it is positioned to become the go-to guide for hiring an SEO. After all, who better to tell companies what they should look for in an SEO than the operators of the world’s most popular search engine?

Starting in January 2017, any website with a "login" form visible (e.g. Client Logins, Shopping Carts, etc) will show an "insecure" message in the browser's address bar if the site does not have an SSL certificate properly installed and configured.

Particularly for my clients that are security-minded, it's important to consider how to proceed with this information.  Some of my clients already have SSL certificates running on their sites, even ones that don't process credit cards.  For clients who already process credit cards, their sites already have the necessary SSL encryption certificate (https), so this is a non-issue. 

I had been researching this issue for a client and wanted to share it with everyone.  My client and I had been discussing the ability to collect recurring payments via PayPal WITHOUT requiring the user to have an actual PayPal account. 

I recently received an email that is referenced in this forum thread.  I was going to post my response on this other site but it tried to get me to sign up for a premium plan in order to post a response.  Instead, I am posting it here:

Solution after finding myself unable to print multiple lines on my Quickbooks Invoices.  Seems like there are a lot of other people who posted similar problems and Intuit was fairly unresponsive.  Hopefully this video will help shed some light on the issue.  I almost wound up typing an amount and hourly rate for EVERY line on my invoices, even though only 1 line per invoice was actually required.  Yikes! 

I noticed that after installing the Joomla 3.6.4 security patch, the background color of the /administrator control panel login screen changed.  It seems that with today's release of Joomla 3.6.4, and ease of which the exploit can be executed, it's really bad timing to make it so easy for hackers to see whether or not a site has been patched.  This latest Joomla exploit allows for a person to do two things:

I just encountered an issue after upgrading a client's site to Joomla 3.6.4.  I was presented with the following error message on both the front end and back end of the site:

Error displaying the error page: Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=' SQL=SELECT id, home, template, s.params FROM #__template_styles as s LEFT JOIN #__extensions as e ON e.element=s.template AND e.type='template' AND e.client_id=s.client_id WHERE s.client_id = 0 AND e.enabled = 1: Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=' SQL=SELECT id, home, template, s.params FROM #__template_styles as s LEFT JOIN #__extensions as e ON e.element=s.template AND e.type='template' AND e.client_id=s.client_id WHERE s.client_id = 0 AND e.enabled = 1

I received another "Is this legit?" questions from a client today, and wanted to share so that others can also avoid this.

These people are combining “SEO” with “Registration” in their tactics, which is total shenanigans… it’s like a mechanic telling you that your car needs a new muffler bearing.  There is no such thing.