This is one example of not following through...

Remember this?

This saviour to the forums; another BoonEx pipe dream or what?

http://www.boonex.com/n/meet-markus-a-new-master-bosun-and-unity-editor

ugg ?!

Yup. I have not seen anything either.

 not one..

It's true, "we" are BoonEx, it's like those guys don't even exist, except to tease with releases.

I have never seen such ignorance as in ignoring customers as this company, EVER!

The idea of "reviewing Products at BoonEx Market" is good but assigning the task to a single volunteer, in this case Markus, turned out to be a poor decision. Reviewing modules might better be put into the hands of several "persistent" and "consistent" people using the Boonex Forums... such as newton27, mscott, geek_girl and deano92964... with the agreement that they be allowed to advertise their Dolphin-related services at the bottom of each review, if they so choose.  

There is one guy named Igor he is pretty great. He has helped me in the past when no one else could.

This is my "favourite".

Something epic is happening...BoonEx documentation is going to be great....Any ideas or suggestions on what else we could do to improve Boonex documentation are most welcome.

http://www.boonex.com/n/the-big-documentation-overhaul

So what is the opinion on the following statement?

What Has Been Already Done

- We re-compiled all our FAQ pages and united them into one big FAQ page with appropriate sections.

- Beginners Guide is no joke anymore. Now it's an actual guide with basic introductory information. 

- Getting Started section now boasts a few new documents, explaining Mobile Apps, Licenses, Motives, etc.

- Installing Dolphin document is reworked into a not-so-intimidating, yet not-so-simple-stupid manual.

- Troubleshooter has been updated.

- There are many other small changes, improvements and fixes that should make documentation easier to read.

What Needs To Be Done

- Dolphin FAQ For End-Users needs to be amended and updated. This document is for public use by any Dolphin web-master. We create it together as a knowledge-base for supporting members of Dolphin community sites. 

- Administration Guide needs to be updated for Dolphin 7.1 renewed admin panel and settings. 

- Community Tutorials require fresh screenshots and updated instructions for Dolphin 7.1.

All these pages are based on Trac Wiki. Advanced and Premium Members can contribute and we seriously need your helping hand! If you take a look at any of our support documents and think that there's something you could do to improve them - please login to Trac and type your gems in. Thank you!

It appears that, other than the section "How to make automatic upgrade script for module", very little has been done to updated the online documentation during the last 6 months.  And it appears the job of updating documentation has been left to the owner Andrew Boon... who I imagine often gets busy with other matters.  Such a important task should be a long-term part-time *paid* position within the Boonex Team... not treated like something that only needs to be "tweaked" occasionally.

 could not have been stated any better.

 Well, after four years here, I have just about every module in the market from clients that I work for.

NONE but a few are worth anything, most are just trash and useless.

I don't think I would have any good input, well a few, for most modules. I already have seen how they "don't" work and have to fix them for the client, when the module creator should have to do this.

As I stated, it's so *ucked up.

Totally agree... I have access to over 50 modules and had to tweak many to get them working reasonably well.  One lesson that I learned a bit late was that many modules are simple variations of one of the free modules included in the default install.  It would be good (for buyers) if modules were objectively reviewed... to expose those that work incorrectly and those that are a waste of money.  One of the best skills a Dolphin site developer can learn is how to clone a default module to create a variation that they need specifically for their site, i.e. so they can run both the default and the clone version at the same time.

 I'm looking at around 200> modules.

The gig with Markus didn't work unfortunately. No sync. Sorry. We're looking for better options.

As for the documentation - we've done quite a bit of improvement and reorg since that statement and more will be done once we come out with the next update. 

Andrew, here is an idea, how about hiring some of the module developers here to fix the bugs or broken features of Dolphin?  Deano just fixed the service menu builder that Boonex released half implemented; I suggest you offer to buy the code from him and fix the service menu since I doubt that it will be fixed by anyone in-house.  Why Boonex would release features that are only half implemented is beyond me but at least get some developers on the job to finish them, or fix the bugs that have been around forever.

 Thank you for stopping by and informing us; you do read these...

 Forget the next update for now, none of us are begging for an update; we want documentation (I don't but newbies do) and a good market that can be trusted.

I second Newton on that. Dolphin will not be that more appealing with next update. 

Please get the support up through better documentation and friendly staff. Have the best support among the competition and you'll get more Free trial people converting to paid license. You need a minimal amount of people converting to get a nice ROI on better support.

I agree, module developers and site admins need some time to update modules and sites first.

 100% thumbs up on this, please listen to us.

We are pleased with the current version.

We want better working modules!

I'm updating a site now that the vendor is lagging on an update keeping me and my client hanging.

I'm not out to point a finger, but they need to get off their ass and update their modules.

I've lost 50% of my clients because they cannot move on with patches because of old modules.

Well, a lot of things in BoonEx are tied to an "update" in one way or another. Thus,  any talk about the next update is not necessarily driven by desire of impressing everyone with new features. For example, Market is closely tied to Dolphin modules system, templates handling, languages implementation, etc. So, for some of the Market improvements, an updated Dolphin is required. Documentation is also often version specific, and when we know that a certain aspect is undergoing a major overhaul, we just can't put too much time into documenting the current implementation. This is, of course, a vicious circle, and we now understand that Dolphin platform has to be handled not as a one unit, but rather as an ecosystem of different parts that need their own updates, documentation files and more version-flexible modules. That's what we are working on - creating a more stable, flowing tie-in between Dolphin and Market to ensure that clients and developers don't get burned with every version update. We already see that we can build a predictable flow for both.

 Thanks Andrew for the reply, we are working hard here for you and BoonEx, I know getting the market up to what we need will be a very long process. I'm (clients) are very happy with 7.1.4, speed, almost no bugs, I know we will continue to upgrade to 8 eventually, which I personally cannot wait for it, but clients are not.

We are going to fast, let's take it down some and let "us" catch up, please.