Errors are the worst thing that can happen to your shop. Sometimes they are hard to figure out and you never know what really is going wrong. They are especially hard when your customer’s just see a white screen, they have no clue what it means generally. That is why we introduced a new type of error reporting in thirty bees. Instead of the normal white screen when a 500 error happens, we display an encoded error message that you can decode in the back office.
Displaying the error messages this way alert your customers that something went wrong, they are not sitting on a white page not knowing. This is the same technique that Google and other major sites use to display errors on their sites. If a user gets a 500 error they will see the image below.
The can click on the error code and send you the code that was generated. This is the most secure way of presenting the error message. Since the error is encrypted there is no information being given to the customer that would potentially put your server at risk. The error message is encoded using the cookie key for your shop.
Decoding the error messages
Once you get a report of an error message, you will want to decode the message. Decoding the messages is pretty simple and can be handled in your back office. In your back office you will want to go to the Advance Parameters then Logs item in the menu. At the bottom of the page you will be able to decode the error message.
From here you can paste in the error code to decrypt it. Once you paste the code and press the decrypt button, you will see something like below.
Now you can start figuring out what the error message means. If you are not a developer or have trouble with the meaning of the message, you can post it to our forums and get help.
If you have any suggestions of how the error message should evolve over time let us know, we are always wanting to make things better and more friendly for our users.