PostNuke

Site search

Search results

Number of hits: 16

How you can help Postnuke - Part 1   (News)

There are many general CMS, Coding, PHP aso communities all over the web. Tell them what we are doing.

Some examples:
Ohloh.net is an open source network that connects people through the software they create and use. This is were you can meet other developers and see what they are doing. The registered projects are analyzed and can be compared. On the Postnuke project homepage you find some very interesting information about Postnuke. Ohloh.net regards not only the Postnuke core but also some of the better known modules. Thus the statistics reflect the development of Postnuke as a whole. You can add your own repositories there and claim your code. Show those other devs, that you are there and what you are working on.

cmsshowcase.com collects websites and sorts them by the used CMS. There's not one Postnuke site in that list. You should take 2 minutes to submit your best Postnuke work.

If you are registered at xing.com you find a Postnuke Group with more than 50 professional Postnuke users - join us there.

Give presentations about Postnuke at Web Mondays or at BarCamps.

When you look for other CMS at youtube.com you find a load of tutorial videos - why don't we have any of those for Postnuke?

If you have a personal blog: write about Postnuke and what you do with it.

Maybe you have some ideas of your own that you like to share with us. Simply add a comment here!

Generated on September 5, 2007.

Did you know: Implement your own Admin-Theme   (News)

even need a header or and other of this fancy corporate design stuff. I want space for my work. Thus the admin.htm is very short:
[code]









[ Home | Administration | Statistics ]



[/code]
That's it.


Save this as admin.htm to /themes/yourTheme/templates/modules
Add a new Theme Template: Administration/Xanthia/Edit Theme/Theme Template/New Module Template
Name: admin.htm
You have to enter something to the text area. Just one letter is suffcient. It only can't be empty.
Save that.
Add a new Theme Zone: Administration/Xanthia/Edit Theme/Theme Zone/Add New Zone
Name: Admin
Zone Label: *admin
Save that.

Now configure the new zone and choose admin.htm from the drop-down
Activate the new zone.

Done - Your new lean backend layout will always appear when functions are called via admin.php (old-style) or with type=admin within the URL.

We will have a small problem with pagesetter. As it doesn't have a clearly defined backend there's no type=admin in the URL. I always use a small "Pagesetter fix" in my master.htm:
[code]




[ Frontpage | Administration |Statistics ]



normal body
[/code]

I hope this article helps you implement a better backend with much space

Generated on March 15, 2007.

PostNuke Community User Survey Results   (News)

http://www.designs4nuke.com/results/

PostNuke Site Navigation
We are currently working on improving the navigation and look/feel of the main PN site. And with all things it doesn't always go as quickly as we'd like but we expect to launch a preview of a new site in the very near future.

Documentation
This is constant concern for everyone involved in the project. There have been some nice additions to the documentation project over the past few months and I think more than not having documentation, the real issue it is difficult to find. So as we improve the main site we are paying close attention the issue of documentation. So look for improvement in this area in the near future.

Module/Block Repository
Some users requested a "full and complete list of all available modules/blocks/themes" - and we would like to say this is nearly impossible and it it were possible, it would be alot of work to keep it up-to-date. Several years ago we setup PostNuke's NOC as a centralized place to support any PostNuke related project for FREE.

The site offers the following developement tools: CVS (including a web interface), mailing lists, discussion forums, bug/feature tracking, document mgmt, task lists, and a website that provides usage statistics, including the project members, the number of mailing lists, CVS statistics, the number of items in the discussion forums, etc.

We encourage anyone, developers and designers, with a PostNuke related project to register their project.

Register a Project
Check out the Current Projects

UPDATE: The NOC is not perfect. The team knows it has flaws and that support there was lacking so we've added additional admins so no one should have to wait for weeks for project approval any longer.

Current NOC admins Drak Valerio, Frank Schummertz (pnCommerce.com) and IIRC Franky Chestnut (pnConcept.com).

This is our attempt to build a module, block, and theme repository for all PostNuke related projects.

Module Info
There are so many modules claiming to be PostNuke modules and were only half heartedly ported it the first days of PostNuke so beware there have been so many changes in the development over the past four years some modules may not work with the most up-to-date versions of the PostNuke CMS.

