Leaderboard

Parameters behind # are for client use only. Request to the server never contains those parameters, server never sees them and can't react to them. When you open urls https://www.example.com/en/products/84/sample-product#/72-size-large or https://www.example.com/en/products/84/sample-product#/whatever your server receive the very same request - https://www.example.com/en/products/84/sample-product It does not know what combination you are requesting. Javascript will later parse the hash parameters, and will modify the product page to display the wanted combination if it's found. This also means that initial page render shows different combination, and only a few milliseconds later the page is 'adjusted' When you provide ?combination=xxx parameter, server knows upfront what you want to display, and can returns page with combination already selected (if your theme supports this, of course). The page already contains correct pricing information, product name, reference code etc -- this is important for web crawlers. This means that you need to provide urls with standard query parameters (after ?) to google

Put a pulse monitor result to keep server running ...

He did write that he's alone... and it can be a good solution for other circumstances, too.

I also think that's a good idea, even if it's not something you think about every day. The time until "standby mode" should be adjustable, because some people only need to log into the back office every 2-3 days, not daily... it really depends on the business. Do other shop systems have something similar? That would give thirtybees another small unique selling point.

Hi @papagino This is actually a pretty good idea and a realistic scenario. @Smile @datakick

Yes, I would start troubleshooting with your hosting first or the person that is maintaining your server. Because they have made some changes recently and we're here just guessing. In general if the thirty bees settings work - they work. Most of the issues are changes - of the merchants or hosting environments. It's not necesary an account/password issue - it might be some additional configuration of the mail server regarding transport/security.