PostNuke

Can be downloaded in ZIP format from here :

<a href=http://www.postnuke-france.org/modules.php?op=modload&name=Downloads&file=index&req=getit&lid=168 target=_blank>French Translation 0.726

You should also read a news for this transation for further information <a href=http://www.postnuke-france.org/modules.php?op=modload&name=News&file=article&sid=334&mode=thread&order=0&thold=0 target=_blank>here but it's in french :-)

Regards,

nunizgb member of pndev team and one of webmasters of french support site for postnuke which is <a href=http://www.postnuke-france.org target=_blank>postnuke-france.org

I was just looking at the Mozilla homepage, and I discovered their status updates page. It's great! They announce current releases, fixes of prominent bugs, new and planned features, important anniversaries related to the project.... Each announcement includes links to related information and documents. And they do it once a week! They even have links to 3rd-party status reports.

I'd like to see a similar thing in PostNuke. The community appears to be very large, with lots of things being developed simultaneously. Why not devote a page or two at PostNuke.com to informing the community of what's going on? Maybe call it "pnStatus". The focus could be on the core, but could even have news from significant 3rd-party development efforts.

I looked around at PostNuke.com, but I couldn't find anything like it. development.postnuke.com looks dormant; the last news posting is from July. And several of the links in the header are broken. Sure, there are forums, but I don't want to spend the time weeding through all of them to find out what's happening, with no guarantee that I'll find anything meaningful. With a "pnStatus" page, any newsworthy items would be together in a convenient easy-to-read format.

What say ye? How about it?

php-con West 2003: Community. Code. Solutions.
October 21- 24, 2003
Biltmore Hotel
Santa Clara, California
http://www.php-con.com

Why is php-con the destination of choice for PHP and web developers? Because php-con is about three things: Community. Code. Solutions.

Community. PHP developers all share a common goal: Getting the most out of the Web. And php-con is the where the PHP developer community comes together to advance that goal.

Code. php-con program packs in full-day tutorials, three tracks of technical sessions and the all-day developer marathon: The php-con Code Sprint. Write, debug and test your code along side PHP's finest.

Solutions. php-con is where you will find everything you need related to robust, rapid applications development, standards and best practices: MySQL, PostgreSQL, XML, PEAR, Webservices, PHP-Gtk, PHP/GD, testing and debugging, performance tuning, and extending PHP.

Don't wait to secure your space at php-con! Early Bird Registration discounts end on September 26, 2003. Register online today at http://www.php-con.com. Information on student discounts is available on our registration page.

** Information, Questions and Comments **

Want to stay on top of PHPCon news? Sign up for our php-con Announce
List and get the latest information. Click on http://www.php-con.com and scroll down to our "php-con Announce List" section to subscribe.

** Sponsors **

Platinum: Linux Magazine
Silver: Developer's Library/Sams Publishing
Media: CodeWalkers, Dr. Dobb's Journal, The FuzzyGroup, HackerThreads.com, New York PHP User Group, PHP-Editors.com, PHP Everywhere, PHPLens, The PHP User Group of Kansas City, PostNuke, Weberdev.com, and Webifex Magazine

Jørn Lind-Nielsen lives on Sealand - the Island with the Danish Capital Copenhagen on it.

Tell me about your postnuke "career" - When did you first came across Postnuke and why do you prefer it over other CMS?

I started working with PostNuke in the spring 2002. At that time I was looking for a CMS to create a community site for a Danish group of mountaineering and wildlife interested scouts called Fjeldgruppen". I knew zip about content management systems at that time and was in fact prepared to create my own site manager from scratch. Then someone mentioned the acronym CMS and I was hooked - no need to do all the boring user handling stuff and all the other infrastructure that are needed for such a thing. Just install and you are up and running.

So I started looking for a CMS and PostNuke was the first one to show up as a viable solution. I never tried XOOPS, Envolution or other similar systems for the simple fact that PostNuke was the first I found that fitted my requirements. It installed without a glitch and I was able to figure out the most important features. Not that it was easy - I have always found PostNuke to be quite difficult to understand for the sole reason that the modules all have different authors, no documentation, and uses a multitude of different names for the same things.

The next problem was that we had some special requirements that none of the modules fitted. We needed a members list with export facilities and other links than the built-in list, we also needed ways to handle sign-ups to our courses, and we needed an image gallery. So I started coding on my own. The first module was a back-end to FormExpress since we needed some better
formatting possibilities of the e-mails that it sends. We use that now for course sign-ups. The next module was a generic report maker with some neat XML report setup. We only used that for our members list. Actually a nice module, but I never got around documenting it, so it's unreleased so far.

The biggest problem was that our server was running SAFE_MODE PHP - and we *really* needed an image gallery for our site. So with the success of the first modules I decided to make such a thing myself for all those people with SAFE_MODE hosting.

I first came across your name at the Content Express Forums - what is your involvation there?

