Lee Collings

Hi @wpfleek ,

Thanks for your reply. I actually noticed you had a 4.0.1 update before you posted the reply on here. So I immediately went to check that out.

You’ve fixed every issue I had, so thank you for doing that so quickly, and your reply. Having this communication has indeed restored my faith in OceanWP, and I will happily embrace the new features and check them all out.

I’ve learnt some things myself too, particularly to make very good use of the staging environment I have set up on my web hosting – which sometimes I admit – I bypass just to get things done quickly.

So again, thank you for allowing my rant, and listening to my concerns, and acting quickly.

Hi @pk385 , thanks for providing that, appreciate it.

Well I’m not really expecting much, being a major release, they’ll stick with this now.

However, the fact a child theme is able to be used is potentially the lifeline here, because I can turn off google Font loading within Customiser, and then make use of the child theme, and simply request Google Font usage from a standard enqueue_style within there.

Benefit of this, being my own code to call the fonts, I know what it’s going to be doing!

The other points are very valid though (lack of awareness this was coming, and the fact to try and hide it by disabling by default). Clearly that’s an admission that it’s not right.

Also an extra point I’d like to make. The option you provide ‘Load Google Fonts Locally’. Can you actually explain what this is doing?

You claim ‘Host Google Fonts directly on your site for faster loading and improved privacy.’, but you don’t offer any detail as to how these are hosted on our site.

Are you downloading the Google Fonts and storing them locally on the website to use?

Having this option enabled has no effect on the loading time of the site, it is still incredibly slow, whether this be on or off.

@gautammkgarg you can spin it however you want, but what you’ve tried to claim and back up doesn’t state WordPress is *compatible* with PHP8 or all, it states very well this is in beta.

As of right now, the fully compatible version of PHP is 7.4.

What PHP themselves state what they support is completely irrelevant.

It just annoys me that you’re completely alienating the largest majority of WordPress users by PHP version (according to the stats that you yourself posted), who are unable to use your plugin.

To me, that sounds like a really bad business plan.

But that’s entirely up to you. Good luck.

Just curious to know why have you seriously limited the use of your plugin to OUTSIDE the recommended safe running environment of WordPress?

WordPress is not compatible with PHP8 even as of yet (not fully). PHP 7.4 is the latest stable version that WordPress is 100% compatible with.

Because of this, I don’t run anything higher than PHP 7.4 on WordPress sites, until that changes.

https://make.www.ads-software.com/core/handbook/references/php-compatibility-and-wordpress-versions/

Hi there, I’m not the plugin author, but I’m a user of the plugin (and a WordPress Developer). This plugin doesn’t have that kind of functionality that you’re looking for.

Just if it adds anything extra, I’ve also posted the same question on Stack Exchange

https://wordpress.stackexchange.com/questions/417273/wordpress-not-showing-plugin-updates-available

No need, because I’ve fixed both issues myself. I was raising the point that this update has knocked out several other websites now that I Wouldn’t have realised until I checked them.

I would suggest you peer review this update that you’ve sent out.

This has happened to two of my websites now, both with this plugin. Updating it has caused critical errors on both sites. Seems a dangerous update!

I’ve just had this as well. Updated the theme, and now the site cannot load!

An error of type E_ERROR was caused in line 128 of the file /home/sites/3b/d/de7735dff3/public_html/wp-content/themes/oceanwp/inc/customizer/controls/typography/webfonts.php. Error message: Cannot redeclare oceanwp_webfonts_enqueue() (previously declared in /home/sites/3b/d/de7735dff3/public_html/wp-content/plugins/ocean-extra/includes/compatibility/ocean.php:94)

Don’t resolve it, this issue isn’t resolved!

With all plugins except WooCommerce the issue is still there.

So what am I supposed to do then?

You’ve stopped me from being able to update now. Are you even doing anything about this?

Also, can you please REMOVE the ‘resolved’ tag… as this is not resolved!

• This reply was modified 2 years, 5 months ago by Lee Collings.

Hello,

No problem. I’m trying to help as much as I can, however there are really things you need to fix and sort out quickly with this or I’ll have to pass this on to the WordPress Developers because you are not following the guidelines for developers. You also haven’t made any reference to any of my points I’ve made and have completely ignored what I’ve written. So I’ll write it again.

The current version my plugin says is 1.4.8.

The plugin details now say the current version is 1.4.5 (so you may have made an update since 1.4.4 as noted in my post, but obviously because for some reason my version is newer than this update you’ve made – I cannot access it).

Again, looking at the changelog this is completely wrong and misleading as it shows updates for 1.0, 1.1, 1.4, 1.5 and 1.4.4.

You have completely messed up the versioning on your plugin and as such now you’ve made it unusable (and un-updatable for me)

So how am I supposed to update this if you’ve made it so that none of your updated versions are newer than mine (until you get past 1.4.8)?

@mdo I’m wondering if there’s anything can be done to help these guys?

Also, something else I’ve just noticed which isn’t related to this issue, but still reveals some really bad errors in your plugin details, is the Installation tab appears to show instructions for a completely different plugin ‘Unlimited Background Slider’…

Hi,

Thanks for your reply, however I don’t think what you’ve said is true at all.

Firstly, there are no waiting updates for the plugin within WP Admin.

Then there’s the strange behaviour of your plugin showing different versions, for example, the list of plugins is telling me I have version 1.4.8 installed.

However, when clicking to view more details about your plugin, it says the current version is 1.4.4 (and this is shown again on the plugin page on www.ads-software.com). The changeling only goes up to 1.4.4 also.

Can you please provide any clarity on any of these points?