PostNuke
Flexible Content Management System
News
One Step Closer to .8: Download the Latest .76 Release
Summary of Main Changes
Further cleaning of HTML
- pn-normal custom class removed in favor of styling of block level element using CSS
- pn-pagetitle class replaced by use of h1 tag
- pn-title class replaced by use of h2 tag
- all fake lists created using middot's replaced with proper lists
Simplication of non API compliant links
op=modload & file=index are the defaults so these are removed from all links
New printer (Xanthia) theme
Enables printable view of any page
Removal of NS- prefix on all modules
Updated modules:
Admin_Messages, Modules, Blocks, Permissions, Groups, legal, Censor, Messages, Ephemerids, Quotes, Autolinks, AvantGo, Credits, Members_List, Ratings & Admin
Modules updated for full API compliance and templated output
- New modules
- Sniffer; Detects browser and browser capabilities using phpSniff (by Roger Raymond)
- RSS; Replaces dated feed handling with an xml based parser (magpie rss)
Bug fixes
- Xanthia - many fixes since original release
- Mailer (added support for additional headers, bcc's & cc's), fixed sending to multiple addresses.
New features in core
- Modules can now be referenced using an 'alias' via the module display name setting.
- Default start function type, function name & parameters to the function can be defined. Note: API compliant modules only.
- Standard database connection error moved to 'template' in includes/templates.
- Ability to turn the site off for maintainence (access to provided via permissions setting).
- Ability to set what function type, function name and any parameters for the start page (API compliant modules only)
New features in modules (in addition to API compliance and templated output)
Modules-module
- filter by letter, state
- graphical indicatator of state
- detection of change of type, admin & user capability
- ability to recover from missing files state
Blocks
- graphical indicatator of state
- ability to define each block as collaspable (credit to Mark Heldstab)
- ability to define each blocks' default collapseable state (credit to Mark Heldstab)
Others
- Groups - ability to add multiple users to a group in one go
- legal - added template accessibility report (thanks to http://diveintoaccessibility.org)
- Censor - added transfrom hook for censor module (supercedes pnVarCensor API - maintained for backwards compatability)
- Admin - added ability to split modules into categories, the categories view are skinable via a single stylesheet
- Credits - support for multiple module contacts via comma seperated values in pnversion.php
- Smarty updated to v2.6.6
- ADODB updated to v4.5.4
Remember, this build is a release candidate and is not recommended for production sites. Please report any bugs to the bug tracker found on the "Development" block on every PostNuke.com page.
Download details
Worm hijacks open source MySQL database
Security experts have warned that thousands of MySQL servers around the world could be press-ganged into launching a denial-of-service attack that could bring down the Web site of a company the size of Microsoft.
A worm, dubbed MySpool by security organisation SANS, is spreading rapidly amongst the MySQL user base. It automatically exploits MySQL servers and subsequently infects Windows systems when triggered by an Internet Relay Chat (IRC) server located in Sweden.
News taken from <a href="http://www.blackhat.info" target=_blank>BlackHat.INFO
A worm, dubbed MySpool by security organisation SANS, is spreading rapidly amongst the MySQL user base. It automatically exploits MySQL servers and subsequently infects Windows systems when triggered by an Internet Relay Chat (IRC) server located in Sweden.
News taken from <a href="http://www.blackhat.info" target=_blank>BlackHat.INFO
Interview: Lee Eason
Tell me about your postnuke "career".
Well, when I first started with PHP it was to build an object translator for
a Flash based order management application I was building. The key was to
keep cost low, so we were using all open source stuff. I liked PHP because
it was fast and very easy to use. Then I started seeing how much PHP was
being used on the web as a language for dynamic sites. That led me to the
open source CMS world, which is where I found PostNuke. I liked how easy it
was to install and extend. I messed with some other systems but PostNuke
was the one I settled on because of its flexibility.
What is your task in within pnCore?
Good question, lol. I don't really know for sure. I'm pretty sure it has
something to do with an article I wrote a while back outlining a PostNuke
module development SDK I have a vision for. It would include a couple of
modules that would work together to help people develop PostNuke modules
rapidly with documentation and support tools all built in.
When did you start programming for PostNuke?
I have not actually started programming for PostNuke yet. I suspect most of
my contribution to the core will consist of input on the project's direction
whenever I can help, and in the writing and development of the SDK's
modules.
What is your development like?
I hope it will be huge. I'd like to see more of the "average joe" be able
to developer, deliver, and support modules they have a need for and can pass
on to the rest of us.
What is the biggest difficulty in your development?
The most difficult thing about developing is trying to create cutting edge
features that will work on any server configuration. I found with
pnFlashGames that subtle differences in PHP and mySQL versions can really
throw a monkey wrench in the works.
Which route will Postnuke in your opinion go in the future?
I think that with the introduction of Xanthia the doors have been opened
wide. The upcoming .76 release also shows us that the developers are
thinking in practical terms, which is great. I would like to see PostNuke
go towards a more business oriented platform, but that is greatly dependant
on module developers providing the functionality to make that work.
What is the weakest/strongest point in PostNuke?
I think PostNuke's greatest weakness is also its greatest strength: the
modular nature of the system. PostNuke relies on third party modules to
deliver a good bit of functionality that every site needs or wants. As a
result, users are at the mercy of the developers of these modules. So if
the modules are buggy then it makes PostNuke look buggy. Conversely, if
they are written and supported well then it makes PostNuke look all the
better. This is another driving force behind my vision for the SDK.
Anything else you always wanted to say about Postnuke?
It never ceases to amaze me how no matter what you do or where you go,
everything is run by individuals. Everyone has their own personality,
complete with their own set of characteristics. This simple fact is what
makes working in a global community like PostNuke so exciting. But you
know, even with all the different cultures and languages the pnCore has to
deal with, module developers and the pnCore team alike all just has to
provide good quality customer support and that will guarantee PostNuke's
continued success. I have always been impressed with the pnCore's customer
support. I strive to offer a high level of support to my module's users as
well; staying positive and trying to be helpful has helped me to establish a
good reputation and a successful project. I only wish we could see more of
that with the third party module developers.
Tell me something about your module work?
I am the author and director of pnFlashGames and pnFlashGames.com.
When did you start working on your own module?
When I first starting using PostNuke I wanted to build a website for my
company and have some tools to help our customers get downloads and
information they needed quickly and efficiently. I could not find modules
that did what I needed so I set out to learn how to make my own modules. I
thought that the best way to do that is just to make my own. So I chose a
fun and easy subject for my first module, a flash games gallery. I found
some flash games to start out with and it just so happened they had a common
high score system (they came from the same author - Paul Neave). So then I
though, if Paul Neave can store high scores in a text file with a common API
for his games, I can make my own API and store the scores in PostNuke's
database for any flash game. Thus, pnFlashGames was born. I never thought
it would become as popular as it is now. I still chuckle when I look back
at my first release.
What features should the Postnuke .8 core have to simplify your
work?
:lol: an automatic conversion script that will take a pnHTML module and
convert it to pnRender.... Seriously though, I'd love the ability to load a
"light" version of the PostNuke API that gives me access to the database and
module API for only the parts I need. This way, I don't have to load the
entire application just to store a score. I only have to load just enough
to get to the pnFlashGames API and make a database call.
Which route will your module in your opinion go in the future?
My community is so fantastic. They are always providing me with great
suggestions and very cool ideas for features and direction. We are working
on multiplayer games, global high scores (site vs. site competitions),
enhanced team functionality (team vs. team competitions), and better quality
and more port projects for other CMS. Currently, pnFlashGames has been
ported to Xoops, Mambo, Invision, and just recently to PHPNuke.
Recently a wonderful thing has happened with pnFlashGames as well. My
company, SourceKit, acquired pnFlashGames and pnFlashGames.com. It's great
news and means that big things are happening with our project. I believe
this is the first time a PostNuke module has been purchased by an
independent company. It says a lot about PostNuke and a lot about
pnFlashGames that a company not involved with PostNuke would see enough
potential and value in a module project to invest like they have done. Best
of all, I still run the project and it is still open source. :) For full
details you can go to the <a
href="http://pnflashgames.com/displayarticle51.phtml">press release on
pnflashgames.com.
What should users of your module regard?
Well, the weakest part of my module is the pnHTML I think. However, I have
addressed that in the short term by using CSS classes in the output whenever
possible and documenting how to use them to customize their look and feel.
I think they are happy with that for now. Eventually I'll port it to
pnRender, but its going to be a lot of work. The strongest part of
pnFlashGames is the traffic generation that comes from it. People like
being on the score board and they will come back to check and make sure
their rank is held. pnFlashGames is an automatic community builder. I
think it is even more effective than a forum because more people will play a
game than post in a forum. Every feature I write is done with that thought
in mind.
Thank you very much for your patience
Well, when I first started with PHP it was to build an object translator for
a Flash based order management application I was building. The key was to
keep cost low, so we were using all open source stuff. I liked PHP because
it was fast and very easy to use. Then I started seeing how much PHP was
being used on the web as a language for dynamic sites. That led me to the
open source CMS world, which is where I found PostNuke. I liked how easy it
was to install and extend. I messed with some other systems but PostNuke
was the one I settled on because of its flexibility.
What is your task in within pnCore?
Good question, lol. I don't really know for sure. I'm pretty sure it has
something to do with an article I wrote a while back outlining a PostNuke
module development SDK I have a vision for. It would include a couple of
modules that would work together to help people develop PostNuke modules
rapidly with documentation and support tools all built in.
When did you start programming for PostNuke?
I have not actually started programming for PostNuke yet. I suspect most of
my contribution to the core will consist of input on the project's direction
whenever I can help, and in the writing and development of the SDK's
modules.
What is your development like?
I hope it will be huge. I'd like to see more of the "average joe" be able
to developer, deliver, and support modules they have a need for and can pass
on to the rest of us.
What is the biggest difficulty in your development?
The most difficult thing about developing is trying to create cutting edge
features that will work on any server configuration. I found with
pnFlashGames that subtle differences in PHP and mySQL versions can really
throw a monkey wrench in the works.
Which route will Postnuke in your opinion go in the future?
I think that with the introduction of Xanthia the doors have been opened
wide. The upcoming .76 release also shows us that the developers are
thinking in practical terms, which is great. I would like to see PostNuke
go towards a more business oriented platform, but that is greatly dependant
on module developers providing the functionality to make that work.
What is the weakest/strongest point in PostNuke?
I think PostNuke's greatest weakness is also its greatest strength: the
modular nature of the system. PostNuke relies on third party modules to
deliver a good bit of functionality that every site needs or wants. As a
result, users are at the mercy of the developers of these modules. So if
the modules are buggy then it makes PostNuke look buggy. Conversely, if
they are written and supported well then it makes PostNuke look all the
better. This is another driving force behind my vision for the SDK.
Anything else you always wanted to say about Postnuke?
It never ceases to amaze me how no matter what you do or where you go,
everything is run by individuals. Everyone has their own personality,
complete with their own set of characteristics. This simple fact is what
makes working in a global community like PostNuke so exciting. But you
know, even with all the different cultures and languages the pnCore has to
deal with, module developers and the pnCore team alike all just has to
provide good quality customer support and that will guarantee PostNuke's
continued success. I have always been impressed with the pnCore's customer
support. I strive to offer a high level of support to my module's users as
well; staying positive and trying to be helpful has helped me to establish a
good reputation and a successful project. I only wish we could see more of
that with the third party module developers.
Tell me something about your module work?
I am the author and director of pnFlashGames and pnFlashGames.com.
When did you start working on your own module?
When I first starting using PostNuke I wanted to build a website for my
company and have some tools to help our customers get downloads and
information they needed quickly and efficiently. I could not find modules
that did what I needed so I set out to learn how to make my own modules. I
thought that the best way to do that is just to make my own. So I chose a
fun and easy subject for my first module, a flash games gallery. I found
some flash games to start out with and it just so happened they had a common
high score system (they came from the same author - Paul Neave). So then I
though, if Paul Neave can store high scores in a text file with a common API
for his games, I can make my own API and store the scores in PostNuke's
database for any flash game. Thus, pnFlashGames was born. I never thought
it would become as popular as it is now. I still chuckle when I look back
at my first release.
What features should the Postnuke .8 core have to simplify your
work?
:lol: an automatic conversion script that will take a pnHTML module and
convert it to pnRender.... Seriously though, I'd love the ability to load a
"light" version of the PostNuke API that gives me access to the database and
module API for only the parts I need. This way, I don't have to load the
entire application just to store a score. I only have to load just enough
to get to the pnFlashGames API and make a database call.
Which route will your module in your opinion go in the future?
My community is so fantastic. They are always providing me with great
suggestions and very cool ideas for features and direction. We are working
on multiplayer games, global high scores (site vs. site competitions),
enhanced team functionality (team vs. team competitions), and better quality
and more port projects for other CMS. Currently, pnFlashGames has been
ported to Xoops, Mambo, Invision, and just recently to PHPNuke.
Recently a wonderful thing has happened with pnFlashGames as well. My
company, SourceKit, acquired pnFlashGames and pnFlashGames.com. It's great
news and means that big things are happening with our project. I believe
this is the first time a PostNuke module has been purchased by an
independent company. It says a lot about PostNuke and a lot about
pnFlashGames that a company not involved with PostNuke would see enough
potential and value in a module project to invest like they have done. Best
of all, I still run the project and it is still open source. :) For full
details you can go to the <a
href="http://pnflashgames.com/displayarticle51.phtml">press release on
pnflashgames.com.
What should users of your module regard?
Well, the weakest part of my module is the pnHTML I think. However, I have
addressed that in the short term by using CSS classes in the output whenever
possible and documenting how to use them to customize their look and feel.
I think they are happy with that for now. Eventually I'll port it to
pnRender, but its going to be a lot of work. The strongest part of
pnFlashGames is the traffic generation that comes from it. People like
being on the score board and they will come back to check and make sure
their rank is held. pnFlashGames is an automatic community builder. I
think it is even more effective than a forum because more people will play a
game than post in a forum. Every feature I write is done with that thought
in mind.
Thank you very much for your patience
Larry Masters (aka PHPNut) Wants Us All to "Live Like You Were Dying"
As you know this item is not about PostNuke software but is news, about a friend and a PostNuke team member, we'd like to share with everyone. Larry Masters (aka PHPnut) our Xanthia theming engine guru/developer is going into the hospital (University of Chicago: http://www.uchospitals.edu) for surgery on a brain tumour. He is checking into the hospital tomorrow (Thursday) and goes into surgery on Friday. We would like to ask everyone in the community to join us in wishing Larry a successful, safe, surgery and speedy recovery.
Also, a personal note, I spoke with Larry on the phone today (Weds) and he's in good spirits. He also wants to assure everyone he'll be fine.
God speed to Larry on a quick recovery and we ask everyone to keep him and his doctor in their prayers. Also, if you'd like to send him a get well card or note we've included his contact information below. Let's all take some time to show Larry our support in this moment of need.
Get well soon Larry!
All the best,
Vanessa aka vworld
on behalf of
The PostNuke Team & Community
P.S. He asks for anyone thinking of sending flowers, plants, etc to instead donate the money you would have spent to a charity reaching out to the Tsumani suvivors/victims.
____________________________
Larry Masters aka PHPNut
20947 South River Road
Shorewood, IL 60431
http://www.larrymaster.com
larry@phpnut.com
Lyrics to the Tim McGraw song, Live Like You Were Dying
(note information posted with Larry's permission)
Also, a personal note, I spoke with Larry on the phone today (Weds) and he's in good spirits. He also wants to assure everyone he'll be fine.
God speed to Larry on a quick recovery and we ask everyone to keep him and his doctor in their prayers. Also, if you'd like to send him a get well card or note we've included his contact information below. Let's all take some time to show Larry our support in this moment of need.
Get well soon Larry!
All the best,
Vanessa aka vworld
on behalf of
The PostNuke Team & Community
P.S. He asks for anyone thinking of sending flowers, plants, etc to instead donate the money you would have spent to a charity reaching out to the Tsumani suvivors/victims.
____________________________
Larry Masters aka PHPNut
20947 South River Road
Shorewood, IL 60431
http://www.larrymaster.com
larry@phpnut.com
Lyrics to the Tim McGraw song, Live Like You Were Dying
(note information posted with Larry's permission)
Sympathy, Condolences, and Solidarity Go Out To Tsunami Survivors, Victims & Families
- RedCross
https://www.redcross.org/donate/donation-form.asp
- International Federation of Red Cross and Red Crescent Societies
http://www.ifrc.org/
- Donate to the Red Cross through Amazon.com
http://s1.amazon.com/exec/varzea/ts/my-pay-page/PX3BEL97U9A4I/104-8764212-2651902
- Doctors Without Borders
http://www.doctorswithoutborders-usa.org/donate/index.cfm
- WorldVision
http://www.worldvision.org/worldvision/master.nsf/
- Unicef
http://www.unicefusa.org/
- PlanUSA (Helping Children Since 1937)
http://www.planusa.org/index.php
- Sulekha-AID Tsunami Relief Fund
Sulekha.com has partnered with Association for India's Development (AID) to raise money for the relief efforts in India following the devastating earthquake/tsunami that has claimed thousands of lives.
http://www.sulekha.com/aidtsunami/
https://www.redcross.org/donate/donation-form.asp
- International Federation of Red Cross and Red Crescent Societies
http://www.ifrc.org/
- Donate to the Red Cross through Amazon.com
http://s1.amazon.com/exec/varzea/ts/my-pay-page/PX3BEL97U9A4I/104-8764212-2651902
- Doctors Without Borders
http://www.doctorswithoutborders-usa.org/donate/index.cfm
- WorldVision
http://www.worldvision.org/worldvision/master.nsf/
- Unicef
http://www.unicefusa.org/
- PlanUSA (Helping Children Since 1937)
http://www.planusa.org/index.php
- Sulekha-AID Tsunami Relief Fund
Sulekha.com has partnered with Association for India's Development (AID) to raise money for the relief efforts in India following the devastating earthquake/tsunami that has claimed thousands of lives.
http://www.sulekha.com/aidtsunami/
Pre release notification - PostNuke .76
Summary of Main Changes
Further cleaning of HTML
- pn-normal custom class removed in favor of styling of block level element using CSS- pn-pagetitle class replaced by use of h1 tag
- pn-title class replaced by use of h2 tag
- all fake lists created using middot's replaced with proper lists
Simplication of non API compliant links
op=modload & file=index are the defaults so these are removed from all links
New printer (Xanthia) theme - enables printable view of any page
Removal of NS- prefix on all modules
Updated modules:
Admin_Messages, Modules, Blocks, Permissions, Groups, legal, Censor, Messages, Ephemerids, Quotes, Autolinks, AvantGo, Credits, Members_List, Ratings & Admin
Modules updated for full API compliance and templated output
- New modules
- Sniffer; Detects browser and browser capabilities using phpSniff (by Roger Raymond)
- RSS; Replaces dated feed handling with an xml based parser (magpie rss)
Bug fixes
- Xanthia - many fixes since original release
- Mailer (added support for additional headers, bcc's & cc's), fixed sending to multiple addresses.
New features in core
- Modules can now be referenced using an 'alias' via the module display name setting.
- Default start function type, function name & parameters to the function can be defined. Note: API compliant modules only.
- Standard database connection error moved to 'template' in includes/templates.
- Ability to turn the site off for maintainence (access to provided via permissions setting).
- Ability to set what function type, function name and any parameters for the start page (API compliant modules only)
New features in modules (in addition to API compliance and templated output)
Modules-module
- filter by letter, state
- graphical indicatator of state
- detection of change of type, admin & user capability
- ability to recover from missing files state
Blocks
- graphical indicatator of state
- ability to define each block as collaspable (credit to Mark Heldstab)
- ability to define each blocks' default collapseable state (credit to Mark Heldstab)
Others
- Groups - ability to add multiple users to a group in one go
- legal - added template accessibility report (thanks to http://diveintoaccessibility.org)
- Censor - added transfrom hook for censor module (supercedes pnVarCensor API - maintained for backwards compatability)
- Admin - added ability to split modules into categories, the categories view are skinable via a single stylesheet
- Credits - support for multiple module contacts via comma seperated values in pnversion.php
- Smarty updated to v2.6.6
- ADODB updated to v4.5.4
Interview: Steffen Voss
What is your real-life job?
I'm a student and going to be an Englisch/Geography teacher. But I also have a job at the university (http://www.gis.uni-kiel.de) and I help the local youth council with their websites (e.g. http://www.balticsea-youth.org).
Tell me about your postnuke "career". (Why do you prefer Postnuke over other CMS?)
When I worked for a bigger German company I had to maintain the intranet. They used static pages until then but I had heard something about CMS and took a look at Postnuke and was overwhelmed. It did almost everything I needed. So I convinced the head of department to use Postnuke and it became my first Postnuke project. Only little later, friends of mine wanted to relaunch their local website (http://www.kiel4kiel.de) so I helped them to implement that with Postnuke.
Postnuke.de was the first contact I had with the Postnuke community, but as the site was a bit messy I offered my help. The webmaster ranted a lot but never let me do anything but post news and forum posts. Little by little I realized that this endeavor what pointless and started looking for like-minded people in Germany and finally found http://www.post-nuke.net. A reservation for the shunned. Larsneo and others had similar experiences with postnuke.de and built up their own community.
By and by we created a German documentation and had more and more people joining us. This year we established a German foundation and organized the first international Postnuke meeting. So things are going well. :-D
What is your task in within pnCore?
I don't have an official function. I do interview, comment and try to keep contact to the core/module devs and to allude them to what the others are doing. "Networking" I think you can call it.
When did you start programming for PostNuke?
I started programming for Postnuke during the Kiel4kiel.de-project - a module called tinyraffle which you find in the noc in a not finished state. I don't need it anymore - so feel free to adopt it ;-)
What is your work like?
As I said - I read and write a lot in the German forum, I mail with devs and try to keep them together and strengthen the company.
What is the biggest difficulty in your work?
It's often hard to promote Postnuke, because of the special communication strategy the project management embarks. There are a lot of nice people working very hard on the future of Postnuke, but the average user only hears about that when a new release comes.
Which route will Postnuke in your opinion go in the future?
The Postnuke core is already far away from PHPNuke but there are still serious lacks on the user side - content handling hasn't improved since PHPNuke - disregarding modules like pnCommerce, Photoshare, Pagesetter aso. .8 will bring the new and for the time being final core. Next thing should be a concentration on the content side of the project. This is what gives new users a good first impression - not a well written source code. Sad but true ;-)
What is the weakest/strongest point in PostNuke?
The weakest point is the name - The general public always mistakes Postnuke for PHPNuke. The strongest point is the great community.
Are you also working on modules?
Yes and no: I released pnAmazon - a module that allows you to include Amazon product-data into you Pagesetter publications using Amazon Webservices. But as it now does all I need, motivation is little to develop it any further.
Internally I work on a module that does almost the same as pnAmazon with an information system that almost every German university uses (uniVIS) - It allows you to include data such as addresses, lectures aso. directly from the central information system into your page. So the department's page is always as up-to-date as the central system. Maybe I'll release it, when it's more advanced. But I'm still looking for a co-developer for this module.
What features should the Postnuke .8 core have to simplify your work?
pnRender is a killer. I love it. It does all I need, but Xanthia has to become more user friendly.
What should users of your module regard?
I only include things that are either needed by me or very simple to implement - I'm not such a good coder...
Anything else you always wanted to say about Postnuke?
Postnuke has such a big user bases and too few people, who actually work for it. A main issue for the future of Postnuke is IMHO to activate the community and to make it easier for people to add their work to development, support, marketing aso. Even the smallest help is help.
Thank you very much for you time.
My private homepage: http://www.kaffeeringe.de
I'm a student and going to be an Englisch/Geography teacher. But I also have a job at the university (http://www.gis.uni-kiel.de) and I help the local youth council with their websites (e.g. http://www.balticsea-youth.org).
Tell me about your postnuke "career". (Why do you prefer Postnuke over other CMS?)
When I worked for a bigger German company I had to maintain the intranet. They used static pages until then but I had heard something about CMS and took a look at Postnuke and was overwhelmed. It did almost everything I needed. So I convinced the head of department to use Postnuke and it became my first Postnuke project. Only little later, friends of mine wanted to relaunch their local website (http://www.kiel4kiel.de) so I helped them to implement that with Postnuke.
Postnuke.de was the first contact I had with the Postnuke community, but as the site was a bit messy I offered my help. The webmaster ranted a lot but never let me do anything but post news and forum posts. Little by little I realized that this endeavor what pointless and started looking for like-minded people in Germany and finally found http://www.post-nuke.net. A reservation for the shunned. Larsneo and others had similar experiences with postnuke.de and built up their own community.
By and by we created a German documentation and had more and more people joining us. This year we established a German foundation and organized the first international Postnuke meeting. So things are going well. :-D
What is your task in within pnCore?
I don't have an official function. I do interview, comment and try to keep contact to the core/module devs and to allude them to what the others are doing. "Networking" I think you can call it.
When did you start programming for PostNuke?
I started programming for Postnuke during the Kiel4kiel.de-project - a module called tinyraffle which you find in the noc in a not finished state. I don't need it anymore - so feel free to adopt it ;-)
What is your work like?
As I said - I read and write a lot in the German forum, I mail with devs and try to keep them together and strengthen the company.
What is the biggest difficulty in your work?
It's often hard to promote Postnuke, because of the special communication strategy the project management embarks. There are a lot of nice people working very hard on the future of Postnuke, but the average user only hears about that when a new release comes.
Which route will Postnuke in your opinion go in the future?
The Postnuke core is already far away from PHPNuke but there are still serious lacks on the user side - content handling hasn't improved since PHPNuke - disregarding modules like pnCommerce, Photoshare, Pagesetter aso. .8 will bring the new and for the time being final core. Next thing should be a concentration on the content side of the project. This is what gives new users a good first impression - not a well written source code. Sad but true ;-)
What is the weakest/strongest point in PostNuke?
The weakest point is the name - The general public always mistakes Postnuke for PHPNuke. The strongest point is the great community.
Are you also working on modules?
Yes and no: I released pnAmazon - a module that allows you to include Amazon product-data into you Pagesetter publications using Amazon Webservices. But as it now does all I need, motivation is little to develop it any further.
Internally I work on a module that does almost the same as pnAmazon with an information system that almost every German university uses (uniVIS) - It allows you to include data such as addresses, lectures aso. directly from the central information system into your page. So the department's page is always as up-to-date as the central system. Maybe I'll release it, when it's more advanced. But I'm still looking for a co-developer for this module.
What features should the Postnuke .8 core have to simplify your work?
pnRender is a killer. I love it. It does all I need, but Xanthia has to become more user friendly.
What should users of your module regard?
I only include things that are either needed by me or very simple to implement - I'm not such a good coder...
Anything else you always wanted to say about Postnuke?
Postnuke has such a big user bases and too few people, who actually work for it. A main issue for the future of Postnuke is IMHO to activate the community and to make it easier for people to add their work to development, support, marketing aso. Even the smallest help is help.
Thank you very much for you time.
My private homepage: http://www.kaffeeringe.de
Interview: Carl Slaughter
Where do you live?
Bethalto, IL USA
Where in the world is Bethalto, IL, USA
What is your real-life job?
IT Manager/Supervisor for a Credit Union
Tell me about your PostNuke "career".
PostNuke was what I started with and I liked it, I have tried others but PN is what I'm most comfortable with and frankly I do not want to learn another unless its REALLY great, and I do not see that happening ;-)
When did you start working on your own module?
Jan, 2003
Please describe to the community what your development is like?
It’s really only I and Batpuppy (Patrick Peay). I do most of the coding and Patrick does the debugging and HTML.
We never intended it to be as big a success as it is, we just wanted a good forum module for our own PN sites. And well the rest is history ;-)
I use HTML-Kit, along with tools like Power Desk Tools, with file find, and Xampp for local web testing. For release development we use TortoiseCVS, and UNIX command line tools for file compares.
What is the biggest difficulty in your development?
The difficulty only rests in your own abilities and desire to learn as much as you can about the PN core, along with keeping with the changes. Knowledge of PHP, HTML, and cross browser coding is a must as well. You have to develop skills in every area, then of course you develop your own personal abilities to bring your own ideas to the code as well, remember there is usually 100 different ways to accomplish the same thing, but only a few ways to do it right ;-)
What features should the PostNuke .8 core have to simplify your work?
Module aliasing. Lower overhead for modules (usually the module's fault) however the PN core has a good amount that is has in memory then if you have a significant module like PNphpBB then you start scraping the top of the RAM ceiling.
Which route will PostNuke/your module in your opinion go in the future?
As PNphpBB matures it will become more and more integrated into PN, we will streamline the code and do away with all unused code from the core of phpBB. Possibly fork the entire code, because currently we have kept the same basic code of the current phpBB release so we can apply phpBB specific patches and admins can easily add mods designed for phpBB. This will eventually not be an issue as more and more people are writing mods for PNphpBB directly.
What is the weakest/strongest point in your module?
PNphpBB is a module version of the popular phpBB forum it does its best to stay true to all the features and functionality of its stand alone counterpart as well as offering those who use phpBB the ability to migrate to a CMS environment. Its weak points are since it is a port of a stand alone module, it has a lot of redundant code, its own DB functions, template/HTML output code and functions that are not necessary due to the fact it is contained within PostNuke as a module (login/registration is not used).
Thank you very much for you time.
Visit Carl and the pnPHPBB forum project at http://www.pnphpbb.com
Bethalto, IL USA
Where in the world is Bethalto, IL, USA
What is your real-life job?
IT Manager/Supervisor for a Credit Union
Tell me about your PostNuke "career".
PostNuke was what I started with and I liked it, I have tried others but PN is what I'm most comfortable with and frankly I do not want to learn another unless its REALLY great, and I do not see that happening ;-)
When did you start working on your own module?
Jan, 2003
Please describe to the community what your development is like?
It’s really only I and Batpuppy (Patrick Peay). I do most of the coding and Patrick does the debugging and HTML.
We never intended it to be as big a success as it is, we just wanted a good forum module for our own PN sites. And well the rest is history ;-)
I use HTML-Kit, along with tools like Power Desk Tools, with file find, and Xampp for local web testing. For release development we use TortoiseCVS, and UNIX command line tools for file compares.
What is the biggest difficulty in your development?
The difficulty only rests in your own abilities and desire to learn as much as you can about the PN core, along with keeping with the changes. Knowledge of PHP, HTML, and cross browser coding is a must as well. You have to develop skills in every area, then of course you develop your own personal abilities to bring your own ideas to the code as well, remember there is usually 100 different ways to accomplish the same thing, but only a few ways to do it right ;-)
What features should the PostNuke .8 core have to simplify your work?
Module aliasing. Lower overhead for modules (usually the module's fault) however the PN core has a good amount that is has in memory then if you have a significant module like PNphpBB then you start scraping the top of the RAM ceiling.
Which route will PostNuke/your module in your opinion go in the future?
As PNphpBB matures it will become more and more integrated into PN, we will streamline the code and do away with all unused code from the core of phpBB. Possibly fork the entire code, because currently we have kept the same basic code of the current phpBB release so we can apply phpBB specific patches and admins can easily add mods designed for phpBB. This will eventually not be an issue as more and more people are writing mods for PNphpBB directly.
What is the weakest/strongest point in your module?
PNphpBB is a module version of the popular phpBB forum it does its best to stay true to all the features and functionality of its stand alone counterpart as well as offering those who use phpBB the ability to migrate to a CMS environment. Its weak points are since it is a port of a stand alone module, it has a lot of redundant code, its own DB functions, template/HTML output code and functions that are not necessary due to the fact it is contained within PostNuke as a module (login/registration is not used).
Thank you very much for you time.
Visit Carl and the pnPHPBB forum project at http://www.pnphpbb.com
Page 24 / 277 (231 - 240 of 2763 Total)
