Textures upload issues and feedback #49930

Closed
opened 2016-11-04 11:00:30 +01:00 by Francesco Siddi · 10 comments

From some online feedback (could be refactored in better tasks):

I noticed problems with uploading textures

Problem 1:
When trying to upload (button "save changes") i get this error:
"The submitted data could not be validated."
it works right until i want to save it.

Problem 2:
I also noticed that canceling an upload creates an empty texture (which i mentioned in the last mail, producing wrong counts)
There are "empty textures" in different categories now. (for example category fabrics has much empty textures now)

These come from:

  • a few mistakes i made, causing me to cancel and restart an upload.
  • problems with uploading today and yesterday (see problem 1)
  • discovering the problem when canceling an upload
From some online feedback (could be refactored in better tasks): I noticed problems with uploading textures Problem 1: When trying to upload (button "save changes") i get this error: "The submitted data could not be validated." it works right until i want to save it. Problem 2: I also noticed that canceling an upload creates an empty texture (which i mentioned in the last mail, producing wrong counts) There are "empty textures" in different categories now. (for example category fabrics has much empty textures now) These come from: - a few mistakes i made, causing me to cancel and restart an upload. - problems with uploading today and yesterday (see problem 1) - discovering the problem when canceling an upload
Sybren A. Stüvel was assigned by Francesco Siddi 2016-11-04 11:00:30 +01:00

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @fsiddi

Added subscriber: @fsiddi

Are these issues still valid?

Are these issues still valid?

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

These were just some glitches in the texture upload workflow. I just tested a few variations of uploading and canceling upload of textures and it works correctly. Since this can't be reproduced in a reliable way, I will archive.

These were just some glitches in the texture upload workflow. I just tested a few variations of uploading and canceling upload of textures and it works correctly. Since this can't be reproduced in a reliable way, I will archive.

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Apparently the issue is not entirely fixed:

Some feedback from Blender Cloud user:

If an upload is canceled it still creates "empty textures" and leads to a wrong number of items in the header (for example category bark has now 20 textures in it, but in the header it says "22 items").

I tested it again, before uploading them there were 19 textures in this category, showing me 19 items.

Here I have created a list where i found these differences

Bark 22 / 20

concrete 61 / 59
eyes 18 / 17
fabrics 72 / 64
ground 78 / 69
plants 80 / 76
rocks 43 / 42
wall 23 / 22
wood 56 / 54 + subfolder

Apparently the issue is not entirely fixed: Some feedback from Blender Cloud user: > If an upload is canceled it still creates "empty textures" and leads to a wrong number of items in the header (for example category bark has now 20 textures in it, but in the header it says "22 items"). > > I tested it again, before uploading them there were 19 textures in this category, showing me 19 items. > > > > Here I have created a list where i found these differences > > Bark 22 / 20 > > concrete 61 / 59 > eyes 18 / 17 > fabrics 72 / 64 > ground 78 / 69 > plants 80 / 76 > rocks 43 / 42 > wall 23 / 22 > wood 56 / 54 + subfolder

This issue was referenced by b3a36f2833

This issue was referenced by b3a36f283309c5a295bafca6ed72d260bf999289

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Resolved in b3a36f2833, 666da0adda, and ae7489d8e7

Resolved in b3a36f283309c5a295bafca6ed72d260bf999289, 666da0addabc17e790bf7a8be04a23c4803a6025, and ae7489d8e7600a743ad69161f167b73fbd4e1da5
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: archive/pillar#49930
No description provided.