cambofrizz

Well, what a surprise. As the OP stated, that’s exactly what we experienced: an explosion of spam emails after we did not sign up for the ‘pro’ version.

HELLO WordPress, are you even screening these ‘free’ plug-ins or what?

I really have no idea why the plugin author is not responding to this issue, which is quite easy to fix. The author seems to have completely lost interest in updating the plugin.

In the latest version, the plug-in author has introduced checks for whether a post is password protected and it’s published. It’s this latter check that causes problems, because the post status this plug-in checks for (‘published’) doesn’t exist. A published post has the status ‘publish’. So lines 186-188 of the file class-wp-post-modal-public.php in the folder ‘public’ should NOT read:

        } elseif ($post['post_status'] !== "published") {
            $response = new WP_Error('post_private', 'Post is not published', array('status' => 403));
        } elseif ($post['post_content'] && $post['post_status'] === "published") {

but instead

        } elseif ($post['post_status'] !== "publish") {
            $response = new WP_Error('post_private', 'Post is not published', array('status' => 403));
        } elseif ($post['post_content'] && $post['post_status'] === "publish") {

Gee, that’s actually quite basic knowledge of WordPress.

I can confirm that something is amiss with the latest version (3.7.0). Clicking on a link does nothing. I cannot find any error in the console log, so I have no idea what causes this mishap.

Also did a rollback to 3.6.3 and that works fine. However, the latest version includes some security fixes, so it might be important to quickly repair that version. Isn’t it a bit strange that the developers don’t reply here to try and find the bug?

I have done that myself (deleting “new_features_notice” in DB), so the message would show again. Now, when dismissing the message I got “success: true” in the console, and I only had to click once. I’ve tried several things with plug-ins activated and de-activated, but I cannot replicate the initial behaviour as reported in the first post. I guess it must have been some temporary glitch in my set-up. Although it would be nice to find out exactly what it was, I’ll leave it at this.

Since your suppport here was quick and to the point I have revised my rating.

If your dev team has already found the problem, I don’t see why you cannot simply release the new version. As written above, I cannot replicate the problem after the message was removed when Disable Gutenberg was de-activated.
Also, this is on a local install.

You don’t understand. I don’t think the issue is resolved, I think the message doesn’t appear again, because it was once successfully dismissed when the Gutenberg plug-in was disabled.

Not anymore, as the message is already gone. I did a rollback to the previous version and then updated, but the message did not appear again.

Apparently it has to do with turning off the blocks in WordPress. I have the plug-in Disable Gutenberg installed and activated. When I de-activate that, the major update message disappears after clicking the dismiss button. It also doesn’t come back when I re-activate Disable Gutenberg.

Oh, one more thing: the input for latitude (owmweather.php line 502) is forcing a value of 90, should be min=”-90″.

• This reply was modified 3 years, 2 months ago by cambofrizz.

Thanks very much for your fast reply and fixes. Working fine now.

There’s just one little glitch: while sunrise and sunset in the ‘Today’ panel are in local time, moonrise and moonset are not: the time zone is added twice to the UTC time.
It’s because in owmweather.php on lines 2049 and 2050 the time zone is added. However, it takes the time from the daily moonrise and moonset data where that already has happened.

Thank you very much, that worked!
You have made a fantastic plug-in, I really like it.

A few remarks:
It seems the icon set-up needs attention, as the current weather icons always load Climacons, regardless of the Icon Pack settings. Also, with some other pack settings (e.g. Weather Icons), the temperature units are not displayed and in the forecast the condition icons are missing, too. Not sure if it is related, but why is there no ‘default’ choice in the individual weather Icons Pack setting?

Also, the hourly forecast in the table setting ignores the setting in ‘Number of hours’ and displays the standard 48 hours.

The above is just to fine tune, because again, it’s an excellent plug-in!

I just did a fresh install of XAMPP and WordPress: unfortunately got the same result when trying to activate the plug-in. So, it seems not related to Laragon but to localhost in general.

I just installed the original plugin (WP Cloudy) and that gave no error on activation or in use. But that one of course is very old and also doesn’t use ‘onecall’ as far as I can see.

Just FYI: I’m trying to install this on a localserver development website. The website is a clean WP install with no other plugins activated. WP_DEBUG shows nothing, no log file is created.

As the error message is a connection issue, I suspect the problem may have to do with my local SSL certificate, which of course is a ‘self-signed’ one. I’m using Laragon as the local server environment. I never had a problem activating plugins on this local SSL certificate, but I know this sometimes gives problems.

I tried to remove the SSL and just use http instead of https, but that gave the same result.

And you are right: on a live server I had no problem installing the plugin, so it definitely has something to do with localserver. Which, by the way, is important to me for developing websites.

• This reply was modified 3 years, 2 months ago by cambofrizz.