Hello Sin-able Sweets Customers! It is soon going to be Summer, so we figure it was time to send out some updated information on Sin-able Sweets. Let’s dive on into the waters…
So, at the beginning of May, we switched the hosting provider for Sin-able Sweets. While the technician on the back end had no issues getting the website moved over, I had nothing but issues with a few things that had nothing to do with the switch. At home, we also changed our Internet Service Provider (ISP) from Comcast Business to Xfinity (AKA Comcast Consumer). While there were no issues for me to get to our website when we were on Comcast Business, when we moved to Xfinity, they have some kind of block on some websites, especially websites dealing with website hosting! In fact, with Xfinity at home, we cannot get to Sin-ablesweets.com, we have to use our phones and our mobile phone internet to get to it! We figured it out when we used a program to sign into computers remotely (yea, we are THAT tech savvy!), and while using DirectLink from the bakery, there were no issues. We have a work around at home for getting to the back end and so that issue has been resolved. If you are on Xfinity (Comcast Consumer/Home) and you are unable to access Sin-ablesweets.com, please send an email to email@example.com letting me know so I can contact Comcast and see what the issues are.
Also, with the website hosting change, you might not be able to get to Sin-ablesweets.com either, and you are getting error messages looking something like this:
I know seeing something like this is concerning, and the first time I saw it myself, I was upset. I knew what to do to clear it up, and I will let you know also.
First, the reason this happened is because, we switched website hosts. I am not sure if you have noticed, but on a web browser address bar, when you go to a website, it should look like this:
There are 2 parts, that are interconnected, are part of why are might be getting the “connection not private” message.
Websites now can easily get a security certificate to prove you are getting to the right website, and these 2 items tell you that it is secure. If there is not a closed lock and https (this does not always show unless you click into the address bar). Because that security certificate lives not only on the website, it also put what is called a cookie (for a bakery, that is a good thing, right!) that when you go there, they confirm they know each other, and you are good to go. If there are things that are not matching, you get that error message above. You can do one of two things to clear this error up. If you click on visit this website, it will give you another screen asking if you are sure you want to do it, click yes, and you go to the website. Then you will see the lock and https on the address bar, and you know you are ok. Now that you have been to the website, the cookie gets updated and there should be no more issues. The reason this happened is because something does not match, so it gives you the warning.
The other way to fix this is to, and I am SURE everyone has heard this phrase before, “clear the cache”. What is “the cache”? This is from the website Kinsta:
So, clearing the cache will take all that information out of your browser, and then when you go to website, it will start downloading resources from websites again, until you clear the cache again.
Clearing the cache is not difficult, but if you are unsure of what you are doing, it can be scary the first time. If you have a “geek” in your life (May 25th was Geek Pride Day – did you thank your geek?), they can help you through the process. If you want to try it on your own, the same website from above, Kinsta, has instructions on how to clear the cache on a majority of browsers. Since most of us use only Windows and MacOS (Apple) computers, and Android or iPhones, the biggest difference is the browser. There is even a video that shows about how to do it. If you do not have one of the browsers mentioned in the article, do a google search for “clearing cache” and the browser you are using.
Next subject, “sugar free” vs “no sugar added”. How many of you have come into the bakery and said “sugar free” and someone working at the bakery said “no sugar added”? Many people wonder why we do that I am sure. The basic reason is we want to make sure people are aware of what they are eating and how words can make a HUGE difference.
If you think of sugar free, what do you think of? Many people first think of diet sodas (have you noticed they are now being called “Zero Sugar” instead of diet?), but as you walk through a grocery store, you will see items saying they are sugar free or no sugar added, but have you looked at the label and seen what items are listed on the ingredients? An easy and simple example is milk. Did you know milk has sugar in it? Technically, that ingredient many people have difficulty processing, lactose, is a sugar! In fact, if an ingredient end with -ose, you are most likely looking at a sugar. Table sugar scientific name is sucrose, brown sugar contains sucrose, and you know we use a small amount of that in our cookies,, and your blood has a natural sugar in it, glucose. That is why we want to make sure our customers understand that if we say an item is “no sugar added”, we have not put any sucrose/table sugar in that item. There are items that have milk products, and even fruit sugars, fructose, would be considered an added sugar!
We will soon be in June, and the heat of Summer will soon be upon us. We want to make sure everyone is aware of our procedures for when temperatures are going to be above 80 degrees Fahrenheit. While we have ductless mini-splits in the bakery, the building is old, not always insulated to newer standards, and there are many air leaks though out. So, while we can cool it down somewhat, if we are having to bake during the heat of the day, it makes the entire bakery extremely warm, and even possibly unsafe for people to work in. So, if temperatures are forecasted to be over 80 degrees, we will ask for you to get your cookie orders in before 10AM (if the phone goes to voicemail, please leave your order and a contact phone number or send an email to firstname.lastname@example.org with your order and phone number). If the National Weather Service issues a Heat Advisory, we would ask not only to get the cookie orders in as soon as possible (even a day or two early), but also pay attention to our website and social media. We may close early and do not want someone to miss out on their order.
If the National Weather Service issues a Heat Warning, and it looks like temperatures are going to be over 95 degrees during the day and not get below 70 degrees at night, we might not open as a safety precaution for our employees and our customers. Again, please watch our website and social media because as soon as a decision has been made, we will post it everyplace we can think of.
The last items we will be bringing up in this update is Oktoberfest. Yes, I know, it is 3+ months away, but it is something that we start planning for early, and we want to make everyone is ready for it.
Oktoberfest this year is September 15th – 18th. We will not be doing CDPs the week after Oktoberfest. Also, please check on the website, social media or our monthly email of the dates of the CDPs as we have adjusted dates we are going to each month. Also, Summertime is also when road construction is in full bloom, and there will be MAJOR road construction in Molalla on Highway 213 and Toliver Road, where they are going to be constructing a round-a-bout. ODOT is going to shut down 213 in that area after the Molalla Buckaroo Rodeo, which happens early July, and it will last through September. The detours will be the same as when they closed 213 to replace the culvert and widen the road in front of Tractor Supply. When we get closer to the date, I will send out an email with the detours for you.
So, that is the updates for now. Again, if you are on Comcast and unable to get to our website, please let me know at email@example.com.
The Sin-able Sweets Team