which one will it be encrypted in cos more cgi could strain my server

seeing how ubb is perl, id say perl.

some of each... depends on what's logical for the task.

what brad said is what i thought

Like Allen said, each can do things differently. It depends.

In my opinion, I always believed that since the UBB is cgi, the portal should be cgi.

Most parts will be, it still depends on what's logical

I have mixed opinions on this myself since I am learning to love PHP but Brad had a good suggestion earlier about being able to create .cgi pages from within the CP and it seems to me that this would also allow us to use the styles and variables and of course recent visitors etc. I realize that this would increase the overall resources used but if a person is surfing through the external .cgi then they won't be on the summary or forum pages at the same time so it will still be single sessions.

I think the thing I would like the most as far as appearance and ease of design change would be to have the $TBT and $TBB available. Allen has done this with hiw PHP styles hack.

I think more than anything, ease of development/ server load/ etc would be the prime considerations. Simple things like styles can be written out into a vars file and read with either perl or php. Recent visitors can be done in perl or php, ubb handles both. And it all can be done from the cp in either php or perl... Where possible, things need to be written to a file and included that way, so the front page is not generated dynamically with each visit. I believe "latest threads" has a mode like that.

Well I'd like it to be as compaitiable as possible with the UBB, like changing settings in the CP.

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by AllenAyres:
some of each... depends on what's logical for the task.</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">why not have a Perl & a PHP version? i think that would be the most logical option. some ppl can't run PHP b/c of their hosts, etc.

That would make development twice as long, with two sets of bugs to track. It would be too difficult.

I agree, we need a goal and a plan. As quickly as the versions for UBB come out we may have a hard time keeping up otherwise.

Chances are it will use php as the "delivery" (think ubb accel) and perl as the backend, (think everything else). I am guessing its being discussed, but keeping server load down is a priority (or it should be).

Greg, are you part of the dev team?

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by Greg Hard:
Chances are it will use php as the "delivery" (think ubb accel) and perl as the backend, (think everything else). I am guessing its being discussed, but keeping server load down is a priority (or it should be).</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">In other words, the same as the UBB with an accelarator on?

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by Dave2:

That would make development twice as long, with two sets of bugs to track. It would be too difficult.</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">there could be two seperate dev teams and two seperate source trees, so yeah, there would be two seperate bug trackers also.

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by TheX:
Greg, are you part of the dev team?</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">Was that retorical? Not as of yet, no.
However, I do know the standards for a portal running off UBB's core files, and plan to assist in any manner i can.

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by Greg Hard:
</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by TheX:
Greg, are you part of the dev team?</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">Was that retorical? Not as of yet, no.
However, I do know the standards for a portal running off UBB's core files, and plan to assist in any manner i can.</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">The question was more of a "I hope he says yes" kind of thing. What will it take to make you part of the dev team?

Ask me? Bribe me with cookies?

Ahhh, cookies works for me too...As soon as I find out the official way these things work I'll move on it. Allen? Bookie? Anyone?

I usually send them here first:

http://www.ubbdev.com/ubbcgi/ultimatebb.cgi?ubb=clearcookies

then have them log back in, voila! fresh cookies

Hahaha, thanks Allen. I of course clicked that link and had no clue what my password was sooooo...now I know what it is. What about the official recruiting procedures?

That would be up to you and Bookie, I think the greatest number of skilled workers up front the better - once the to-do list is set, you guys can start dividing up the tasks to be done.

Thanks allen.

np, and pssstt.. check your pm's occasionally

I think having too much CGI on my server would kill it aswell, I'd say we should really think about PHP, as its really fast and also has the ability to do flat files as well as Databases.

In this case, i'd definately pick PHP as it will be perfect in the long run.

And you Could create .php pages from the Admin CP if you wish. Thats just up to the Coder(Developers) to add as a feature.

Just my $0.02
Xavier

hehehe, untill we use cgi, we will be DOS, exactly it have a bomb script, this script bomb at ultimate.cgi , althought we use accelator to export ultimatebb.php it also can't be visit, when UBB.classic is bomb, no one can visit forum, for that reason I leave UBB.classic to use invisionboard, it's free and speed

I think UBB.classic should have changed to use php and mySQL, database is text can allow hacker use local exploit to get pass admin and member.

I like the cp of UBB.classic best, it so easy and have much funtion.

this is a test

um.. what exactly are we testing mate?

Um..i've asked for this to happen, but i got the reply of "Use UBBThreads it supports php/MySQL" so yeap.

tho i must say, UBB.Classic's CP area is wonderfully layed out

[spam deleted]

[spam deleted]

Thats my $0.02
Xavier

You mean .01 this is not a 'spam the site for another forum script' thread - you'll be shown the door if it's done again. You'll find the same policy on the support sites for the 2 scripts you named.

Thanks for understanding