Joe Workman Stacks Updates Crashing

Ricinport

Hi

Anyone else having problems with Joe Workman's Stacks updating or is it me?

Ric

FigNewt2

Me too! Seems to be the older stacks that fail to update.

UPDATE:

All good tonight! All I know is, it would go faster if I didn't have so many of Joe's stacks!

thinkfilm

I just checked with Joe Workman's support and they are aware of the problem and are working on it. Slowly, it seems some of the stacks that failed to update are being updated. I bet it works itself out over the next day or so.

mitchellm

Crashing still happening with about half the stacks that try to update. Others updated fine. Been the case for several hours now.

thinkfilm

Problem now resolved for me. All my Joe Workman stacks have just updated successfully. Hope you guys can say the same soon enough.

mitchellm

One of mine not loading before now loaded. However, I have a suspicion that not have uploaded (but somehow thing they have). Is there an easy list somewhere so we can check what version number we should have?

For example, my Dispatch Dropbox stack reads 1.2.4, but I believe that's an update from a week ago (and so it may be fine OR not—don't really know).

At any rate, a simple list somewhere at Joe's site so we could double check version numbers we should have would be a great help. It's a PITA to go to each stack, plus I doubt the version numbers have been updated for today's change.

I guess I'll know for sure when the new version of Stacks comes out!

Colorwave

I just successfully updated a ton of his stacks with Sparkle. No hitches for me, so hopefully whatever was causing the problems reported here was fixed.

Rusty Wood

All seems fine now 70+ stacks updated... tried earlier and only had a 50% success rate ..

Rusty

mitchellm

Seems to be fine now. Some new stacks updated for me.

kpryce2

So why such a large number of updates? What has been changed?

thinkfilm

According to the update notices all these address a (mis)setting that relates to the Stacks API that needed to be corrected before the release of Stacks 2.1. I've seen both Joe Workman and Isaiah (of Yourhead) have used the phrase "overzealous use" by the developer to describe the situation that precipitated the updates. Make of that what you will.

thinkfilm

Just a follow-up: personally, I've experienced no problems before or after the flurry of updates so I assume the stacks API issues they address are somewhat esoteric for the average user.

kpryce2

Thinkfilm,

Agree I've tested a few of the updates and nothing is obvious to me. They all worked fine before the updates.
Ken

Colorwave

The worked fine before the updates, but not with Stacks 2.1. Joe is being proactive in fixing this before it becomes a problem for most users. Given that it only takes a couple of minutes to update them all, I think we should be grateful that this is being sorted out before, not after, anything is screwed up.

Ed Brenner

Joe was using both a 'min' value and a 'max' value for the API in the pList. He had to remove the 'max' value.

Kevin Mullins

Had a few issues updating yesterday but all sorted now. Agreed @Colorwave, I'm glad Joe was proactive on this as opposed to reactive.

joeworkman

Hey everyone. Sorry for not responding to this sooner. All of the updates should be working well now. Please let me know if you are still having issues with any of the stacks.