mumbomedia

Have the same problem and also an idea why this happens.

As I can see from the log snippet, Instagram is sending two HTTP responses in sequence.
429 and 302. 302 is a temporary redirect.
Instagram sends it because you are not logged in.

I also get the same result when I link to Instagram’s privacy policy.
This suggests that Instagram is responding to all HTTP HEAD requests that your plugin uses with a 429 HTTP response. I think this is due to search engine spiders possibly using the same approach and Instagram doesn’t want anything indexed by them.
This would explain Instagram’s behavior.

Of course, this assumption can only be confirmed or denied by Instagram itself but I am 99.9% sure that this is the case.

I see.
Thank you for this clearification.
I was just confused by this message because I never see it before.
So I can safely ignore this message, when updating from the dashboard.
As long as the zip file is loaded from www.ads-software.com it should contain only the files needed for wordpress to run and nothing else.

I would recommend to post this in the theme forum https://www.ads-software.com/support/theme/astra/ Therefore there is more chance that anyone see it and could help you.

That’s where I got the info from.
But this documentation isn’t helpful at all.

@sterndata

I don’t understand what you mean.
Could you please explain what’s wrong.

Kind regards

Alexander Behling

Hi Nikola,

that are fantastatic news.
Looking forward to the new release.

Kind regards

Alexander Behling

In general everyone can contribute to all plugins available from here.
Personally I’m working on the german translations because I’m a native german speaker.

So if you want to contribute feel free to do so.

Yeah that’s fine by me.

I look forward to the next update.
In the meantime, I’m going to ask our host if they can set the non-strict mode as the default so we won’t have any more problems doing a backup that we do by default every time we make major changes like wordpress- / plugin-updates or even a complete migration.

No problems arise in regular operation.
Only when creating / importing a backup e.g. An error is thrown via PHPmyAdmin because the strict mode of MySQL 5.7 or higher does not allow invalid date values.
You have to change the mode manually for the import to work via SET MODE=””.

Since 5.7, such fields should be defined as nullable instead, which in my opion also makes more sense. From the PHP programming perspective, it shouldn’t make any difference whether you check against “0000-00-00 00:00:00” if the value is an empty string.

Your welcome

That sounds good to me.

Kind regards

mumbomedia

Also strange that when the plugin is active fontawesome isn’t enqueued.
After deactivating it, the site looks as it should.

Your welcome.

Glad to hear that I could help.

Btw. for formal german pages I recommend using this plugin:
https://www.ads-software.com/plugins/language-fallback/

With this plugin you can setup the regular german translation as a fallback if a theme or plugin doesn’t provide a formal translation.
Also Loco Translate is an helpful plugin because you can edit the translation files on the server and therefore you haven’t to install an editor on your pc like Poedit (which is often updated and your get a update message everytime you open a file with it).

Hello @nikelaos

first of all the naming is incorrect.

The files should be named sitemap-de_DE_formal.mo and sitemap-de_DE_formal.po.
Then it will work.

great to hear that.

I assume that it will be announced in your newsletter (which I have of course subscribed to) as before.

I am excited looking forward to the next release so that I can use this as soon as possible.

Have a nice day and stay healthy

Kind regards from Germany

Alexander

It was a tricky one but I managed to get it to work.

Will there be any plans to make it easier to register custom presets, deregister even built-in preset (in case you don’t need them) and modifying existing blocks?

• This reply was modified 4 years, 6 months ago by mumbomedia.