PostNuke

Site search

Search results

Number of hits: 25

Going OpenID   (News)

(if you already know OpenID then jump directly to the last section about
OpenID in PostNuke)
OpenID - a Free, Decentralized Online Identity
OpenID is a relatively new web-technology for managing your online identity. It's primary purpose is to facilitate Single Sign On across independent websites. This means you can create yourself an OpenID identity and use that for login in to different websites without having to retype your password over and over again.
Your OpenID consists of a URL, e.g., http://jornwildt.myopenid.com, and the OpenID technology makes it possible for you to prove that you own this URL. So, when you want to log in to a website supporting OpenID, you type this URL and then the website takes care of the rest (almost). EnThinnai Blog compares OpenIDs to credit cards: credit cards are issued by someone, it proves your identity at the issuer, you can have as many cards as you want, and in OpenID's case you can even use them to get access to places.
You can also use your OpenID to sign a weblog comment without the need to register as a user on that website. No one else can do that with your URL so your comments cannot be spoofed by anyone.
Take a look at these demos of how it works in some applications: OpenID for WordPress.
OpenID on blogger.com.
OpenID at
plaxo.com.
On Simon Willison's website you can also see some good examples of what OpenID can be used for.
One very interesting thing is that OpenID has just been adopted by Yahoo! So now each and every one of the 250 million Yahoo! users have their own OpenID identity. Even Google, IBM, Microsoft, and VeriSign have signed up to support the new technology. With that kind of backing OpenID is no more a kids toy.
OpenID is of course not the perfect solution for everything
(see for instance idcorner.org) but I would say it is close to perfect for Single Sign On and signing comments in the web/PostNuke world I live in.
If you want to start using your own OpenID then get one at
myopenid.com - it's free and it's all you need.
OpenID in a PostNuke world
PostNuke should of course also have such a thing as OpenID for Single Sign On, user registration, signing comments and so on. So a new OpenID module for Single Sign On and user registration is on it's way (expected release in March or April). Have fun with it.
An OpenID implementation with PostNuke should also enable you to use your PostNuke installation as an Identity Provider, meaning that your OpenID could be YourName.YourSite.com. Hopefully the OpenID module will support this.
Other uses for OpenID in PostNuke could be to sign comments using the ezComments module or pre-allow access to certain Mediashare photo albums through your friends OpenIDs. Only the sky is the limit and OpenID is free for you to use and invent with.
Regards, Jørn Wildt

Generated on February 29, 2008.

A Call For Volunteers   (News)

Layout and User Interface Team
Now PostNuke is nearing the final release of 0.8, we're beginning to look beyond towards the future development, both of .8 and .9. In that future, we'd like PostNuke to look better, be easier to use and to really stand out among all the competing systems out there. And all that while remaining standards compliant and accessible! We need a team of skilled people to take PostNuke to the next level. We're looking for those skilled in HTML, CSS, Photoshop and image design, Ajax (specifically prototype and PostNuke's Ajax framework), PostNuke's theme engine and those with a knowledge of standards and Section 508. Does any one of that list sound like you? If so, please contact us as soon as possible for more information!

ValueAddon Development
We're still looking for willing developers to take over development of all the old ValueAddons in SVN (see the PostNuke-devel/modules directory for a full list). The more modules from this selection that are adopted by third party developers the better - the core team can concentrate on faster and better releases of the core, moving us to .9 quicker. All the modules in SVN are .8 ready, they just need a little attention and new features adding. Please get in touch if you can adopt a ValueAddon.

Support
This is something every single PostNuke user can contribute to. We're always looking for help in the forums, answering questions and helping users both experienced and just getting started. The PostNuke community is a friendly place, so why not show that to those who join us by answering any questions they may have? Even better, if you could transfer whatever you write a detailed page in the PostNuke Wiki you'd benefit the whole community.

