Thierry

I was a huge fan of this plugin when it was new. It was (as far as I know) one of the first ones to offer meaningful and well working Gutenberg block extensions. Over the time, one could already see that the author wasn’t able to consecrate the needed time to maintain and to further develop his blocks. I think we have to respect his personal decision. From what he writes on capitainewp.io, he is rather business oriented and not forcibly the geek we’d like him to be.

Now, I guess that someone more geeky could fork the repository and continue the good work. Anyone?

That sounds very German: “If there is written compatible with PHP 5.6 it has also to be compatible with PHP 5.6!” (And now take your spiked helmet off) ??

Not sure if this is the correct attitude… As a software developer myself, I neither care about backwards compatibility nor do I make a statement about that. To educate my clients, I sometimes even add specific code to prevent my software from running on outdated systems under WinXP or Win7.

And so, I also think it is the duty of every website operator to constantly update and maintain their installation because using obsolete software like outdated PHP versions opens security holes and puts your server and all clients who visit your website potentially to danger.

Thus, instead of pestering about an outdated compatibility information, be responsible and update your server, please!

Just wondering why one would still use a deprecated version of PHP… WordPress themselves recommend using 7.3 or above.

They state as follows:

Note: If you are in a legacy environment where you only have older PHP or MySQL versions, WordPress also works with PHP 5.6.20+ and MySQL 5.0+, but these versions have reached official End Of Life and as such may expose your site to security vulnerabilities.

Works for me! Thank you for your great work!

As far as I know, the plugin settings are theme related and stored by the WordPress engine in conjunction with other theme parameters. Thus, you’d have to redo all settings manually in the new theme.

Can’t confirm about communication. Up to now, Oliver always replied within minutes, and he was always polite and helpful.
For me, it’s one of the best supported plugins. That’s why I, besides buying the pro version for two websites, made even additional donations in an earlier development stage to get some custom features which then found their way into the public release.
My German is perhaps a bit rusty (as you might know, we Frech people are highly foreign language autistic), but isn’t there a proverb, saying “Wie es in den Wald hereinruft, so schallt es auch wieder heraus” ?

@hansbeen: Don’t make an idiot of yourself… After updating the plugin, there was a popup with instructions and a link which allow to get back all functionalities. It is sufficient to read and to follow the instructions.
https://webd.uk/new-separate-premium-plugins/

• This reply was modified 4 years, 11 months ago by Thierry.

Allow form submission when the client has a public ipv6 address. I guess that there could be a format or length problem when the form tries to process the client‘s IP address during submit if it is the longer ipv6 address format?

Although I think I shouldn’t support people who make money on other people’s misfortune, I’d suggest that you cache your websites through a CDN like cloudflare. Even the free version is already impressive:

One of my websites has lots of images in carrousels to load (artistic stuff is more demanding for eye-food) and cloudflare brings the load time down from 3.54s (worst case) to 202ms (best case / all cache hits).

Yessss!!! It’s solved! Thank you so much!!!

Enough shouting in the desert. I’ll try to wait patiently for a diagnose and the solution…

Have narrowed it down: The back to top arrows on front-page sections behave normal when I uncheck “Use featured image as header image” in the header options. As soon as I check that, the back to top arrows go nuts.

The back to top arrow problem is (at least now) independent from the parallax settings and shows all the time (on this website) as soon as I enable these for front-page sections.

I’ve no idea from where that comes. I removed all usual suspects from the pages which are used as front-page panels, featured images, read-more links, shortcodes, but the problem persists: https://dev.upie.fr

I just noticed it. I haven’t ever used the true parallax thing on other websites. The only thing which I can confirm is that I haven’t this problem on my own website where I don’t use true parallax…