Miguel Muscat

Hi Spike,

This is a known incompatibility with the WooCommerce PayPal Purchases plugin. The developers of that plugin are already working on a fix for this issue, and they will release an update that fixes it.

Hi @mymothersdaughter

If you are not using any templates that include images, then this should not be happening. But I wouldn’t call it a vulnerability. It’s most likely just a “bug”, when the code has some imperfection which leads to weird behavior.

On the off chance that it is a vulnerability, as @fierevere said, we should continue this conversation in private so as to not publicly disclose information that malicious individuals could use to harm other people’s sites.

So kindly send us a message using the contact form on our site. Click on the “Premium support” button and then choose the “Other” option.

Hi @cragbriggs,

I’ve inspected the error on your site and I’ve found that this issue is most likely not the plugin’s fault. Your site might not have HTTPS properly configured, or may have something installed that is interfering with HTTPS.

Here are my findings:

The plugin is making a request to this URL (notice that it uses HTTPS)
https://baigalidesigns.com/wp-json/sl-insta/media/feed/

However, your site is responding to this request with a redirect:

Status: 301 Moved Permanently
Location: https://baigalidesigns.com/wp-json/sl-insta/media/feed/

This triggers the browser to use the “Location” URL instead, which as you can see is not an HTTPS URL. When it does so, the request fails because of “mixed content” (you cannot have HTTP content in an HTTPS page).

By the way, I obtained this information from the “Network” tab in the browser’s console, in case you wish to confirm this yourself. The relevant request will be near the bottom of the list, called “feed” and will probably be marked in red.

So for whatever reason, your site is intentionally redirecting REST API requests to HTTP URLs. We’d advise that you start by checking if one of your other plugins may be responsible for this redirect and if it can be turned off from that plugin’s settings. Failing that, your best bet would be to get in touch with your hosting provider to resolve the issue.

I hope this helps!

• This reply was modified 3 years, 8 months ago by Miguel Muscat.

@snorklez Just a heads up: we’ve released an update (v0.6.1) that patches the plugin to be compatible with PHP 8. Let us know if that works for you!

Hi @monomatic

Thanks for bringing this to our attention. We’re just about to release version 0.6, and I’ve included a patch for these warnings in the update. The update should be available within a few minutes.

Hi Fyn,

Yes, let’s continue discussing the second issue via email.
Since the issue of this thread has been fixed, I’ll mark the thread as resolved.

Hi @mks123,

It appears your site might not have a valid “gmt_offset” option in the database.

Kindly check your site’s timezone options in the Settings – General page. We recommend clicking the Save button even if you do not change any of the options.

Hi Fyn,

We’ve had a similar report today that turned out to be caused by a failed import of the Instagram posts. The solution to this is to simply re-import the posts. You can force the plugin to do that by clearing its cache:

1. Go to the Settings page and click on the Tools tab
2. Click the Clear cache button and wait until the button changes to Done!
3. Go to the Feeds page
4. Click on your feed to edit it
5. You should see a notification come up that says that posts are being imported from Instagram

This should hopefully resolve your issue. If not, we’ll have to wait to see the feed on your website, which may give us some more insight.

• This reply was modified 3 years, 11 months ago by Miguel Muscat.

Hi @fyn

After saving the feed, did the preview immediately change to only show 2 posts, or does the feed only show 2 posts when it is embedded on the site?

We understand.

Let us know how it turns out, so we can update this thread accordingly for other users that may be facing a similar issue.

I see, that’s rather odd as there’s usually an explanation of what went wrong.

So then we will have to use our best judgement. We believe that you may be missing the “cURL” PHP extension from your site, or have the “allow_url_fopen” PHP option disabled. We’d recommend contacting your site’s hosting provider and forwarding this information to them, so they can enable these features for you.

Hi @arlenefoy1,

First of all, I’d like to apologize for the inconvenience this has caused you. We understand that these errors can be hard to recover from, sometimes requiring quite a bit of manual work. So we’re sorry about that!

Secondly, it seems like you’ve omitted the first line of the error in your report. This first line is the most crucial as it outlines what exactly went wrong. Without this information, we unfortunately cannot be sure what caused the error.

Our best guess is that your site’s server is lacking a feature that is required for our plugin to be able to communicate with Instagram, such as the PHP cURL extension.

But before we go any further on just speculation, what exactly triggered the error? If possible, try triggering the error again and copy the first line of the error, which is typically a message in plain English.

Thanks, we’ll keep doing our best!

Hi @ktvran

The errors you are seeing are due to intermittent problems from Instagram’s end, which means we unfortunately have no way to resolve this problem ourselves.

From our testing, we’ve found that trying to connect the same account multiple times usually results in success after around 5 to 6 times, though your mileage may vary.

We’ve also noticed that business accounts seem to be unaffected, so we’d encourage you to consider upgrading to a business account. It’s free and comes with many other benefits.

Other than that, we can only wait for Instagram to resolve its issues.

@giantguineapig What exactly is reporting that the dates are invalid? Is it some other service that is reading your WPRSS feed?