Marketing and Publicity
Following .8 we're planning a marketing campaign to show the world just how good PostNuke is. If you have contacts in the web development industry, are able to publicise PostNuke to clients, coworkers or write a series of articles for a magazine then you can contribute here! We're looking to form a team entirely focused on this goal, so please contact us if you can help out.


Of course, if there's nothing in the list above which appeals to you we can always find a use for a willing volunteer. If you

Generated on January 4, 2008.

pnMeeting 2007: Mark West: Porting an Open Source Template to Postnuke .8   (News)

There are several sites that offer open source web-templates - you can take them and build your own site on them.

You choose one of their templates and turn them into a theme in 20-30 minutes with some experience. So if you watch the recorded presentation you will be able to follow Mark explanations step by step. We will put them online within the next few days.

Additionally there is already a lot of information in the development wiki.

In Mark's presentation you will also learn about the need to still provide table style sheets and how to correctly implement them.

Also a theme isn't only the template for the general layout - with for example the RSS theme you can generate RSS from every templated module. Of course it is also possible to generate other kinds of XML or other ways of displaying content.

One major advantage of the new theme engine is the possibility to completely port a theme with all settings from a sandbox site to the live site as all variables are stored in Smarty compatible .ini files.

We hope that this presentation sparks a new wave of themes and inspires new people to design their own layouts as these steps do not only apply to open Source web templates but also for your own designs created in Dreamweaver, NVU and so on. Mark already converted more than 100 free web templates that are available for .8 in the NOC or on Mark West's homepage.

BTW: Some more photos

Generated on September 8, 2007.

pnMeeting 2007: Robert Gasch on DBUtil and the Object Model in .8   (News)

Only few have heard about DBUtil, even fewer have used it themselves. Robert Gasch aimed at changing this.

DBUtil frees the programmer from the need of writing SQL. You rather work with objects and all your selects will be checked for permissions. So if you fetch a set of 10 articles you will only receive that 10 articles that the users is allowed to see. This alone is a major enhancement and saves lots of code lines.

Robert presented the object library as a powerful yet quite easy to use system for the handling of objects. After the initialization of an object you can select, edit, delete aso the object. For a more detailed look into the ObjectLib you should watch the recorded presentation which we will publish within the next few days. Or watch the other presentations live.

Do you want to see how our location looks like? Look here!

Generated on September 8, 2007.

Case Study - www.eurojamlive.org   (News)

So, how does eurojamLIVE! fit in?
eurojamLIVE! has been designed to allow participants and event organisers to communicate before, during and after the event.
There will be 10,000 people at the event, so the website has the potential to receive a great deal of traffic over the coming months.
eurojamlive.org as a PostNuke website
PostNuke was chosen for the eurojamLIVE! website. We needed a solution that could be deployed quickly, with only a limited amount of
modifications. The websites for Scouting 2007 are run on an entirely volunteer basis, and PostNuke's ease of use and open source code
was ideal for this.
Constructing the website
The website initially began as a standard PostNuke install. All the extra core modules that were not needed were removed, and the
tables for each of these modules manually removed from the database. The decision was made to use pagesetter
for most of the content, including the news functionality. We needed the workflow and template functionality provided by pagesetter
but not available in the core News module. Additionally, PNphpBB2 was used for the forums, due to its extended feature set.
In the end, the site's configuration looked like this:
PostNuke Version: 0.760
Although at the time 0.760 was still in the RC stage, it was considered important to use the latest version to take advantage of
sessionless anonymous users (for a performance increase) and also recent improvements in Xanthia's full page caching, which in the end
proved important for the website.
Module List

pagesetter
photoshare
EZComments
PNphpBB2
Downloads
pnFlashGames
Weather

Blocks

dp-StaffStatus

Theme

pnfr-vx - courtesy of Chestnut, pnFrance

