Can't upload images in the Share your Work forum

[VectorWhiz]

I get Error 200 when trying to upload images to a post.

[v_kyr]

Check the characters used in and overall your filenames, there are certain combinations the forum upload feature doesn't like and then throws errors.

[walt.farrell]

Also, what kind of file, and what are the pixel dimensions? 

[VectorWhiz]

File name: Would it kill you to admit 2 Circular - 740 x 740

Filetype: transparent png

Dimensions: 740 x 740 px

Filesize: 261 KB

[GarryP]

Does the filename contain the multiplication sign, as it does in your text, or just an ‘x”?
If it’s the multiplication sign, can you try a name without it?

[Old Bruce]

17 hours ago, VectorWhiz said:

I get Error 200 when trying to upload images to a post.

Sometimes it is a problem with the net.

[VectorWhiz]

8 hours ago, GarryP said:

Does the filename contain the multiplication sign, as it does in your text, or just an ‘x”?
If it’s the multiplication sign, can you try a name without it?

I renamed the file to Test.png - same result. I used a regular x initially by the way. I tried uploading a different file - error 200 again.

[v_kyr]

35 minutes ago, VectorWhiz said:

I renamed the file to Test.png - same result. I used a regular x initially by the way. I tried uploading a different file - error 200 again.

Does it just happen with your PNG files now, or also with those as JPG files etc.?

[VectorWhiz]

jpg-files can be uploaded fine. png's still result in error 200.

[iconoclast]

Maybe the forum doesn't like Alpha Channels? Have you tried a png without transparency?

[VectorWhiz]

I have uploaded png's with a transparent background before and it did not result in problems.

[iconoclast]

18 minutes ago, VectorWhiz said:

I have uploaded png's with a transparent background before and it did not result in problems.

Yes, you are right, I tested it, and transparencies don't seem to be a problem. Even CMYK works. Possibly a problem caused by a Browser Update?

[VectorWhiz]

On 9/27/2022 at 11:50 AM, iconoclast said:

Yes, you are right, I tested it, and transparencies don't seem to be a problem. Even CMYK works. Possibly a problem caused by a Browser Update?

I tried Opera (what I commonly use), Chrome and Edge a transparent and uploading a png with transparent background resulted in error 200 again. The png's, by the way were exported from Affinity Designer.

[iconoclast]

My browser is Firefox. So possibly a browser-related problem?

[R C-R]

16 hours ago, VectorWhiz said:

I tried Opera (what I commonly use), Chrome and Edge a transparent and uploading a png with transparent background resulted in error 200 again. The png's, by the way were exported from Affinity Designer.

Just as a test, using any of your browsers can you attach a sample PNG file to a reply in this topic instead of to the share work forum, or do you get an error 200 here as well?

[VectorWhiz]

Yes. When attempting to upload the transparent backgound png-file that I inteded to upload in my share-your-work forum post, I receive a 200 error again, while before I was able to upload png's with a transparent background. So this problem has only occurred since recently.

[VectorWhiz]

@ NPM: the Dali image you uploaded has no transparent background. I have no problem uploading png-files that do not have have a transparent background.

[VectorWhiz]

The problem with uploading images (Error 200), seems to occur only with png-files that were exported from Designer version 1.105.1342 (Beta). I tried with a grey background and transparent, neither of them would upload. When saving the image again (without changing anything to the image) in FastStone image viewer, there seems to be no problem with images with a transparent background or a solid background. Perhaps take a look at the export engine code.

 

[thomaso]

2 hours ago, VectorWhiz said:

The problem with uploading images (Error 200), seems to occur only with png-files that were exported from Designer version 1.105.1342 (Beta).

I got this "error -200" quite frequently but also quite irregular, mainly for just screenshot .JPG done with macOS. Since I use https://imageoptim.com for every image (e.g. strip profile, re-compress) I don't get the issue any more. 🤞

(p.s.: any reason you still run a Beta ?)

[VectorWhiz]

8 hours ago, thomaso said:

I got this "error -200" quite frequently but also quite irregular, mainly for just screenshot .JPG done with macOS. Since I use https://imageoptim.com for every image (e.g. strip profile, re-compress) I don't get the issue any more. 🤞

(p.s.: any reason you still run a Beta ?)

Beta as far as I know, is the most recent development available, which is the only reason I run it. And by the way, relieved to see that I am not the only one having this problem, although apparently there are ways to work around it.

[walt.farrell]

45 minutes ago, VectorWhiz said:

Beta as far as I know, is the most recent development available, which is the only reason I run it.

It's only the latest when there's an active beta, but there isn't an active beta at the moment. The 1.10.5 release version is technically what you're supposed to be using. The beta you have may be the same level as the release version, but sometimes is slightly older.

[VectorWhiz]

20 minutes ago, walt.farrell said:

It's only the latest when there's an active beta, but there isn't an active beta at the moment. The 1.10.5 release version is technically what you're supposed to be using. The beta you have may be the same level as the release version, but sometimes is slightly older.

 

The update policy and numbering syntax is confusing. When a new version is released, users get a message when opening Designer that a new version is available, which I downloaded and installed, but you say I should not be using it?

[thomaso]

1 minute ago, VectorWhiz said:

When a new version is released, users get a message when opening Designer that a new version is available, which I downloaded and installed, but you say I should not be using it?

Beta and release version are two separate programs and entirely independent from each other. Once you have updated your release version it doesn't make sense to continue using the Beta which is older as soon it 'became' a release version.

As far I remember in beta versions the update message / auto-update feature never worked but we where informed via email & forum once a new beta was available.

[R C-R]

FWIW, this is a link to the most recent post in the Latest Affinity releases on each platform by store topic:

 

[Old Bruce]

17 hours ago, VectorWhiz said:

Beta as far as I know, is the most recent development available, which is the only reason I run it.

The most recent version is 1.10.5 and it is not a beta version. I would not use the beta version. I am surprised you can actually run it but maybe that is a Windows OS ability.