Images not displaying and saved with spacer.png after upgrading to Beta 1

Please upgrade to beta 2, and let us know if you are seeing the same first of all

Sorry Marc, I should have elaborated. This issue came up after upgrading to Beta 1, and is still there after upgrading to Beta 2. 😅

I can confirm that I also see this on beta 2.

Newly attached images works just fine. also, if i simply edit a post and re-add the attached photo to the post itself, it works just fine.

This is because spacer.png (Default Blank Image) is set as src and the correct image is in data-src.

The same problem occurs in the RSS feed.

Unfortunately this happens with EVERY image converted from IC4 to IC5.

I will add for information that this also happens if the image is not an attachment, such as a GIF.

40 minutes ago, SeNioR- said:

I will add for information that this also happens if the image is not an attachment, such as a GIF.

This happens with all the images in the description or comments, whether they are attached or a direct link from another site

On 10/24/2024 at 11:50 AM, Marc said:

Please upgrade to beta 2, and let us know if you are seeing the same first of all

any updates on this?

if there's a quick why to fix this I would love to know and manually fix it even before the next beta..

14 hours ago, Omri Amos said:

any updates on this?

if there's a quick why to fix this I would love to know and manually fix it even before the next beta..

We would not provide quick fixes between beta for the most part. If you are in a position you need really quick fixes to an issue, you really should reconsider using a beta product

Please don't give me that attitude.

I am 100% confident in running the beta version. I tested it on a test duplicated site before switching, and it is much better for me than the v4 version even with this bug.

My world will not collapse if this takes some time to get fixed.

However, if it's just a quick CSS fix, for example, then I don't see why you wouldn’t just say how to fix it so this bug will be fixed sooner rather than later. What are you gaining by not telling us how to fix it, assuming of course it's a quick, easily manually fixable issue?

Anyway, you didn't even answer the question about the updates... is this bug even got looked at yet?

We are not your enemy. We are users who install the beta software on our websites in order to HELP YOU find and fix bugs before the final release. Not asking for a "thank you", but complaining about our interest in the status of our reported bugs is not very nice.

Thank you

50 minutes ago, Omri Amos said:

Please don't give me that attitude.

I am 100% confident in running the beta version. I tested it on a test duplicated site before switching, and it is much better for me than the v4 version even with this bug.

My world will not collapse if this takes some time to get fixed.

Sorry to hear you believe there was some kind of attitude there. That is certainly not my intention. Given the chasing of fixes, this tends to indicate you are waiting for them. When running a beta, you should always expect its going to be in the next release. If not the next couple of releases. 

59 minutes ago, Omri Amos said:

However, if it's just a quick CSS fix, for example, then I don't see why you wouldn’t just say how to fix it so this bug will be fixed sooner rather than later. What are you gaining by not telling us how to fix it, assuming of course it's a quick, easily manually fixable issue?

Allow me to explain. We have many many bugs being reported. Some of which are large bugs, some of which are oversights, and some of which will have unintended consequences upon other items of what is a very new product. I am not a developer on the product myself, and the developers are very busy resolving bugs and doing updates for a major release. So it will not always be possible for me to answer the question, other than exactly what was stated above.

We would not provide interim fixes. These need to be tested individually, and then tested with the product as a whole. One change may depend upon another. If I were to give you whatever the fix happened to be at the time, it may well break your system more, as I dont have the required knowledge to make that decision. For that reason, we have to follow the release process. 

59 minutes ago, Omri Amos said:

Anyway, you didn't even answer the question about the updates... is this bug even got looked at yet?

At present, the bug is "Open". Which simply means its not been resolved. There may have been someone look at it. There may have actually been several people look at it. Outside of speaking to every developer to see if they have looked at that particular item, its not possible for me to tell me anything other than what you already know. Its a bug report in our bug tracker and you havent yet got a fix.

1 hour ago, Omri Amos said:

We are not your enemy. We are users who install the beta software on our websites in order to HELP YOU find and fix bugs before the final release. 

Again, Im sorry to hear you believe you are being treated as 'the enemy' here. Its simply not possible for me to provide updates to every bug, interim fixes for every bug, and up to date what has and hasnt been looked at. We have hundreds of items. While I appreciate you are interested in this one, other bugs are of interest to other people too.

1 hour ago, Omri Amos said:

Not asking for a "thank you", but complaining about our interest in the status of our reported bugs is not very nice.

I'm just letting you know its not possible to provide interim fixes, and if you do need them, its not worth using a beta. This wasnt a complaint in any way. We're unable to presume your own personal ability, so we do need to ensure people know this information. I can only apologise if you were offended by me providing this.

Got it, thanks!

This issue is now fixed after upgrading to Beta 4. The topic I left with the blank image is now being displayed correctly. 🥳

https://www.japanesespitz.au/topic/6-number-1-australia-joins-the-community/

Thank you team!