cleanfriends
I have a questions....so if the extensions or mods can not contain bug fixes only new functionality, does that mean Boonex is actually going to start producing updates ie bug fixes on a more timely manner, not waiting for a new version for simple things to be fixed. I understand the need to adhere to launch dates and getting new versions out out on time, but they dont do us a whole lot of good if all you do is put out a new version number FILLED with more and more bugs, that JUST got fixed by the see more same faithful contributors your now going to run off with this 'false bravado' of a safe guard made to make the buyers feel more confident, but why not just fix things your self BEFORE YOU LAUNCH A NEW SCRIPT and stop passing on the problems to us then creating roadblocks. Why not just answer your expertzzz account and start taking action on the fraudulent sellers, dont punish the ones you have left, because from the way it looks in the forums, they're not going to stick around very long if you keep this up. IMO Josh
DosDawg
i 100% completely agree with you on this josh. i have stated that more than my fair share of times. that the script should not be released, until it has been evident that the bugs and kinks are worked out. i participated in php-nuke, e107, development, and never were there as many bugs, nor releases as with boonex's dolphin. there is no need to release a version of the version you have out is functional. there should be a core system, from that core, you would then program plugins, or mods call see more it what you want to call it Fins or snouts for all i care, but the core system should remain the same, and the code convention that is submitted should conform to a standard.

if there are new "CORE" functionalities, then by all means, release a new core version. but the site shouldnt blow up, and users shouldnt be forced into updating.

just my 2pence

later,
DosDawg
Vespen
Totaly agreed. The new extension requirements is too strictly, imho. From the other side i think that selling custom updates is smth wrong... i prefer to buy good featured extensions. Maybe let ppl to upload Dolphin code-changes for Free only following all other requirements? Another special case is languages, i don't realy understand why is Dolphin base complectation is Eng only?? I don't like selling langs too, especialy knowing that i definetly will have to edit the translation myself to fit my see more purpose...
lp897
I agree it is mandatory to have an stable core version without any bug and issues before to launch new dolphin versions that carry out with them the same unsolved bugs. for example what is "random quotes" ? this is a feature without support nobody knows how to implement it and nobody from dolphin side has the right answer. sowhy did you create this feature? or why did you never fix it (because this is an old feature).... whats going on with the subscription module.. something like that... see more I think that you have to focus on to have a powerful and stable product, that means that you have to be sure that each current features should be work without any problem before to launch new versions or something like that.

I have ad-free v.6.1.1....
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.043830871582031