Custom Developments
Although nothing revolutionary was needed, a few custom developments were used.
Block Management
A fairly simple module making it easier to change the news stories appearing on the homepage. Instead of the default pagesetter block,
which requires the story ID, this module allows the user to choose the story title to show, rather than having to know the ID.
Profile integration - PNphpBB and PostNuke
Better integration between PostNuke's profiles and PNphpBB profiles were needed. As a result, all the forum profile settings were
moved to a link in the 'Your Account' section, the profile link in the forums now redirecting to user.php. One further change was
needed for everything to work as expected - the profile information had to be updated each time the user visited the forum index,
incase they had changed any part of their profile.
The First Day
Although the site was launched on the 3rd of June, it's existance was not advertised until the 5th June
at 2pm. Between this point, and 9pm, the site received 55,000 hits and served almost 1GB of traffic. This level of initial
support was not initially anticipated, and there was a slowdown for a few minutes until Xanthia's full page caching was enabled.
This had the effect of reducing server load by more than 50%, and the site consequently confortably rode through the initial spike in traffic.
The server itself already ran the Scouting 2007 network of sites, before the eurojamLIVE! launch. In an ideal world the eurojamLIVE!
website would be on its own seperate server, however this is not the case, and therefore performance in paramount. In the end,
I would say the server and the PostNuke website stood up to the demands quite well.

Visit eurojamLIVE!

Generated on June 14, 2005.

Kevin Hatch, Author of PostNuke Book   (News)

Question
Vanessa Haakenson: Kevin first let me thank you for taking the time to answer my questions. Tell us about yourself and what attracted you to PostNuke. How long have you been using PostNuke? Why didyou choose PostNuke?
 
Answer
Kevin Hatch: Well for what it’s worth, I’m a professional web developer. I’ve worn a lot of hats over the years with different sometimes-fancy titles, but overall I’ve mainly been a front-end UI guy in most of the teams I’ve been with. Lately I’ve been doing more programming and database development than Photoshop graphics, but I also freelance as a designer to help balance out the creative side.

I was first introduced to PostNuke early in 2003. My workplacewas primarily Microsoft when it came to web development, and my background at the time was much more with VB/ASP and early .NET. But we were starting a change to Linux servers, and it seemed clear ASP was on the way out. It was a coworker friend of mine that originally suggested PHP as a more universal solution, and without any particular preference for ASP I was happy to give it a shot. My experience with C++, Java, and JSP allowed me to pick up PHP pretty easily, and I quickly feel in love with language.

My first PostNuke site was actually an intranet portal. I’d converted all our other sites’ ASP pages to PHP, but we started looking at different PHP content systems to make the intranet development a little easier. I tried early alternatives like PHP-Nuke and phpWebSite, but PostNuke impressed me as a more mature system that also possessed a strong community of users.


 
Question
Vanessa Haakenson: What is the easiest and/or most difficult thing you encountered building your site?
  
Answer
Kevin Hatch: Funny thing, the most difficult thing about my current site was the choice of methods for publishing the content. There were too many options. I struggled with a number of different combinations of stock and third-party modules like PageSetter. I went all out, creating complex layouts and forms for my pages, but ultimately my needs just didn’twarrant all the trouble. I came back to the basic Sections module for most of the content, and the simpler solution gave me more raw control.
The easiest thing had to be my solution for the column layout using AT-Lite. My original theme was done with Xanthia, but I later tried it in AutoTheme to see how the layout features would work for what I needed. I found AT’s AutoBlock objects to be anabsolute dream for easy block-to-page assignment, and that’s what I ended up using.

Question
Vanessa Haakenson: When did the idea of a PostNuke book happen? What's the back-story?
  