Better Forum Support
First let's agree the forum is quite helpful but we recognize there are some areas we can improve. We appreciate the feedback and are looking into ways we can optimize the technology to help us provide better forum support. But don't be shy, once you learn to do something or have an answer/response to a question get involved.

Summary
Finally as mentioned in the comments there were design errors in this initial survey but even with these errors the results are valuable and has shed light on several areas of the project. Again, it's our first survey and we will improve as we create more surveys in the future. There's no such thing as a perfect questionaire but we intend to get closer to perfection in the future. :)

Get Involved
We are looking for volunteers for several positions listed below:

1. Module Review Reporter: Responsible for testing and reviewing new and older modules to publish on the main PostNuke site. Your articles/publications will include your picture, a short bio, and a link back to your site.

2. PostNuke Community Reporter - not every module developer writes his own news at PostNuke and we're looking for someone who is interested in writing up announcements, interviewing developers, and looking for exciting developments in this specific area of the community.

3. International Community Reporter: As a project we want to build relationships with the wonderful international sites and communities. The person who takes on this position will be responsible for writing announcements, and conducting interviews. Your articles/publications will include your picture, a short bio, and a link back to your site.

4. PostNuke Theme Reporter: Responsible for theming news, short how-tos, tutorials, and introducing/interviewing designers. You should be familiar with all the elements of theming for PostNuke including the Xanthia and AutoTheme. All your articles/publications will include your picture, a short bio, and a link back to your site.

5. Special Content/Documentation : We are looking for someone to compare/contrast the features of PostNuke to the following: PHP-Nuke, Mambo, and Drupal. The person should be familiar with both software CMS's to do a clear, concise comparison of features, functions, etc. Also you would have access to the PN team to review the comparison to offer technical feedback and information for accuracy. And the document would be included on the main PN site to help potential users decide which package to use. You would also be provided with a matrix of specifics to compare with guidelines so you wouldn't have to start from scratch. Your publications will include your picture, a short bio, and a link back to your site.

For more information about the volunteer positions contact us at: vanessa at postnuke dot com

Generated on July 12, 2005.

Postnuke .8 - A Preview   (News)

order to improve Postnuke's performance the code was optimized. Additionally Smarty's (Xanthia) and ADODB'd caching can be used.

5. Advanced User Module - All features of Chestnuts pncUserHack will be included in the new user module. Dynamic user date will be kept in an extra module.

6. Mailer Module - Basing upon phpMailer (PHP Libary) external SMTP-/Mailservers, HTML-mails and attachements can be used.

7. Further Database Abstraction - ADODB data dictionary Tools will support installation with various database management systems other than mysql.

8. Advanced Authentication - Additional to Postnuke's user database authentication with other system can be realized. LDAP will be supported and other systems can be added via plugins.

9. Additional Hook Modules - Jörg Napp's EZComments replaces the hitherto NS-Comment modules. Other hooks will be bbcode, bbclick, bbsmile and hitcount.

10. Advanced Statistics - Craig Saunder's AdvStats Module will replace the HTTP-referer and the statistics module.

11. Syndication Feeds (RSS / Atom) - Feeds can be generated from all modules using templates.

12. extended RSS Support - Future RSS support will be using external RSS parser Onyx RSS

13. Global Categories - The new categories module provides cateories in all compatible modules like FAQ, News, WebLinks aso.

14. Collected Pending Content - Basing upon the SnakePending module all pending content will be collected and displayed in a to-do overview.

15. Printing - Printing view supported via special printing template

16. Better Support of current Standarts - All output will be valid HTML strict (hitherto: transitional) and XHTML. This also applies for the the feeds.

17. Support of 3rd Party Developements - Postnuke will in future include 3rd party open source developements. Since the .7 series only featured ADODB as an example, .8 will make use of the Smarty developement, but will also include phpMailer and Onyx RSS.

Together with Jørn Lind-Nielsen globally available pictures gallery Photoshare and his meta module pagesetter, pnCommerce, PagEd, Content Express and all the other great modules this all sounds great, doesn't it?

The ultimate question remains unanswered: When will .8 be released? pnCore-Team manager Larsneo expects a milestone release in

Generated on March 11, 2004.

Interview: Jörg Napp   (News)

