Extensions Requirements

Andrew Boon posted 22nd of May 2008 in . 21 comments.

From now on all submitted extensions should comply with the Extensions Requirements. We're trying to protect customers from junk and problems here, so if you have any comments or suggestions - share.

You, potential buyers, may want to take a close look at that file, for it will define what you'll be buying.

 
Comments
·Oldest
·Top
Please login to post a comment.
webid0001
Well done! Hope the bo-team will got the time to check all requirements on EVERY extension. But you can be sure, this is the only way to sort out problems for the future - these people who are angry now - make'd customers angry before.
gkcgautam
Thats a good move. Next good step can be release of a free/paid extension by Boonex team which can serve as a demo for the developers. ( Best would be releasing it for free )
Andrew Boon
Yeah, good idea indeed. We'll work on that.
praveenkv1988
I think the code convention is not mandatory. As every one have their own way of writing codes.
Andrew Boon
There's a good reason for Coding Convention being required. When someone buys Extensions, especially many of them - they would want to have readable code, written similarly across the entire website.

Life's a little bit more complicated for developers now, but at the end of the day everyone should benefit. Let's concentrate on making customer happy now - and success will follow.
DosDawg
praveenky,
when you are dealing with an application on this scale, it is important that a convention be standardized, and every programmer adhere to it. i dont think they were so far reaching in asking that the code conform to a standard. otherwise you end up with so many bugs, created from malfunctions of communicating between the mods and the core.

good luck,
DosDawg
sammie
does that mean we have to now pay someone to code chat ADMIN and MODERATOR rights?

or is boonex gonna address this issue and reply to it for once ?
DosDawg
sammie,
i got a message from rayz yesterday, saying he would be releasing a patch that would have the admin back on the AV chat. so it is being addressed. hope this helps you out.

later,
DosDawg
zmoos
I think this is great, and I believe the Code Convention is also very important. It helps to eliminate conflicts, improves consistancy, and will make the extensions easier to moderate and ultimately safer and better supported for the webmasters.
luis6620
Dolphin with Google

I do not understand English, and I'm just knowing Dolphin, but I am keen to be aware and contribute my experiences.

Right now I see that Dolphin is not read by google, the titles of the post are not accessible.

I write several other blogs and get many visitors just writing, google is responsible for show, so I have many stakeholders to my business without having to speak directly to people.

Google reads the titles of blogs as a post, so I just read it once, the other see more titles always appear to google as post does not recognize the different titles that I give to my blog post.

The same happens with markers AddThis, I could not read the title of the post. It is very good Dolphin, was overcome to achieve much, I give you a hug to creators.
silly question: is anyone supporting your products these days?

contributors forumz are dead, extension devs are not quite quick in answering the question. boonex account in expertzzz is totally silent.

stupid question: what is the transition period (to a working/stable/dependable environment & service)? one month? one year? never?
DosDawg
ciprian,
this is an all new system, and moderators are being incorporated into this new system. the contributors are trickling in, and extensions are being submitted. as with anything new, we all have to understand the rules in order to play the game. the ground rules have been laid, and those of us who have the desire to support this community are working on getting our ducks in a row so we can escalate our membership level.

later,
DosDawg
rogerbr9999
I sell translation for dolphin in lang-???.php file and work fine ... It isn´t in sql but work fine for my clients ...

http://www.rela2.senior.eti.br
LeonidS
But if buyer will try to change some little thing in your lang file it will be fully rest to default...
Stuart038
Does this mean from now on all code/mods that conform to these specifications will work on all future releases of Dolphin? Good idea by the way.
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....
aatkco
Please Replace Imagemagick With Any Service Which Is Already Located In The Servers By Default Because My Hosting Provider Dosen't Support Adding New Scripts To Server ( Security Reasons )
 
 
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.056483030319214