Aces High Bulletin Board

General Forums => Custom Skins => Topic started by: Vraciu on April 25, 2016, 06:12:34 PM

Title: Skin Update Error
Post by: Vraciu on April 25, 2016, 06:12:34 PM
Skuzzy,

Tried to update a skin and received the following error claiming an update is in progress already.    :headscratch:

Any suggestions?




Title: Re: Skin Update Error
Post by: Skuzzy on April 26, 2016, 10:45:19 AM
Are you trying to update a kin you recently submitted, but has not been released?  You cannot update a "submitted" skin.  You can only update a "released" skin.
Title: Re: Skin Update Error
Post by: Vraciu on April 26, 2016, 11:49:07 AM
Are you trying to update a kin you recently submitted, but has not been released?  You cannot update a "submitted" skin.  You can only update a "released" skin.

Update to a released skin.
Title: Re: Skin Update Error
Post by: Vraciu on April 26, 2016, 01:13:47 PM
Did a reboot on my machine and tried to update again.  Same error.    :headscratch:
Title: Re: Skin Update Error
Post by: Skuzzy on April 26, 2016, 03:33:29 PM
Try it again.  I added the skin reference to the error page.  I need it.
Title: Re: Skin Update Error
Post by: Vraciu on April 26, 2016, 05:25:49 PM
Try it again.  I added the skin reference to the error page.  I need it.

Okay.  Standby.
Title: Re: Skin Update Error
Post by: Vraciu on April 26, 2016, 05:28:10 PM
 :bhead

 :cool:

Same problem.

Title: Re: Skin Update Error
Post by: Skuzzy on April 27, 2016, 11:04:40 AM
Found the cause.  Should be good to go now.
Title: Re: Skin Update Error
Post by: Vraciu on April 27, 2016, 11:57:00 AM
Found the cause.  Should be good to go now.

Just tried it.  Worked as advertised.  My thanks, sir.    :salute
Title: Re: Skin Update Error
Post by: Skuzzy on April 27, 2016, 11:59:54 AM
On the up side, the problem was actually correct.  A left over update, from the last batch, caused the error.
Title: Re: Skin Update Error
Post by: Vraciu on April 27, 2016, 12:11:53 PM
On the up side, the problem was actually correct.  A left over update, from the last batch, caused the error.

Ah!!   Go figure!  :)   :aok