How did your Postnuke career start?

In early 2002 I was looking for a CMS for a Website. After some researches I had to choose between PHPNuke and Postnuke, but I chose Postnuke for the besser concept. There was the API, and the big community that convinced me of Postnuke.

What are your tasks in the pnCore-Team?

I work on pnRender, the Postnuke Smarty implementation. Besides I seem to be the only one to keep an eye on static-docs.

When did you start programming for Postnuke?

My first selfwritten modules are fortunatly unpublished. They are only used internally. But my first steps I did in theming.


How do you work?

Most of my own code I write as a kind of "proof of concept". That is e.g. how "Search Statistics" evolved: The idea is to get a statistic on search queries without any changes in the core structure. The resulting modules was written in a hustle - it still lacks an adequate admin interface...


What is the future of Postnuke?

As some your interview partners already said, Postnuke will become more of an application framework. That sounds much like a buzzword, but there's a lot behind that. Apart from the the Photoshare integration into PagEd there's currently almost no cooperation between the modules. The greatest challenge is to offer this kind of mechanisms in an abstract way, so that module developers can use them.

A first step is the hook concept. There should be a lot more hooks available to demonstrate the power of this concept.


What is Postnuke's strength?

The strenght lies in its future. A clean implementation via the API, the development into an application frame and the coming Smarty integration are great oportunities.

The weakness is that Postnuke is quite well documented, but this documentation is hard to find and spread across several sites. The same applies to the modules. The NOC is well intended alas poorly implemented...


I know you have some "side-project", tell me about them.

You can find my projects at http://lottasophie.sourceforge.net.

My best-known Modul is certainly the universal comment module EZComments. I started working on EZComments in connection with my work on the German Postnuke documentation in early 2003. The idea was to implement a documentation including user comments. Content Express doesn't offer comments, so we had to implement them. With Postnuke's hook-concept it was an easy task to attach the comments.

The Title_Hack is a way to display "sensible" information in the title of the browser. The hack has become more popular than first expected. Meanwhile there exist title plugins for a number of modules.

Last but noch least I am involved in the maintenance of My_eGallery. I use this module at my own private site. Several patches and fixes existed for My_eGallery but not centrally available. Patrick (Marsishere) stopped working on MEG so I adopted it and maintain it together with chasm.

The users should keep in mind that my developments often are a "proof of concept". If you find a big, don't keep it - report it in the forum and if anybody changed anything in my modules, I'd like to get it. Feedback is far to rare.

Thank you for the information.

Generated on December 23, 2003.

Web Accessibility - An introduction   (News)

Accessibility - In General
According to the German federal law on equality of treatment of handicapped
persons (BGG §4) ", constructions, means of transportation, technical
commodities, systems of information processing, accustic and
visual sources of information and communicative systems are accessible when they
are accessible and usable for handicapped persons unaidedly, in the usual way
and without special difficulty."
Basically, accessible web pages aren't only accessible for the average user
at his desktop pc with the latest browsers. Web-accessibility is not only considerate
of the various utilities that handicapped persons use to perceive a web page,
but also of users with older browser versions or with special access hardware.
Some figures to give an idea of the size of this group (statistics from Germany):

10% of the male population is color-blind. Web pages with low contrasts
(eg. black fonts on dark-blue background) is for them practically unreadable.
"Press the green button to verify" is meaningless to them.
5% of the population is blind or visually handicapped. They use special utilities
and hardware like Braille-displays or screenreaders.
11% of the population is older than 65.
5% of internet users don't use Windows, but MacOS, Linux, PDAs or cellphones.
Numerous sites, especially large ones, still have up to 20% users visiting them through 4th generation Netscape
browsers.