Answer
Kevin Hatch: Early on as I worked with PostNuke I knew it was a project under development. It didn’t solve all my development needs, and I quickly started hacking and extending the code to get the extra features and customization I needed. In order to reproduce those hacks later as needed for other installs or upgrades, I documented the steps I took. I quickly had a great deal of good content collected, and I decided it ought to be posted online in case anyone else wanted to make the same custom changes I had. I wrote up the hacks as walk-through articles, and added them to my website.
I did post links to the guides now and then when answering a forum post that could use them, but just having the articles online ultimately prompted the book. The publisher Pearson Ed was looking to do some books on Content Management Systems, and in searching online for PHP-Nuke and PostNuke resources the editor came across my site. They liked the style and content of the articles, and asked if I’d be interested in writing a full book along those lines. I also have a formal writing background, and said I’d be happy to do it. That was back in November 2003.
After the approval of the book proposal I'd put together, the book itself was written over the course of the next ten months. Things were going fine with it till the surprise release of version 0.75. Sweeping changes were made to the content to add in the 0.75 changes, and some of the existing sections were no longer relevant and had to be cut. In the end there was also an overall length issue, where some of the other third-party modules I wanted to cover were also dropped. There are a lot ofgreat modules out there, but there just wasn’t the room to do them all.

Question
Vanessa
Haakenson: How
is
the
book
selling?
Are
you
going
to
do
a
follow-up/update
when newer
versions
of PostNuke
are released?
  
Answer
Kevin
Hatch: I
know
that in
the first
month over
two thousand
copies
were
sold, but
I don’t
know the
overall
sales figures
yet. I
did secondary
edits earlier
this year
for the
second
printing,
so the
first runs
seems
to have
done better
than their
initial
expectations.
There was
also talk
of doing
a German
translation
of the
text, but
I’ve
not heard
back from
that department
to know
if it’s
gone through.
I've been
very swamped
with
work lately,
so I've
honestly
not been
following
it closely
the last
few
months.
Whether
there’s
a follow-up
will probably
depend
more on
the long-term
book sales.
I’m
up for
writing
it if it
works out.
I’ve
also considered
doing a
shorter
book that
picks up
where PostNuke
Content
Management
left
off. I
think it
would be
useful
to have
a step-by-step
walk through
on the
development
of an API-compliant
module.
In the
first drafts
of my book,
there had
been a
section
at the
end just
on module
development,
but all
that made
it into
the book
was the
short API
functions
appendix.
The book
was targeted
well to
reach a
large audience,
but I do
with I’d
done even
more on
the advanced
side. I
think PostNuke
is a great
core
product,
but I’ve
never built
a site
with it
that didn’t
have third-party
modules
and custom
hacks.
It’s
like how
Firefox
is a great
core product,
but having
the right
few extensions
can literally
change
the way
your
browse.
PN already
does that;
there is
of course
the NOC
and many
great
developers,
but I’d
definitely
like to
see even
more. You
shouldn’t
have
to be a
coder to
get it
to work.
PostNuke
can become
anything
you want
it
to be,
but it’d
be easier
to have
all those
options
possible
in simple
add-on
modules.

Question
Vanessa
Haakenson: You
have
a great
site,
KevinHatch.com.
Tell
us
a little
bit about
the site
and how
you customized
it. What
modules
are you
using
for the
site? What
modules
were customized
or built
from scratch?
  
Answer
Kevin
Hatch: Well
my main
site’s
running
on PostNuke
0.75. As
I said
earlier
I’d
used a
variety
of third-party
modules
during
the development,
but I’m
currently
only running
AT-Lite
for the
theme.
The pages
have two
main content
areas,
and while
I began
with both
areas in
the “body” area,
my desire
to reuse
the side
column
for navigation
elements
prompted
me to
set it
up as a
separate
block area.
I created
an AT AutoBlock
object
for
each area
I wanted
to isolate,
like "Links" or "Homepage" for
example.
The
AutoBlocks
are displayed
in the
same place
in the
theme code,
but I
control
the visibility
of those
blocks
from within
AutoTheme
on a page
by
page basis
using the
AT Custom Modules
feature.
The
site does
have some
custom
code hacks,
but for
the most
part they
have
been used
to simplify
the PostNuke
install.
I normally
don’t
need most
of
the core
PN features
for my
personal
site, so
I removed
what I
didn't
need. The
links page
is the
most obvious
example.
That is
just the
core
Web Links
module,
but I changed
the display
of the
content
and removed
all
the user
features
that were
not needed
anymore.
I’ve
considered
writing
a
new links
module
from scratch
as well,
but for
the moment
just editing
the
core’s
working
fine, and
I do have
enough
other projects
to keep
me busy.
The KevinHatch.com
site is
really
not finished.
I’ll
be adding
a PNphpBB2
forum for
the application
support
in the
next couple
months,
and I need
to
finally
set aside
a weekend
to edit
and upload
some of
my other
guides
and
tutorials.
I plan
on expanding
the old
programming
guide content
to
include
information
on UI design
and Photoshop.
The site
is also
currently
a hybrid
of PostNuke
and raw
PHP using
server-side
includes
to pull
in the
PN theme
elements.
It was
simply
faster
at the
time to
set it
up that
way,
but eventually
the site
will be
completely
PostNuke.  

