PHP Portals... will it....

[Nossie]

hehe my hat is off to you kind sir  



good luck !!

[AndyMan1]

well, I just submitted a call out to the PostNuke community asking for assistance with working on a PostYabb..or a quite better name than that

If they put it up on the main page, we will hopefully get some coders down here to get involved, and maybe work with matt some. After all, they built on top of PHP:Nuke, so they'd be able to offer some assistance, wether or not its the PHP and not Post version.

With even more crossed fingers comes the wish of someone else taking on a module job, maybe even compatible with both PHP and Postnuke.

Anyway, kudos to you matt for doing what your doing. I'm sticking with my lovable cuddly PN, but im sure others will definantly appreciate what you are doing. Do you think i said doing enough yet? Doing Doing Doing Doing Doing!!

[Shindou Hikaru]

It's only 3 people. Me, Matt, and Omario. So coders is a large word.

If I have time, I might help. I also have some other projects to work on once YuKE is finished.

[Shoeb Omar]

yeah and u ccant really call me a coder so....

yeah u can call me a coder btw

[tore-]

i preffer postnuke, but if phpnuke is the thing ill use it

[tore-]

Ive just made an mod for my board, a recent news mod, it will get the subject with link ordered by date and print it out. If this is something you would like to get the source to just say so.

[Jeff Lewis]

News.php already does that in 1.3

[Shindou Hikaru]

Jeff, did you get my latest instant message?

[Jeff Lewis]

No...I guess not.

[tore-]

News.php already does that in 1.3

oh, well, i use News.php two places, one for each thing, full info with content of thread and so on, and then just the subject field.

[AnalogDuck]

Uhhh, a message to the YaBBSE community moderators:

I recommend something that seems to be overlooked.  I think this thread ought to be broken into three or more seperate threads.

If non-YaBBSE developers are going to be developing YaBBSE modules for various CMS's, why not lock this thread down - along with all of it's silly arguments over who's CMS is the best CMS - and instead start new, unique threads of discussion for development of each YaBBSE mod; for postnuke, phpnuke, XOOPS, myPHPnuke, phpwebsite, etc.

Let each group cough up their own developers.  Don't screw with the origonal YaBBSE code or direction at all.  YaBBSE is a tight project with good focus and momentum.  These are very sought after qualities you should always be wary of abondoning.  If phpnuke peoples are willing to develop the integration, and so are XOOPS peoples, good for them.  PostNukers - you want your PostYaBB, go for it.  A good start would be to take your postnuke discussion elsewhere, to another thread.  The bickering over who's CMS should be the lucky winner of YaBBSE integration isn't doing you a bit of progress.

Break up and make seperate camps.  I don't think there's any reason everyone needs to agree on this one.

Obviously peoples who have been "in bed" with their CMS for a good length of time are not just going to up and leave all of their hard work and migrate massive amounts of content to a new CMS just for the sake of YaBBSE integration, so you should all stop being so selfish as to try and convince everyone else your CMS is more deserving.


"My CMS can can kick your CMS' butt!"

[Matt Siegman]

Who wants to write an installer for YuKE?  any volunteers? we kinda need some help

BTW: most of the changing code is the YaBB code

[Jeff Lewis]

Which is what it should be if you're making the CMS the central part of a site...

Analogduck, these guys making yuke will have a combined SE and phpNuke system under GPL if you can make use of that...

[tore-]

Like an installer manual or? if so i can do it

[Shoeb Omar]

my jobs to write sa manual