It is nice when it worked

Hi Tony
Although I can appreciate you had a difficult time while using our plugin I really don’t appreciate being called a “chimp”.

With that being said, we experienced issues a few months back with users on SiteGround hosting plans (only certain plans). We found that somehow their backup process wipes our marker table. We’ve investigated this at great length and have, as a result of this, put in automated backups in our plugin to try avoid this issue in the future as we understand losing marker data is a critical issue.

Nick

Hristo from SiteGround. All our accounts are backed up by the same system. Clouds have just less restoration points due to the nature of the product itself. All databases are restored in full as well as the files selected. We do not wipe any content whatsoever. I would love if you can shed some light on that since I would love to have any potential bug fixed!

@hristo-sg Thanks for getting in touch!

For most SiteGround users it works fine, but when SiteGround moved away from cPanel a migration happened. During that process, some of our clients reported data losses. We looked into that and it has to do with our geometry fields not being supported.

We use spatial data here for improved search performance based on location. These are stored as Point() geometry fields.

Unfortunately, those fields (wp_wpgmza table -> latlng column) need to be encoded/decoded for SQL import/export functionality or need to be skipped -> Otherwise SQL import will fail.

The problem is that there’s no (identifiable) way for us to hook into SiteGround backups to handle the encoding.

The alternative is that we move away from using spatial data, which means our plugin will become a huge performance issue for all users with large data sets.

The cPanel to Site Tools migration is completely different process than the backup restoration. It is now over, all our servers are on Site Tools so we don’t expect such problems to happen again. I am aware of the collation issues, they were reported and addressed accordingly but since we migrate server to server issue like that can affect multiple clients.

Soo I would say that problem should not happen again really and was indeed cased by our migration ?? Feel free to reach out directly to me if there are any incompatibilites with our systems, I would do my best to have them resolved.

@hristo-sg thank you Hristo!