We recently completed a server infrastructure upgrade to increase the performance of your website.
Wow, that was boring. Let’s try again.
Everyone wins when a website is faster! We just added some rocket fuel to the servers that host the websites for Websites For Printers. With this added rocket fuel, you’ll see that:
The rest of the details get geeky fast, so just carry on with your day with the assurance that we’re taking care of your web technology needs so that you don’t have to.
Breaking News from our tech department: “Houston, we have a problem.”
There was a hiccup during the server upgrade on April 12, 2016, that caused some database records to be lost. All missing records (new orders, proofs, etc. that were created on that day) have now been recovered, but there is one aspect that is not recoverable. Any changes made to existing items on April 12, 2016 (proofs marked as approved, orders marked as completed, Document Library Items changed from Public to Private, etc.) were not captured. If you made changes that day prior to the server upgrade, the changes did not get applied to the upgraded database; those changes are not recoverable.
We suspect this server hiccup affected a relatively small number of customers. Unfortunately, we have no way of knowing with 100% certainty exactly who was affected, so our best recommendation is to check email notifications you received on April 12, 2016, and note any changes that you were notified about. You can then check your workflow to make sure that the system currently reflects those changes. For instance, if you received an email notification that one of your customers approved a proof, we’d encourage you to double-check that proof record in your website to make sure the change “stuck.”
We are aware that orders and proofs are often as crucial to your business as a successful shuttle launch is to space exploration. Please let us know if you wish to have some help analyzing this issue, or if you have any concerns about specific orders and how your data may have been affected. In some cases, we may be able to pull old data as a reference point if we have a specific order number.
We wish this hiccup would have never happened…but it did. Please accept our sincerest apologies for any issues this may have caused.