Thank You
Vanessa
Haakenson: Thank
you
for
sharing
your
thoughts
with
the community
and readers.
  
Answer
Kevin
Hatch: I’d
just like
to say
thanks
again to
all the
developers
who’ve
put in
so much
time to
keep this
project
going.
The open
source
movement
for me
has really
re-energized
my love
of online
development.
I
know things
don’t
always
get released
as quickly
as users
might want,
but
the focus
on producing
a quality
product
is quite
admirable.

  
About
Kevin Hatch
Kevin
Hatch is a
professional
web developer
specializing
in user
interface
design.
He has
more than
a decade
of
experience
in Internet
development
and has
worked
in a variety
of roles,
ranging
from graphic
designer
and interface
systems
analyst
to webmaster
and network
architect.
These days
he mainly
programs
in PHP
as a webmaster
and application
developer,
and freelances
as a graphic
designer
for select
projects.
He
has a combined
degree
in Computer
Science
and English.
He's experienced
in technical
writing
and is
the author
of a book
on the
PostNuke
CMS. He
currently
lives in
eastern
Iowa with
his wife
and their
nine pets.  
Related Links: KevinHatch.com
Purchase the book: PostNuke: Content Management System  

About
Vanessa Haakenson
Vanessa
Haakenson
brings
several
years of
experience
in developing
web based
instructional
products.
She is
an Open
Source
advocate
and contributes
her free
time to
managing,
promoting,
and working
with the
PostNuke
content
management
system.
She has
used PHP
for three
years and
has conducted
workshops
on PHP
basics.
Related
Links:
Designs4Nuke.com
(http://www.designs4nuke.com)
   



This work is licensed under a Creative Commons License.

 

Generated on April 25, 2005.

Interview: Steffen Voss   (News)

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

Generated on December 20, 2004.

Not quite a Roadmap   (News)

50%. He emphasized the advantages of this real templating system of non-templating systems like the old theme enginge or Autotheme.

After some turkish fast food Larsneo (Germany) told about the advantages of accessibility within Postnuke core. All avertable barriers will be removed from the core. The rest will lie in the hands of the administrator. This will not only make Postnuke sites accessible for handicapped users but also better to evaluate for search engines.

His second topic was the dangers of cross site scripting and other security issues. He pointed out his latest advances in fighting these problems. In the following discussing the team came up with a number of ideas that might prevent some of the mistakes of the past.

The second Day

The second day was the day of the module developers and far too short. Jørn Lind-Nielsen (Denmark) introduced us to his latest coup: workflows in Pagesetter 5.0.0. The state-based system uses XML and php-plugins for the design of specific workflows. Everybody was really impressed by his advances.

A new quality of commercial module development was presented by Frank Schummertz (Germany): He and his collegues from pnCommerce are currently working on a complex confugurator module that enables their customer to offer a shopping system for air conditioning system. The user enters all the requirements he has and the module calculates a specific offer.

The Remains of the Day

All in all it was a very interesting weekend with a bunch of really nice people. I think by getting to know eachother personally the relations within the team improve and we established some quite important connections among the module developers. As far as I understood Jørn, he's going to cooperate with Xexpress' Brave Cobra (Belgium) who not only entertained us with the story of his journey that almost ended in Paris and not in Stuttgart, because he used the right highway in the wrong direction. He also turned out to be a skilled singer and guitarplayer as he played some songs in the Biergarten as the other relaxed from the day.

Not quite a Roadmap

One of the important results of the meeting was the evaluation of the state of the .8-development – what is done, what is missing and what needs to be done:

Postnuke .8 will not contain any more features that .7x in regard to kinky stuff like more colorful links or coffee machine drivers. It will be a total redesign of the Postnuke core that gets rid of all the legacy stuff from phpNuke and form Postnuke into a professional framework that offers Interfaces for module developers.

So the main features will be the abstraction of API, Permissions, ADODB aso from the modules. An admin will be able to install the pure core with e.g. Pagesetter only and it will work. This will be a slim, performative core and it is already pretty advanced. But it needs to be completed and properly tested.

The next step will be milestone releases for module developers to test their modules with the new core. These milestones will work and can be uses as example but there will be no upgrade mechanisms for existing sites and no garantee that it will be 100% compatible to the final release. As a result the milestones can't be used in live sites.

Another thing that needs to be done is a total rewrite of all the old modules. They need to be API compliant and templated. The estimated 6 month did not suffice as the work turned out to be more complicated than imagined.

The last problem to be solved is the upgrading process, as for example the data from the Weblinks module will have to be distributed to the new Weblinksmodule, the ratings hook and EZComments.

All this efford will make the system more secure, performative and flexible but it's still some road ahead.

BTW: We are already planning a second meeting next year near Hamburg

Generated on August 10, 2004.

PostNuke Communities Around the World: Denmark   (News)

submissions in our forums. This may not sound like much compared to other countries but considering the size of Denmark... it is.

We have some very competent supporters in our midst of which I will only mention a few (some may have heard about): Øivind Skau aka little (Norwegian Developer of PagEd, Nubel etc.), Franz Skaaning aka lexebus.net (Themes etc.), Jørn Lind (Developer of PhotoShare and PageSetter) and believe me there are a lot more just as competent... thanks to ALL of them and to all the members without whom we (the supporters) would die of boredom ;-)

