You are here: Forum Home / RapidWeaver User Forum / Stacks Chat / Thread
I’ve found a few of my third party stacks to be incompatible with Stacks 1.3, and have let the developers know. But there are probably others waiting to be found, or that other people are aware of. So, is there a definitive list of stacks that need to be updated, or should we create one on the forum by people contributing their findings to it?
“They say Rome wasn’t built in a day, but I wasn’t on that job” (Brian Clough)
Hi,
I’d be interested to know which ones you’ve found to be not compatable. I have not yet upgraded to 1.3 for this very reason - I have some complex stack arrangements in several sites I don’t want to have to re-make…
Does anyone know whether the ‘Css stack’, ‘DssDiv stack’, ‘Countdown stacks’, ‘Url Image Stack’, ‘Html enclosure stack’, ‘Fixed background stack’ and ‘Spacer stack’ are working OK with Stacks 1.3?
Thanks,
Pete
Formula for success: Rise early, work hard, strike oil. J P Getty.
Alternatively… put your feet up and play with this…
Mauricio’s prettyPhoto stack doesn’t work and neither did Joe Workman’s RSS stacks (he’s fixed them now). I’m hecking off some others and will report any more I find
“They say Rome wasn’t built in a day, but I wasn’t on that job” (Brian Clough)
Most of these folks have made updates to these.
We took a lot of time and effort to try to make the API 2 very compatible with all the various stacks around. The one thing that seems to get in the way is that Stack 1.3 is a bit more strict when loading things. If it discovers that there is a problem while loading a stack that would cause Stacks to hang or crash later, it just doesn’t load that stack.
I think in both of the cases you mention it was a syntax error in the stack’s “plist” file. It may seem inconvienent that Stacks is refusing to load these, but it’s probably saved you from crashing later—so hopefully the few minutes spent updating now will be time well spent.
Isaiah
I’m Isaiah and I run YourHead Software. We make RapidWeaver plugins:
Stacks - Drag and drop, fluid layout.
Blocks - Put anything anywhere.
Follow @isaiah on Twitter. Read Isaiah’s blog.
The other stack I meant to mention in my original post was the Spacer stack from Will Woodgate. Re-downloading this (which Will appears to have updated) and the prettyPhoto stack (which Mauricio has updated) has solved the problem. I definitely think updating now is worth it in the long run, as Isaiah says. I’d just like to know from other users or the devs themselves which ones do need updating now. Its a big job to trawl through them all individually (I got so far before getting fed up!). Thanks
“They say Rome wasn’t built in a day, but I wasn’t on that job” (Brian Clough)
The other stack I meant to mention in my original post was the Spacer stack from Will Woodgate. Re-downloading this (which Will appears to have updated) and the prettyPhoto stack (which Mauricio has updated) has solved the problem.
Like a lot of Stack developers, I had access to the Beta of Stacks 1.3 so was able to make a head-start on improving compatibility with 1.3. Isaiah did an awesome job of documenting the new API changes, to the extent of producing short screencasts - these resources were a major help. The most important Stacks (like the Spacer stack) were updated, improved and published within 24 hours of Stacks 1.3 being announced. I can’t speak for other developers, but on my website I have clearly marked 1.3 compatible stacks and created an archive page of the older 1.2 stacks.
If you find a Stack which is not 1.3 compatible, my advice would be to report it to the developer. That way they will be made aware and can confirm one way or another if they are committed to providing future updates.
Themes: ThemeFlood
Stacks: Stacks4Stacks
The most important Stacks (like the Spacer stack) were updated, improved and published within 24 hours of Stacks 1.3 being announced. I can’t speak for other developers, but on my website I have clearly marked 1.3 compatible stacks and created an archive page of the older 1.2 stacks.
Thanks Will, that’s exactly the kind of information I would like developers to provide, either via this forum (in this post or elsewhere), and/or on their websites
“They say Rome wasn’t built in a day, but I wasn’t on that job” (Brian Clough)
I had several issues with the 1.3 update when first released. I decided to revert back until developers had time to update them. I haven’t had a chance since then to go back and test the potential culprit stacks.
Maybe I can find time tomorrow night to do so. If I find any remaining issues, I will notify the developer and post here so that the users know which ones are problematic for the time being.