Verified Purchaser badge

Verified purchaser

Member since: Oct 2016Deals bought: 192
1 stars
1 stars
Posted: Oct 17, 2024

Nothing short of disastrous

I tested BerqWP on a very basic website, and the experience was nothing short of disastrous. The site completely crashed, with numerous errors appearing on both the frontend and backend. I found myself unable to restore the site using my usual backup solution, as BerqWP compromised that too. The only way I managed to bring my website back online was by deleting all files via FTP and wiping the MySQL database entirely before re-uploading my local backup.

Unfortunately, the support from BerqWP has been the worst I’ve ever encountered with a WordPress plugin developer. Despite requesting access to assist further, I received no response from them after eight days, despite multiple follow-ups on my part.

Why is there no reply to support case #7365? You specifically asked AppSumo users not to voice complaints publicly, even labeling them as "not genuine customers" here: https://appsumo.com/products/berqwp/questions/so-many-problems-by-other-users-1189926/.

I have fulfilled all your requests, reached out to support, followed up multiple times, and patiently waited for eight days. So, I must ask again: why is support case #7365 being neglected?

Founder Team
Hamza_Mairaj

Hamza_Mairaj

Oct 17, 2024

Hey there,

We’re truly sorry for the inconvenience. We're currently dealing with an overwhelming number of support requests, which is slowing our response time. With our small team, managing new plugin updates and support tickets can sometimes be a challenge. Please know that your ticket hasn’t been ignored, we’ve now added our response and would love to onboard you with BerqWP.

Regarding the "Constant WP_CACHE already defined" error you mentioned in the ticket conversation, this occurs when debugging mode is enabled on a website, which is disabled by default. You can resolve this by editing the wp-config.php file and changing the WP_DEBUG constant value to false. After saving the file, the error should disappear. Actually there was no need to restore whole website. It was a quick fix.

Helpful?
Share
Ratings