None anymore. I joined the development team for a short while, but didn't have the time to spare. So I never got around doing anything with the CE code.

What is your development like? Do other people help you? How do you work together? How big is the impact of the community on your development?

I work alone 99% of the time. I get some help from a Dutch Photoshare user who has setup a CVS server and added a few features here and there. Hopefully he may find some time now to add yet some more features.

The feature set of Photoshare is driven by a combination of community input (50%) and my personal desires (50%). I have recived a lot of positive feedback and is glad to have my own web-site where all the interaction is handled.

What is your roadmap with Photoshare?

The focus area for the comming releases of Photoshare will be

1) The ability to, as easily as possible, hack the various News and page edititor modules in such a way that they can integrate Photoshare images by "point and click".
2) Improving on the visual design.
3) Better upload facilities and some simple image manipulation functions.
4) Community interaction with the gallery (voting and commenting on the images).

What is the weakestpoint in your module?

The strongest points are the ability to run on SAFE_MODE servers and the
access control. That's what Photoshare was designed for. Most other
functions can be found on all other image albums.

...and the weakest?

The weakness lies in the lack of features and resources to create them. Being mainly a one-man team restricts the coding speed to a certain level.

Are you actually looking for help with Photoshare? (Coding, Documentation...)

I could use some coding help, but being an arrogant bastard with a phd in computer science doesn't help me much getting help. I have already scared off a few people ;-) If someone want's to help they better do it right!

What is the biggest difficulty in your development? And why? Is it a Postnuke inherent problem? What features should the Postnuke .8 core have to simplify your work?

The biggest difficulty is the integration with other modules in PostNuke. I would like people to be able to (easily) insert Photoshare images in News items (as well as other items), show context dependent images in a block so that my "random image" block shows images related to the items currently shown in the main module area (News items for instance). To do so I think PostNuke needs some core "black board" where the current module can sort of "post/write" information about itself (for instance the topic related to the News item) . This would allow the various blocks to know what to show based on the current module data.

It would also be helpfull if the core had a standardized API for retrieving the list of all users and topics. Now I have to code the SQL requests myself and who knows which version of PostNuke these will break in.

Which route will Postnuke take?

I think PostNuke seriously needs to focus on static content. There's a lot of very nice modules for handling of all sorts of interaction (image sharing, News, bulletin boards and so on) but only two modules for page editing - ContentExpress and PagEd. If I mostly needed to show a lot of static pages and the addition of more page should be easy, then I would never choose PostNuke.

Jørn Lind-Nielsen's Homepage: http://www.elfisk.dk/

These and some other questions are to be answered in a lose series of interviews I'm going to do in the coming months. I already asked some module developers for interviews but few have answered I hope this changes with the first published articles. My first interview will feature Jørn Lind-Nielsen of Photoshare - the youngest of Postnuke's gallery modules. Maybe some of you also want to do some interviews - feel free! I will also appreciate suggestions for interview-partners.

The interviews will be published here at postnuke.com and in a translated German version at post-nuke.net. If you want to translate them into French, Spanisch, Klingon and publish them at your national Postnuke community - just do it. ;-)

The Linux4Arab is very popular Linux site among Arab speakers, as it has been for the past 7 years the most updated, and well-known site in its field.

The recent site upgrade that was waited for, took place in August 29, and it included beside the CMS change, adding many new features and sections for the site.

We are getting to represent Postnuke very well and in two weeks we are going to release a version of Postnuke totally in Brazilian Portuguese with manuals and docs translated.

We want to build a Community of Members that will help people to know Postnuke and have their WebSite improved with Postnuke features. Our project is to show how it is possible to have knowledge and share with others and rceive this again.

Then we wait for you in our Postnuke Braziian Community. Come on!!! Visit Us!!!

Introduction to the PostNuke CMS
Postnuke is a free CMS (Content Management System), which is based on PHP. It makes use of the ADODB database abstraction layer and connects to many Database Management Systems like mySQL, SQL, PostGRESQL, and many others.

PostNuke development is Open Source allowing robust, modular and secure feature-rich software. It has a development community with over 120 active developers who contribute their time and knowledge to the project for free.

Some features of the PostNuke CMS
Since the primary purpose of PostNuke is to easily maintain dynamic content, it has many default features which cater for that. Users can submit content which are approved by the admin before publishing. Administrators can set permissions and create groups to distribute work loads. And the latest PostNuke version contains a WYSIWYG editor to allow users to have more control over their content.

PostNuke is extremely easy to customized even for those who are not well versed with HTML. Customization of all aspects of the website's appearance is possible through themes, including CSS support. It is suitable for any type of website is that it is flexible, and expandable, in the sense that it is easily customized and maintained through modules, themes and blocks which can easily be fitted to it very with little configuration.

You can read more about this review at http://www.edevcafe.com/viewdoc.php?eid=317