We should definitely compare notes. I have been working extensively with the Store module for months and have resolved many similar issues. When I joined the Store team, I really tried hard to get it posted with the newest release of DotNetNuke. I had less than a week to become organized and less than 24 hours notice about the release. It was just not possible.

Note that there is quite a difference between fixing code to make it work for your own needs and maintaining code that will be used by the community.

For example, I am finding that understanding the bug reports and locating the real problem takes much more time than actually fixing it. Trying to manage the huge list of requests can be overwhelming when many are duplicates and/or slight variations of other requests. Documenting my work is very important and also very time consuming. Testing changes for multiple versions also requires thought and effort.

Finally, you have to try your best to balance the needs of the group compared to the needs of the individual.

We realize that there is much interest in the Store module and we share your enthusiasm.

Thanks for the kind words.

Amit,

Of course we would be glad to share your ideas and techniques on the forum, especially when we are duplicating the effort.

For example, the first things I modified for my own needs were…

1)       Additional Tokens (breaking up the Title)

2)       Multilevel Categories

3)       Category Sort Order (alphabetical and order)

4)       Import/Export of Products and Categories

5)       HTML Templates for email messages

6)       Featured Items and Clearance Items (by Category)

7)       Purchase Order Payment Provider

8)       Simple Payment Provider

9)       Product Searching

10)   Express Item Entry

About two weeks ago I was asked to join the team. My job is get version 1.1.0 “out the door” that works “out of the box”.

I have been concentrating on the part no one else likes - the bugs and broken parts. From my work, the forums and Gemini, I am trying my best to add enhancements as long as they don’t break existing code. At the same time I am looking for ways to improve the module with templates, procedures, standards and proper documentation.

1) How would you handle taxes for version 1.1.0?

2) Do you fix the current tax user interface and system or dump the entire mechanism in favor of a process that will also work for other countries?

3) Should we be working on Reviews or simply ignore/remove them until they work as requested?

4) Do we have to refactor the original design to incorporate the many new requests for changes?

When we missed the deadline for DotNetNuke 4.3.3 (about 10 days ago) we decided to organize a stable and usable release.

When it rains it pours.