jasonbear

I agree with Anthony Hortin.

Without knowing in advance the exact text that your plugin has identified to be replaced across my entire site, there is no way on God’s green Earth I’m paying for the pro version.

Kevin, instead of HIDING the exact text that’s going to be replaced (which—in my opinion—is a horrible business decision that limits your conversions to Pro), you should simply put a % cap on the number of replacements that will be performed with the free version. In other words, show people all matches that can be replaced, but let them know that only a random selection of 25% (for example) of the matches will be replaced using the free version. And once the user replaces a certain keyword/phrase, that exact keyword/phrase can’t be replaced again without upgrading to Pro.

I agree with dylandawg.

Without knowing in advance the exact text that your plugin has identified to be replaced across my entire site, there is no way on God’s green Earth I’m paying for the pro version.

Kevin, instead of HIDING the exact text that’s going to be replaced (which—in my opinion—is a horrible business decision that limits your conversions to Pro), you should simply put a % cap on the number of replacements that will be performed with the free version. In other words, show people all matches that can be replaced, but let them know that only a random selection of 25% (for example) of the matches will be replaced using the free version. And once the user replaces a certain keyword/phrase, that exact keyword/phrase can’t be replaced again without upgrading to Pro.

I agree with tijsgerritsen.

Without knowing in advance the exact text that your plugin has identified to be replaced across my entire site, there is no way on God’s green Earth I’m paying for the pro version.

Kevin, instead of HIDING the exact text that’s going to be replaced (which—in my opinion—is a horrible business decision that limits your conversions to Pro), you should simply put a % cap on the number of replacements that will be performed with the free version. In other words, show people all matches that will be replaced, but let them know that only a random selection of 25% (for example) of the matches will be replaced using the free version. And once the user replaces a certain keyword/phrase, that exact keyword/phrase can’t be replaced again without upgrading to Pro.

Dev is lying through his teeth. Horrible support.

It absolutely does NOT support PHP 7.4.33.

The author does not care about you or any other user. They will respond ONLY if they deem it important or it’s in their best interests.

Divi

Thanks.

By the way, I’m using the latest version of Chrome for Mac (desktop).

Here’s a full-page screenshot. I’d prefer not to post the URL.

https://freeimage.host/i/HV7So4R

I already marked it “Resolved.” Thanks.

–

Weird. I just received an email notification about your latest response. I then did a normal page refresh, and the 1.2.0.6 entry appears. Maybe there was a geographical propagation issue. Thanks again!

Thanks for the help. I just tried clearing the Chrome cache, clearing cookies, restarting, refreshing, force-refreshing, restarting again, etc. The last log entry that I see is still 1.2.0.5.

The “View version 1.2.0.4 details” link is broken. I never update anything before reviewing the changes/changelog.

OK, I’ll relay that information to Divi.

Thank you very much for your help, Frank! I hope that this thread will help others, too.