If you don't only aim at gamer kiddies with 19" displays, you should start
thinking about whom you exclude with your killer design. A blind person for example,
who cannot use a company`s internet pages, will choose another vendor. But what
can a blind person do when his registration office's internet site is not accessible?

 
The Legal Side
Since May 1st, 2002, the ordinance for accessible information technology
(BITV) became effective. All federal institutions are obliged to make their internet
sites accessible - in the sense of the word used in this article. Governments are called to work out
similar state laws which oblige state and municipal institutions to follow accessibility guidelines.
BGG and BITV are based on the EU action plan "eEurope 2002", initiated
in 1999 and finalised in 2000 by the European Council. eEurope aims at 3 main goals:

A cheaper, faster and more secure internet
Advancement of internet use
Investment into persons and abilities

The latter comprises the participation in information technology of as big
parts of the population as possible. Summarised under the term "eAccessibility",
access to eCommerce, eGovernment and so on is to be made possible. This was to be
implemented with the adoption of the Web
Accessability Initative's guidelines.
 
Guidelines for Practical Use
Already in 1999 the World Wide Web Consortium (W3C) released the Web
Content Accessibility Guidelines 1.0 and made it quasi-standard for accessible
internet design. Since then many of the rules have proved too restrictive,
irrelevant, incomprehensible or simply not representative of the state of technology
anymore. Some of them even turned out to be not internationally applicable.
For these reasons a version 2.0 is in the making. Since v. 2.0 is still in development, this
text will only relate to WCAG 1.
The Web Content Accessibility Guidelines 1 are split up into 3 priorities:
Priority 1: A Web content developer must
satisfy this checkpoint
Priority 2: A Web content developer should
satisfy this checkpoint
Priority 3: A Web content developer may satisfy
this checkpoint
If you violate a regulation of priority 1, many people will be excluded. A violation
of priority 3 regulations excludes only few. There are 14 main regulations, with
the priorities attached to all of their subcategories:

1. Provide equivalent alternatives to auditory and visual content.
2. Do not rely on color alone.
3. Use markup and style sheets, and do so properly.
4. Clarify natural language usage.
5. Create tables that transform gracefully.
6. Ensure that pages featuring new technologies transform gracefully.
7. Ensure user control of time-sensitive content changes.
8. Ensure direct accessibility of embedded user interfaces.
9. Design for device-independence.
10. Use interim solutions.
11. Use W3C technologies and guidelines.
12. Provide context and orientation information.
13. Provide clear navigation mechanisms.
14. Ensure that documents are clear and simple.

There is also a W3C-list of suggested Techniques
for Web Content Accessibility Guidelines 1.0.
 
Testing Accessability
Several tools exist for testing the accessibility of your website:
http://www.w3.org/WAI/WCAG1AAA-Conformance
http://bobby.cast.org/
http://www.cynthiasays.com/
As a result you receive 3 levels of conformance:
Conformance Level "A": All Priority 1 checkpoints
are satisfied
Conformance Level "Double-A": All Priority 1 and
2 checkpoints are satisfied
Conformance Level "Triple-A": All Priority 1, 2,
and 3 checkpoints are satisfied
Internet sites of German federal instititions have to fullfil Double-A conformance.
Recommended is Triple-A.
 
Not only for handicapped persons
A main problem with accessibilty is that a web site must cater to the needs of two different interest groups: On the one
hand, handicapped persons that already have to use the latest browser version
in cooperation with their hardware and utilities, and on the other hand, users
with old browsers.
This problem is however a perfect focus area for the idea behind CMS-es: The separation
of content and layout. It becomes possible to detect the user browser client, and in a manageable way offer
a classical HTML 3.0 page or a modern HTML 4.01 page, with the same content.
Practically speaking, modern web design means above all to do without tables for layout
use. Tables have always been a crutch when it comes to creating layout, and more so today than ever.
Modern layout is created via CSS. A nice example of how accessible
design can be created can be found at http://www.inknoise.com/experimental/layoutomatic.php.
This also shows that accessible web sites do not have to be plain text.
Tables should only be used the way they were originally intended: For example
as an address table with columns and rows, column heads and so on. Used this way, also
the tools of blind persons can make sense of them.
 
Accessibility and Postnuke
Making a Postnuke site accessible is practically impossible: While themes can
easily be created with CSS, you will fail at the modules, which excessively
use hardcoded tables. Not until the introduction of the Xanthia Templating Engine
in Postnuke 0.8 will it be possible to make your site accessible for everyone.
Then you can start developing accessible templates for all API-compliant modules,
something which is currently possible only with third-party modules that use smarty, like
PostCalendar or pnCommerce.
Until then the possibilities are limited when it comes to making at least some of your content
accessible: The AvantGo module - originally designed to make the News accessible
for PDAs - can also be used for accessibility. There seems to be an extended
version of the Avantgo named Extravantgo, but during my researches the download
page was inaccessible ;-)
German version of this article: post-nuke.net

Generated on October 8, 2003.

PostNuke Is Alive and Well   (News)

launch of demo.postnuke.com, it should be up sometime this week. But if you are the adventurous type you can always download the
latest/greatest from CVS (http://developers.postnuke.com) but remember this is only for review purposes and shouldn't be used on
"live" sites. If you're unfamiliar with CVS you can get more information here:http://noc.postnuke.com/docman/view.php/5/2/CVS%20Access%20Guide.htm
And we encourage those interested in discussing the upcoming release we have setup a forum
on the NOC and you can access it here: http://noc.postnuke.com/forum/forum.php?forum_id=227
There has also been
some concern regarding the templating engine, it is true we lost work on the
PTE (Phoenix Template Engine) but the XTE (Xanthia Template Engine) will be as
powerful as the proposed PTE. Both
are based
on SMARTY which
brings a wealth of features to the table. We've created a compare/contrast
chart for you to review so you can see that the templating
engine will deliver on the promises made in the past and we're confident you won't be disappointed
with the new engine's features and stability. (Note:
XTE
is currently in CVS for review.)

In
the past promises have been with the fullest intentions of keeping
them -- but as we all know life happens and plans change.
But as said before we've picked up and are marching (coding) forward.
And just so you know the progress is exciting, and that sense of
excitement is back in the project. We are having fun and in my
opinion this is the most important part of the project because in the end that's what everyone gets in return, that sense of accomplishment and the joy of doing it. So as a team we are working
towards, a 1.0 release.
Other changes have been made behind the scenes too. For example, Harry has passed the day-to-day activities of managing the project to me. He is still actively involved in the project in the background and in an advisory role. Moving forward things aren't going to change from the original vision of the project but we are looking toward the future as technology and developments change. Keeping up-to-date on new technologies will allow us to integrate any new developments into the project when it makes sense.
Finally, the community of PostNuke is what makes it unique, and therefore I consider keeping you informed about all aspects of development an important part of being a member of this community. So announcements will be made on a monthly basis under the category pnUpdates. We're all working toward the same goals, so let's all have fun in helping to create software that provides each of us with the kind of solution that meets our needs.

Development Information Links
PostNuke
Task Tracker
http://noc.postnuke.com/pm/?group_id=5
Reporting
Bugs
http://noc.postnuke.com/tracker/?atid=101&group_id=5&func=browse
Feature
Requests
http://noc.postnuke.com/tracker/?atid=104&group_id=5func=browse
Interesting
Statistics:
May 2003 PostNuke Downloads: 14,884
 
Informational
Links
What
is CVS (Concurrent Versions System)?

Generated on June 9, 2003.

Logging you in. hang tight!   (News)

last few months, there have been lots of rumors about the future of PostNuke, and also the failings of PostNuke as it is today.

We at Team PostNuke think that on this occasion of hitting 10,000 members, that we should point this out to the world, let you all know that PostNuke is alive and doing great, the numbers speak for themselves.

If you wanted to have a peek at our pnForums Stats page, you'd be surprised to find the numbers speak quite clear as to the success of the forums, and our support structure we have in place. You could also, if interested enough, have a look at our pnForums Memberlist on those forums, to see in more detail, how many people actually even had to post. Many hundreds have not. Are they lurking? Maybe. Did they find what they needed while they were here, went back to their own sites with the information they were seeking and continued to work on their sites? We would like to think so.

There are many other Content Management Systems out there, good ones, one's that are new and up and coming, others that have been around for many years and have spawned forks from them going in new directions, as is the history of PostNuke. But our numbers continue to grow by leaps and bounds. This says something, this says that PostNuke is "the" choice of users worldwide.

Many of you that have been around a long time, know that there have been slow times and fast times alike around the world of PostNuke, this is the way of open source I believe. Just when you think everythings going great, something gets in the way to slow things down. We have had a few of these kinds of set backs in past months. One thing is sure though, as people come and go, there remains one constant thru it all, that is, the PostNuke project itself.

This project has brought people together from all points of this small world we all live in, many new friendships have been born, some have been lost, but the idea that the project itself should live on has always been there at one point in time for all of us.

In eight months over 10,000 people have logged in for the first time on those forums to see what PostNuke was all about, many more new "pnUsers" do each day.

There are some CMS projects out there that have no forums at all, either they don't have the time to be bothered with their users, wanting to help them succeed and use the software, or, they just don't have the support infrastructure that we do here at PostNuke. This is just one of the many great things about this software, that is the support you get with it.

PostNuke is not a finished product, but you'd really find that hard to believe by looking at how many use it worldwide in many, many different countries and languages. We are all here because we like the software, we like the tools that have been created by the wonderful teams of the past, present, and future developers of PostNuke. I for one, want to thank them all for their contributions.

In the coming weeks as has been promised, PostNuke .726 will hit the streets running. This will be our last release until .80 which has not yet been announced as to when it will be ready, but I can assure you all that it is being developed by some great developers, and you may have even visited the test site by now, which is running on the new code. The improvements are great, the new tools being developed right now for that .80 release promise to be exciting for us all. You can expect to be supported when it gets here.

PostNuke is alive and doing great, the software is constantly being developed, and there's room for you to get involved. We are always looking for new pnUsers that have an interest in working with the team.

Our forums shine above the rest of those other Content Management Systems because of the pnCommunity and the way we support each other on a daily basis. Yes, there have been times when there's been bad press posted, nay sayers if you will, that have spoken up to say they are unhappy with how things are going, well, we're sure sorry that some feel this way. Look around, we're trying, we are succeeding, PostNuke is still growing, it's growing every day.

As always, you'll find the support you seek on these forums if you are a new user. If your a seasoned veteran, come join us, get involved and help out on the pnForums, help someone else get going with their very own PostNuke site. Together we will take PostNuke places it's never gone before. The interaction of developers with users here on these forums IMHO, is second to none. We take pride in the support we give those that come to ask for help.

As with everything else branded with the name PostNuke around here, the forums are constantly being reworked to provide a better place to come to and get help fast. Changes will be made there as often as necessary to insure this continues. If you'd like to get involved, and you know your way around the PostNuke software well, we invite you to pitch in, if you don't have time to drop by the forums every day, maybe you have the time to put together tutorials of things you know about. The Tutorials and Solutions area is a great place to publish your work, and it will surely help others coming in behind you, new to all of this.

We want to thank all that have helped out these past 8 months on our new pnForums to make them the success that they are, and we invite you all to look forward to the future of PostNuke.
Still growing, ever changing, filled with drama and ups and downs, this is PostNuke.

Welcome to PostNuke we're glad to have you with us.
Logging you in, hang tight! :)

Generated on June 5, 2003.

Statistics Issues   (News)

5x higher than what Stats in PostNuke was reporting. When comparing to server logs, it appears it maybe even worse than that.

I was wondering if a more complete Stats module is in the works, or available. Maybe one that can report on Unique Visits, Page

Generated on August 6, 2002.

Hosting Service for PostNuke sites   (News)

http://blockhouse.zzine.org/

e.g our blue package:

Bluehouse Hosting Package - $16.95/mo (12 months only $14.95/mo!)
For beginner webmasters who powerful set of tools to develop with!


100 MB's Storage
10 GB's Transfer
Online Control Panel
Unlimited E-mail Accounts
3 Virtual FTP Accounts
Unlimited MySQL Databases
Unlimited E-mail Aliases
Unlimited Auto Responders
Unlimited E-mail Blockers
Unlimited Mailing Lists
Password Protected Directories
FrontPage 2002 Support
Powerful Shopping Cart
Unlimited Discussion Forums
Full CGI Access
WebMail System
Complete PHP4 Support
Detailed Web Site Statistics
Redundant Nightly Backups
SSH Secure Shell/Telnet Access
Pre-Configured Java/CGI
Perl 5, TCL, C++, Python, Java
Static IP address
Access to Raw Domains Logs
Free Search Engine Submissions
Free Real Audio and Video Support
99.9% Uptime Guarantee

You can apply on our page if you're interested...

cheers,

CHi

Generated on July 19, 2002.

Page 1 / 2 (1 - 10 of 16 Total)