I am working on a wedding planning website where I am trying to create a spreadsheet for each user on my website, which they can edit to create their guestlists. I was really happy to find sheetnode, because it fulfilled all my requirements of importing/exporting spreadsheets, integration with views/cck etc.

However, I am facing some issues:
- I am not able to view the spreadsheet on Firefox on my Mac. It shows up on my macbook, but does not show up on macbook pro on FF. It works like a charm on Safari.
- I am not able to save the data in the spreadsheet when I am logged on with a non admin account.

I am wondering if these are the bugs with the application or if that is something in development. Also, I am trying to figure out when the development of sheetnode will be completed so that I can plan the timeline of my project accordingly as I would really like to use it for my website.

I would like to do the following things with sheetnode:
- Create a template for a guestlist with the following fields: Name of the guest, Address, Out of town, Events invited for, RSVP, Gift, Thank You notes sent.
- I would like to filter the guestlist based on Events invited for, Out of town, RSVP, Thank You notes sent.
- I would like to integrate cck with it so that I can create drop downs (so that users can easily filter) in the spreadsheet. This way there are no spelling errors if users are entering the data themselves.
- I would also like to create a view of the guestlist so that the users can easily print it.

Please let me know if these features will be available and how long it will take for them to be developed.

Comments

infojunkie’s picture

infojunkie
Location Vancouver
commented
Status: Active » Closed (won't fix)

Hello, thanks for your report.

To increase the chances of me or any module maintainer addressing your issues to closure, it is best to file one report per issue. In your case, you would file 2 bug reports and a number of support or feature requests.

Note that I will not implement features that are not generalizable beyond what you specifically need for your own site. Also, when you make a feature request, I cannot guarantee a delivery timeline as I work on this module (and many others) whenever I can. There are periods where I advance very rapidly, and other periods where I have no time. Furthermore, I might not share your sense of urgency to get a specific feature implemented. I'm sure you are aware that such is the nature of open source development.

That said, if you're willing to *sponsor* some of the features or fixes that you need to meet a specific deadline on your end, then I will make time in my *professional* schedule to accommodate you. Feel free to contact me privately to discuss the details of such an engagement.

Finally, please note that no piece of software is ever bug-free. Whoever claims the contrary is a liar or an ignorant.

Cheers,
Karim

nehagupt’s picture

nehagupt commented

Hi Karim,

Thanks for your prompt reply. I certainly don't expect your development to happen according to my deadlines. However, I was just trying to gauge and see if you had a timeline for this project. I also don't expect you to create features specific to my needs, however was just trying to get an idea if what was on the project page for sheetnode was fully implemented or still under development (for ex. integration with views and cck).

I am just looking for some pointers/ documentation to use the sheetnode module, and for developers/users to point me to the right direction. If you know of a community of users who are trying to work with sheetnode, then I would love to connect with them.

Again thanks for your reply,
Neha

infojunkie’s picture

infojunkie
Location Vancouver
commented

The roadmap on the project page is supposed to reflect the current state of the project. Whatever's marked as "done" should be functional, whatever's marked as "in progress" should sort-of-work, and everything else hasn't been implemented yet. Obviously, features that are not mentioned at all don't exist. Specifically, the CCK-related features that you mention do not exist today.

As for documentation/pointers, that's what support requests are for! Because this module is fairly new, the community around it is almost non-existent. I am doing all the supporting for the time being. That's why I was asking that you split the issues up - they'll be easier to track.