I guess having low expectations is one way to avoid disappointment, just as answering a question with a question is one way to avoid answering the question. Unfortunately, it doesn't accomplish much in the way of speeding delivery or getting an answer for the original question...
For the remaining optimists willing to wait a few months (or less), here's a current screenshot of the registration options:
Joined: Aug 30, 2005 Posts: 3186 Location: near Albany NY
Posted:
Wed Jun 11, 2008 5:41 pm
I spent the day today in the trenches with Kevin's new distribution. From a features point of view Ravennuke Cnbya (or whatever it gets called) is going to be a knockout. But from a details point of view, there are a ton of "notice" type errors. Constants not defined, constants already defined, a million things wrong -- or perhaps a thousand. But a lot. Perhaps I'm wrong and if so, correct me, but if you run cnbya output through the W3c validator I'd expect you will see lots of errors. By the time it hits the streets as part of RN there will be none.
I just wish developers would develop with error reporting turned up all the way.
Still, you can see a listing of all your users right on the screen. You can search without going thru the funky ya_dropdown. And there's lots of configuration options that should suit 99% of people's needs. Just be a bit patient cause this will take some time.
Before committing RNYA to SVN the first time, I used the HTML validator to successfully test most, if not all, functions using the serial option (i.e. both Tidy from W3C and SGML Parser). By my count, less than 200 lines were changed today, including 2 changes that broke compliance. Some of the changes were corrections to changes made yesterday, and most of the changes would not affect compliance, though they do comply with RN standards.
I didn't even look at error reporting yet because I wanted to get it into SVN so everyone on the team could participate in developing this complex change. It's great that several will be able to contribute to making sure this addition to RN meets RN's high standards. But as we are in the middle of development, posts like this are not only unhelpful, but counterproductive because they waste valuable time requiring responses like this.
I'm sure you were frustrated with errors only evident with error reporting on, and I definitely appreciate the changes and your many excellent contributions. Let's keep our eyes on the ball - and development discussions in SVN - and focus on the most valuable efforts to improve RN.
Joined: Aug 30, 2005 Posts: 3186 Location: near Albany NY
Posted:
Wed Jun 11, 2008 8:27 pm
In the context of the Ravennuke community discussion generally I just wanted people to know that incorporating CNBYA into Ravennuke is not just a matter of plugging something in and it works. I apologize if my efforts to express that wasted time. I'm totally onboard with your recommended approach from here on out.
Thanks, Frank. You are absolutely correct - we could simply plug in something and hope that it works, but that would most likely result in broken and / or insecure sites.
A significant number of issues identified using error reporting were resolved last night, and though some may still remain, I think you will see significant improvement when checking today. There were a few functions I didn't test (e.g. registration, password reset requests), but hopefully will get these done this week so we can focus on functional improvements.
There's no need for any of you to justify yourselves, we understand its not finished and still in beta stage, and bound to be a lot of issues hence the beta stage, your all doing a great job keep it up
Here's an update (very rough, but you can see the direction) showing inline validation of the user name, email address and password strength:
There are obviously some improvements to be made for appearance (e.g. changing the color of the field to indicate an error), as well as some associated changes / correction and language, etc. But the cool thing is that the inline user name and email validations use the same functions used when submitting the form. Nice!
We'll also be adding validations for required fields, and maybe more... Of course, this will be configurable for those who don't want to use them.
By the way, the inline validations use a cool approach that waits until the user stops typing before validating - which should reduce server load. Sweet!
what are you using for validation, as ive been playing eith the mootools framework and must say i think its a definate foot forward for the future of nuke.Its easy to program and powerful even if your not an expert js programmer.
here's an example.....
it uses the random function in php just to give you an e.g. so click in the box and tab out and keep doing it to the different effects
Only registered users can see links on this board! Get registered or login to the forums!
We reviewed several JS libraries / frameworks and selected jquery. There is a powerful validation plugin for jquery, and we are enhancing that with some additional integration for RN.
Definitely agree - it nice to see these capabilities for Nuke.
argh ok, good job, one thing i have noticed is even though mootools is extremely easy to program the mootools forum was not very helpful, although being a member seems to raise your expectations
Though there are many similarities among the JS libraries / frameworks (we looked at prototype / scriptaculous, jquery, mootools, dojo, YUI), support (not just forums / groups, but also adoption and available plugins / enhancements) was a key differentiator for jquery. Along with easy of use, support could change over time (as it does and has with CMS applications), of course. Also, I could see some uses for ExtJS in addition to one of the aforementioned libraries, but it just doesn't have some of the basic stuff we need, even though it has some really great advanced functions.
There are plenty of discussions, comparisons, etc. about this subject, and I do not wish to relive that here.
Only registered users can see links on this board! Get registered or login to the forums!
seems out of date as jquery does have tree view support, for example, and it's probably not accurate to compare prototype without scriptaculous, but does highlight some of the factors we considered:
* Browser compatibility
* Ease of use
* Maturity and Support
* Overall quality
* Documentation
* AJAX capabilities and handling (XML, JSON)
* DOM manipulation
* widgets: integrate datetime picker, autocomplete field, tabber interface, table sortable by any column field.
In addition, one very important factor this doesn't consider is license. We need to have something that can work with the GPL license RN uses. jQuery uses both the MIT and GPL license, as do most of its plugins.
Only registered users can see links on this board! Get registered or login to the forums!
Quote:
Hello all, unfortunately it has been quite a while since you have heard from me on CNB Your Account.
My current activities do not allow me to put the effort in the project that it deserves, being the #1 Your Account replacement for PHPNuke.
Therefore I have decided to hand over the project to some people that are willing to develop it further and invest time into a solid version controlled (SVN) codebase that will help thousands of PHPNuke admins all over the world.
Before I will transfer the ownership I will put out a full public final release of what I have.
I will make sure it also runs on RavenNuke 2.10, which is the current most reliable edition of PHPNuke available.
You have my solemn promise this time that you this will happen before the 1st of august (2008).
I think you will understand that with all my hours invested in this piece of code I would really like to at least finally release a working version of it to the public.
It is with some pain in my heart that I will be going stop my part of this wonderful project. But I acknowledge that it it much better for the community to be able to move on, and be blessed with actual releases
With kind regards,
Richard van Oosterhout (menelaos61)
Only registered users can see links on this board! Get registered or login to the forums!
All of you who didn't register thusfar can go to
Only registered users can see links on this board! Get registered or login to the forums!
to register an account, and you will be the first to actually receive the 'CNB Your Account 5.0 Public Beta1' when I will release it (before august 1st!) AND: I could use some of your help to test-drive my last and final release so that I may leave the scene with the honor of a nice working public release of code. Will you help me with that?
It is scheduled for release 8/15/2008. We may be releasing sooner but that is our scheduled release date.
almost 2 weeks passed the scheduled release date, but ther is no information about neihter from the CNBYA (or RN Your Account) nor RavenNuke 2.3
it would be appreciated if someone would told us what's going on.
Joined: Aug 27, 2002 Posts: 16986 Location: Kansas
Posted:
Thu Aug 28, 2008 8:08 am
First of all, that was written on 6/19/2008. Much can change in 2 months and we don't go back through the forums and modify posts as that is not feasible.
"What is going on?"
On 8/3/2008 we posted a message on the home page and in the forum Announcements stating we needed testers and that we were doing a more formal QA Process. While we did not explicitly state when we would be releasing v2.3 it is pretty obvious that we don't intend on releasing it until we are satisfied with the product. That is why there has been no further date published. We publish dates as an expectation/courtesy and we are usually close when we finally publish.
We will release v2.3 when we are satisfied that it meets our QA standards. Look for it some time in September as of our expectations right now.
View next topic View previous topic
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
![[Valid RSS]](http://www.ravenphpscripts.com/images/valid-rss.png "Validate my RSS feed"){kind=small}
:: 
::
