jorenvh

Hi

I dug in the code and found that the issue is not with this plugin but within the Azure storage plugin.
However it will impact all users of this plugin that use the azure storage plugin as well.

Azure storage is getting a 409 conflict response when trying to overwrite the existing file in the blob storage. With message “The blob type is invalid for this operation”

It seems like they are doing something wrong when trying to overwrite the file.

I’m happy to leave an update here when I or the plugin owners find a solution for the issue

Joren

Thank you for investigating, I will just ignore it for now as it’s just a notice and not an exception. Maybe we can keep this ticket open and I can provide you with an update as soon as I found the issue or when I was able to upgrade the AMP plugin?

I’m using https://amp-wp.org/ on version 0.7.2, a little bit behind as we need to plan some time to do a major rewrite in order to support their 1.x release.
We will be upgrading that plugin in September according to project planning.

Hi

Thanks for you reply.

I wasn’t even considering making changes in core files ??

The option you provided was something I found already but that’s not what I’m looking for. I need a way to make them required even when it’s only when they are added as a feature image or if they are added to the content of a post.

If that’s not possible a way to alter the html printed their would be awesome, so that I can add the “required” value on those fields and add an extra paragraph with some extra guidelines.

Any idea if this would be possible?

Thx
Joren

Hi @mazedulislamkhan

Can you please reopen the ticket?

thanks
Joren

Hi @mazedulislamkhan

Can you please reopen this ticket? It is not resolved yet. Starting next week we have a dev sprint planned for this project. In that sprint WP & the plugin will be updated to the latest version so after deployement to production (first week of April) I can guarantee if this is fixed or not.

Sorry that I didn’t get back to this topic, but I’m bussy planning the next sprint and release for this project.

Joren

Hi

I found some time (I had put the ticket aside so that it didn’t eat all my available time for this project) to further debug this issue and apparently it was bug in my own custom code for this project.

What happend:
I overwrite the url of an image so that it loads the image from our CDN, but we recently switched from a multi site to a single site installation and apparently WordPress uploads the images in another folder for single sites. Changing the CDN path resolved the issue.

Stupid bug but it was my own fault ??

Thanks anyway!
Joren

Doesn’t compatibility works in two directions? I’m just trying to (help) resolving this issue, so sorry if I misunderstood something ;).

Kr
Joren

I also reported the issue in the support forum of WPML. Explaining the issue and I asked them to share a copy of their plugin so that you can replicate this issue locally.

https://wpml.org/forums/topic/compatibility-windows-azure-storage-for-wordpress-plugin/

But it says you guys are compatible so I suppose you guys had access to the plugin to make sure it’s compatible.

I can ask if the plugin can be shared for testing purpose for compatibility?

I would love to but I’m afraid I can’t since we are under NDA. I can guide you through the process of replicating this issue.

Setup:

* Latest WP
* Latest WPML version (inc translation managment plugin)
* Latest windows Azure storage for WordPress plugin (using azure CDN as cname)
* 2 our more active languages

=> now try translating anpost using the translation editor or by clicking the + icon on the post listing page. You will see the featured image of translations isn’t working

Kr
Joren

Is there any extea info you nead?

Hey Thanewest,

Indeed very weird! In my case I can tell that it has nothing to do with that since my servers & wp version did not change in the last couple of weeks.

I’m definitely installing the other one! Thanks for the info ??

Hi Thanewest,

Thanks for the info. I noticed that turning the plugin off and on removes the errors until I deploy the next version. So definitely switching to the other one.
Strange though since I’m using this one for over a year already, the first time that I’m having troubles.

Thanks,
Joren

Hi,

I’m also getting the following errors:

Warning: Illegal string offset ‘image_size’ in /wp-content/plugins/rss-image-feed/image-rss.php on line 133

Warning: Illegal string offset ‘image_size’ in /wp-content/plugins/rss-image-feed/image-rss.php on line 133

Warning: Illegal string offset ‘sitewide’ in /wp-content/plugins/rss-image-feed/image-rss.php on line 152

For some reason, it only shows these errors on my staging environment and not on my dev machine.

Where you able to solve this issue yet?

Thanks,
Joren

No problem at all, can not expect you to remember everything who asks a question in here ??

For others who would land here our are following the topic, Edward solved the problem and it will be available in the next release