Sven71

Hm, I don’t remember Code Snippet to work otherwise ever and I’ve used it for years now. Anyhow, if the problem is solved whatever way then I guess this thread can be closed.

As a starter:

$subtext = get_field( ‘subtext’ );
if ( $subtext ) {
$response = ‘<p>’ . esc_html( $subtext ) . ‘<p>’;
echo $response; // output the HTML
}

Nothing more. No PHP open / close tags in code snippet editor to be added by you.

My wild guess: it broke because of the PHP tags. You are not working in a HTML editor here that would demand the tags. You do work in a PHP editor and especially the closing PHP tag cuts off further PHP code outside your snippet which easily breaks sites.
Please take a first attempt at omitting PHP tags and report back the result.

• This reply was modified 2 years ago by Sven71.

Thank you for your response here, Rene.

“The only reason why we added the term “Lifetime” was that we got many requests by people asking us if our premium plugin continues to work after one year.”

True that users keep asking that question on seemingly any plugin available. Hence that question is handled in the FAQs by most authors preemptively, they still avoid “lifetime” in advertising.

I do appreciate your attempt at making things more transparent here and I hope it works for your customers on the long view. Nothing worse than a bad image due to misunderstandings as it is always hard to clean it off afterwards.

Just an experience of a 50 years old boomer ??

Sorry for stepping in without being asked, especially for not being a user of this plugin (however interested):

I have to agree with Frobastic here: all major premium plugins that offer lifetime licenses come along with lifetime updates which actually is the essence of a lifetime license.
The mere persistence of functionality beyond the deadline of a limited license is standard with most plugins; hardly any plugin stops working at the end of the license duration.

Compare to Genesis Theme Framwork, WP time capsule, Shortpixel imageoptimizer, etc.

On CodeCanyon you also get lifetime updates, but only 6 months support which is another difference.

You should seriously reevaluate your policy or the way of advertising here, because “lifetime” with limited updates AND support is simply misleading and won’t be cherished a lot.
Of course, if you offer unlimited sites instead of lifetime, limited license duration will be recognized as normal.

Well, no reply after 5 weeks, so plugin perma-removed.

Joined today. In QUIC.cloud panel the ‘generate certificate’ feature doesn’t seem to work. Keeps telling me “generating” in a yellowish line and browser complains about insecure page on website connection.

What’s wrong there?

You’re welcome.

??

OK, gut my host to update to the latest cURL. They first hesitated due to recommendations on their Debian package regarding downward compatibility (about the same as jQuery stuff with wordpress …. compatibility over security), but now I got it. Unfortunately that didn’t do the trick. I realized that openSSL also seems outdated, so I shall keep readers here posted.

@autotutorial Thanks again for the input. Can I update cURL locally or is that hosting company stuff?

I pretty much run into the same issue.

WP 5.2, PHP 7.3.5 as Apache-FPM (nginx in front), cURL 7.29.0

The error was plugin related on my server. Removing …

– Bookly Calendar(basic plugin, not an addon)
– miniOrange Two-Factor
– SP Gravity Forms WPDB Connect

… had that error vanish. Unfortunately, I need those.

@markrh

Thank you for your input. I’d like to ignore that one, too. However, on the larger frame I am looking for the cause of my site “phasing in and out” …. i. e. without any changes made sometimes it is accessible and working just fine, an hour later I receive “your website has a problem” on a grey screen (which disappears when adding “OLD” to my plugin folder. That’s when I found that certain plugins throw that error and began wondering.
Of course, I am not sure if that cURL error is behind that instability problem as stats also show CPU memory is exhausted repeatedly. Now I am not on a New Relic plan so I can’t tell the cause here. And to quote McCoy: “I’m a doctor, not an engineer …”

For now I try to get rid of that cURL thing and watching the stats and stability with the mentioned plugins being turned off since last eve.

@autotutorial :

Thanks for the response. As for the link and the given hints there:

– Make sure your server is running a recent version of PHP and the cURL library.
PHP 7.3.5 as Apache-FPM (nginx in front), cURL 7.29.0

– Try to increase your Server Memory Limits settings.
memory_limit: 768 M

– The cURL error can be a dns related issue. Your hosting company might need to switch dns configuration to OpenDNS : https://www.howtogeek.com/164981/how-to-switch-to-opendns-or-google-dns-to-speed-up-web-browsing/
Not sure about that one. DNS wise the site runs thru Cloudflare, DNSSEC active, in case that’s somehow important. Will check with hostpress on this one.

– Ask your host if there is some limitation with wp-cron, or if loopback is disabled.
wp-cron is called hourly by server, alternate_cron in wp-config is switched off. A test with alternate_cron ‘on’ did not solve the error.

– Ask your host if there a firewall or security modules (e.g. mod_security ) that could block the outgoing cURL requests.
Will check with Hostpress on this one.

As for OpenSSL: version 1.0.2k

So far, thank you for the input and the link.

BUMP! Support forum? Anyone? Why am I not surprised ….

Well, I decided to deactivate BUP. There’s a Woo solution for booking that works as well and with Woo I have all the payment options I need with Stripe. Like I said: There goes another customer …

• This reply was modified 6 years, 10 months ago by Sven71.