File a bug report I guess. Someone just bought it earlier today. I’m mobile but I just see the Floppy link redirecting to the generic plugin homepage. I didn’t delete it or anything. Other plugins like Calendar Grid Pro are available. I don’t know what’s up with that.
Bug report:
Cheers, will do
Sorry Bubble is so dumb.
Haha, it’s okay.
It’s a brand new app and if I’d got off my butt and bought Floppy ages ago (I’d been making do with List SHifter) this wouldn’t be a problem
I don’t know what’s going on, but surely I’m not the only person affected. I don’t see Floppy in the plugin tab for purchase either, but given what I know about Bubble (everything), I’m not going to touch anything for fear of messing things up further. I apologize for the inconvenience, but file a bug report with them. There’s no reason that it shouldn’t be showing up. (I’d do a “cyber week” promotion off the cuff, but I’m afraid to push any updates.)
Hey @peter.hudson, oh I see the issue. I guess the server-side plugin update requirement (there are changes to the API there) deadline has passed. I had thought that was happening later this month, but apparently I was wrong. So Floppy is temporarily unavailable.
Anyway, I’ll make the required tweaks to bring it back as soon as possible.
Whew! I was almost crapping my pants thinking Floppy will be removed permanently eventually. It’s a critical plugin for my apps!
Thanks in advance for the update!
@ihsanzainal84 it’s annoying as I haven’t been in the mood to futz with Bubble plugins. It’s just the whole asynchronous field fetching thing in SSAs. Wouldn’t even be an issue for anyone if the Bubble plugin APIs weren’t so bare bones. It’s like, why does anybody even have to write a function to fetch a list? Core things like that should always have been part of the API so there’s an “official” canonical way to do them. Grumble.
Hi Keith,
Yepo - that’s the response I got back from them.
Look forward to trying it out.
I am building a fixturing system for a sports organisation and I think Floppy is going to be very helpful for creating many of the lists of objects.
Pete
Hey @keith - just noticed this:
I’m sure you’re aware of this, but as List Shifter is a pretty fundamental part of my app, I just wanted to confirm that it’s on your roadmap to update it so things don’t go dark on March 12.
Thanks mate,
Tom
Yeah Floppy has SSA plugins in it and those need an update for the new node API. I’ll get to it soon.
Cheers,
K
So I can’t buy Floppy until this is resolved? Crap 
[HELP WITH A USE CASE]
Hi… I am pretty sure Floppy can do this but don’t know where to start. I am rebuilding part of an app that shows estimated and actual time worked on tasks. The data things are Task, Person, TaskPerson, and Time. Time is of types Actual or Estimate. Tasks have a list of dates and Time has dates and hours. Tracking actual time against TaskPerson is pretty straight forward as a user enters the hours worked on each TaskPerson. It can then calculate the remaining hours for the TaskPerson, and divide them by the number of remaining days from the list of dates.
But for estimated time by day is a bit trickier. The original design was to use Floppy to iterate a new Time (estimate) for each day in the Task’s list of dates and calculate the average number of hours per day remaining. Since these data are changing all the time, I would like a solution that doesn’t store the estimate data as a thing.
So now I would like to explore if Floppy can store the list of dates and average hours per day remaining so that I can use it in some charts. I could step through all the TaskPerson for a Person and store a key for each date but I don’t know how to “build a table” in Floppy that I can also store the average hours for each date. If this is possible, then I could group by day and see the total number of remaining hours for all TaskPerson by date.
Can anyone help to steer me in the right direction?
Hello everyone,
I’m trying again.
Does anyone know if For worfkow: Remove Keys Floppy. Is it possible to remove several keys on the same action instead of creating one action per key?
thanks
Hey @keith you may be already be aware of this but Floppy showing up as deprecated now:
Hey @keith , I just tried to install it on a new app but the plugin is not showing up on the plugins search , and it says its deprecated and needs an update.
Any other way to install it?
Thanks
If youre starting fresh you can duplicate an app that has it and it’ll come with it. Not ideal but I’m sure Keith has to spend some time getting the code to work with the new Node. We all need to be patient.
Yep, patience is the watchword, but note that I’m making progress:
UPDATE TIME 
: FLOPPY has been updated to version 1.10.1. The new version brings the server-side actions included in FLOPPY up to the new Bubble server-side API (version 4) and so you should find that, once again, it is installable from your apps or by visiting its plugin page:
Please note that while I’ve tested the SSAs as best I can, as with any new version, there may be bugs and you should test in your application before deploying. If you notice any issues, please report them here in the thread and @ me. If something should cause a problem, you can roll back to version 1.9.56 in the meantime.
The updated server-side actions are:
The other SSAs (which didn’t require any changes to work with the v4 API) and client-side actions are not updated in this version. Note that the updated SSAs do not have any new functionality, they have just been updated to use the new asynchronous server-side API.
On the element plugin side, there are also no changes over the previous 1.9.56 versions, with the exception of Floppy Expression Watcher where I fixed a small annoyance. (In FEW, it’s possible - perhaps even common - for its input lists to be undefined when it’s first instantiated in the page, causing a non-critical error to be reported in the console. This has been fixed. This is actually possible with other plugins, but not as common and I’ll propagate that improvement to other elements in the near future.)
Note on experimental plugin: I also updated (unsuccessfully thus far) the experimental and not-actually-for-your-use “Floppy Bulk Create Things SSA”. While I may make it work in the future, that plugin is simply a proof-of-concept for an idea that isn’t actually a good idea. Rather than delete it, however, I’ve left it around as a possible future feature. Basically, you are not supposed to use that plugin and it currently doesn’t function properly.
@Dimo, while the Remove Keys action for Floppy only supports removal of two keys at a time (and is designed, of course, for removing the two specific scalar and list keys that a particular Floppy is managing, even though you can also use it to remove arbitrary keys by name), there is also a “Clear All Keys” Floppy action. However, that action removes all keys in the specified storage space, not just keys that Floppy might have created.
Another alternative is to drop a Floppy Reader element on your page which can manage 6 scalar and 6 list keys that you name. You wouldn’t have to use it for anything else, but its Remove Keys action would let you remove any of those 6 scalar and list keys with one action.
This would actually be a good idea for a new action. While the interfaces we can build in the Bubble plugin API are pretty limited, there is a “Key/Value” pair interface element in Actions that the programmer user can actually click to create an unlimited/arbitrary number of entries. I think the reason I didn’t implement a “Remove” action like that is that it might be slightly confusing, but I can see the use. Another idea would be to add a large text field to the remove dialog that lets you enter a comma-delimited string of key names that you’d like to remove (or a separate action).
Anyway, I’m noting this as an interesting idea for a future update. Thanks for using Floppy!