Besides support in the forums we do a lot of translation and documentation to give newbies the best possible experience with PostNuke.

I can honestly say that I'm proud to take part in the "journey" and although our community may be small... we make a difference for thousands of users in Denmark.

Thanks to hazan for this great idea... this could very well turn out to be the "starter" for some greater things... better awareness of PostNuke's impact globaly... better communication between the various communities... etc. etc.

I would like to take the opportunity to thank all the developers out there, core as well as module and theme developers for their unremitting efforts to support and develop PostNuke and 3. party modules and themes.

Also many thanks to the admins, supporters and users of PostNuke.dk without whom these lines would never have been written!

Best Regards
Kim Enemark
Admin (PostNuke.dk)

Generated on July 8, 2004.

PostNuke Communities Around the World: Germany   (News)

supporters" there are Klaus Petzka (Petzi-Juist), Special Agent Immo Fietz (immof) and my humble self Steffen Voß (ArschMitOhren).

Since May 2002 our site has attracted more than 3,500 registered users, who produced close to 40,000 forum posts and more than 6,000,000 pageviews.

Last year we decided to found a membership corporation. That is done by now, but due to the distance between the various founders and the medium Iinternet, we haven't achieved the ability to actually take new members but that will be solved soon. (Prussian Bureaucracy) ;-)

Our latest event is the European pnMeeting in August. What was intended to be an informal barbeque with our Southern Germans Jörg, Andreas and Frank, evolved into an Iinternational developer meeting. Mark and Drak from Great Britain will also come along with Jörn from Denmark, Brave Cobra from Belgium. I think it's going to be nice and we will certainly present a couple of hundred photos afterwards. ;-

Generated on July 3, 2004.

Page 1 / 3 (1 - 10 of 25 Total)