Beta Test of new skin admin system.

[Vraciu]

Adoption went through.  Skin assigned.   Click on it under management page...


Skin Information
http://www.325thfg.org/
http://www.web-birds.com/15th/325/325th.htm



Directory Read Error
p51b_10 open failed

[oboe]

- I was able to select and adopt a skin (a P-39D by Rogerdee), I got to the Congratulations on your adoption page.   

- When I went back to main skins admin page, it shows only 8 released skins for Oboe, all P-38Gs.   I should have P-39Qs, P-38Js and Ls, P-51Bs and a P-51D.

- clicking on any of the 8 skins shown, it displays a bunch of php source code.

Logged out and logged back in again, still shows only 8 skins, all P-38Gs for oboe.

EDIT:  tried to submit a new skin, but it was for P-51D and I got the message showing all skins full. When I backed out of this, all my skins were showing again.

[Skuzzy]

Adoption went through.  Skin assigned.   Click on it under management page...


Skin Information
http://www.325thfg.org/
http://www.web-birds.com/15th/325/325th.htm



Directory Read Error
p51b_10 open failed

- I was able to select and adopt a skin (a P-39D by Rogerdee), I got to the Congratulations on your adoption page.   

- When I went back to main skins admin page, it shows only 8 released skins for Oboe, all P-38Gs.   I should have P-39Qs, P-38Js and Ls, P-51Bs and a P-51D.

- clicking on any of the 8 skins shown, it displays a bunch of php source code.

Fixed.  An adopted skin cannot be viewed until the update has been submitted.  Has to do with the skin actually still released, but being updated.  It is a rather complicated mess as it has to be moved out of the normal path of things so we know it is being updated.

We have to update two other databases manually, when a skin gets adopted, in order to be able to track it.

This is the best I can do for right now.

Oboe, you were working while I was making changes.  I am doing this live.

[Skuzzy]

Something is still amiss.

Give me a minute.

[oboe]

oh, sorry.  let me know when  clear to test again...

[Vraciu]

Fixed.  An adopted skin cannot be viewed until the update has been submitted.  Has to do with the skin actually still released, but being updated.  It is a rather complicated mess as it has to be moved out of the normal path of things so we know it is being updated.

We have to update two other databases manually, when a skin gets adopted, in order to be able to track it.

This is the best I can do for right now.

Oboe, you were working while I was making changes.  I am doing this live.

Okay.  So how can we view the original bitmap?  I like to have these to look for clues.   I’m guessing if we don’t save them before we adopt them we lose the ability to view them. 

[Skuzzy]

Ok, I think I have gotten things worked out where you can view the adopted skin from your front page.

Everything should be good to go now.

[Vraciu]

Whatever you just did fixed it.  I can see the original BMP now.  Nice job, Skuzzy. 

 

Now to try an update.

[Devil 505]

Adopted a 190A-5 skin without issue. 

[Vraciu]

I had a file named incorrectly and got stuck in a loop during the upload--never returned an error, just gave me the eternal circle of motion.   Fixed that issue when I noticed and it worked out just fine.  All files validated (I submitted every single one as a test).


Welcome to the skin update validation page.
Basic Skin Information
Object Name    p51b
Skin Name    325FG/318FS By Vraciu
Skin Reference    P51B8101605
Submission Update Status
File    Name/Data
Verified    Type    Size    Color
Depth    File
Format
dude1.bmp                
dude2.bmp                
fullsizeimg.jpg             N/A    
reference1img.jpg             N/A    
reference2img.jpg             N/A    
thumbnailimg.jpg             N/A    
p51b.bmp                
p51b_e.bmp                
p51b_n.bmp                
p51b_p.bmp                
p51b_s.bmp                

Congratulations! Your skin updates have been accepted for review!

[Skuzzy]

Which file was named incorrectly?

[Vraciu]

Which file was named incorrectly?

I believe it was reference1img.jpg -  I had it named as "reference1img - Copy.jpg" instead.

It worked right with the proper name.

I then went and did the entire process again with a second skin and it worked fine.  No misnamed files.     Heh.

[Skuzzy]

I'll check the error handling for that.  There is a window where I cannot post an error back to the client.

[Vraciu]

I'll check the error handling for that.  There is a window where I cannot post an error back to the client.

You want me to screw it up again on purpose and see what it does?

[Skuzzy]

I should be able to duplicate that.