-
A Warm Welcome to Our Newest Member, Mateo Tibaquirá Palacios
(News)
-
Welcome Mateo, tell us a little about yourself. Who are you,
where are you from, and what do you do?
My complete name is Néstor Mateo Tibaquirá Palacios, but I prefer to be called Mateo. I'm from Colombia, a very beautiful country with some horrible problems; balanced, eh? I live in Popayán, where I'm finishing Electronic & Telecommunications Engineer Studies with an emphasis in Telematics (Information and Communications Technology). I chose Telematics because I like to program. Growing up, I did not have a computer, and from the distance I hated the idea of using a command line console. Now, it's different; I love my Ubuntu with the Yakuake console; and Eclipse PDT rocks!
At the University, I discovered that I had sufficient skills to write software. I began programming in C++ and Java some time ag
Generated on January 26, 2008.
-
Two new core team entrants
(News)
-
is going to play the main role in renewing the PostNuke language system for .9, we are glad to have an expert for these things onboard now.
Philipp Niethammer (philipp.ni) is already known as the author of pnBook, the first pnRender-based guestbook module. Recently he wrote several additions, i.e. a ListUtil for managing different types of lists (flat, nested aso) and FilterUtil for comfortable filter definitions including Pagesetter. His newest work is an interface for the logging system DBUtil provides so that one is able to manage the change history of a particular object. Along the way he also fixed some bugs in DBUtil and ObjectUtil, so we decided to get him into the team.
Thanks to both guys for their engagement and contributions to the project
Generated on September 26, 2007.
-
Recovery Console for PostNuke .8+ - Now Available
(News)
-
Onboard Tools
Configuration OverviewDisplays many site config settings including module, block and theme detection.
Database Access RecoveryRe-encodes database credentials for the config.php file.
Theme RecoveryResets default site theme and/or resets user-applied themes.
Disabled Site RecoveryYou wondered what turning your site off would do...now you know! This utility restores the site to the "on" state.
Modules Module RecoveryDeletes any Modules modules entries found in the database and freshly installs the Modules module to the System category.
Blocks RecoveryA chart displays important block data and allows for disabling and/or deleting any content blocks. Changing the state of multiple blocks at a time is supported.
PostNuke Site SearchA built-in search bar searches the PostNuke site for content by keywords. Searches for matches in the following modules at this time: pagesetter, users, downloads, weblinks, comments, ezcomments, all news stories/topics, and all forums.
PHP InformationPHP info is displayed by section via a tidy menu.
About The ApplicationA dedicated page that displays licensing, credit and other general information.
Additional Features
Cross-browser-compatible CSS layout.
Highly accessible onscreen display.
Visual, interactive, informative navigation.
Various (but few) core images used for aesthetic lists.
Succinct onscreen instructions for each utility.
All actions require confirmation and provide error/status messages.
All forms re-populate themselves upon error.
Applicable current settings are displayed on every page, before and after recovery.
Security
Utilities that are not needed intelligently disable themselves.
User input cleansing.
Filename can be changed without breaking the application.
Time-sensitive application lockdown.
Gracefully Degrades When
PostNuke version is less than .8x.
PostNuke initialization fails.
Application is under lockdown.
Application is uploaded to incorrect location.
Of Other Interest
Written as a PHP class.
Extremely commented code.
Output source is XHTML 1.0 Strict; tidy and skimmable.
Quietly runs with E_ALL enabled.
A big thanks to all who contributed to the original PSAK, which was the strongest inspiration behind this Recovery Console, and to those who contributed with ideas, feedback and testing of the PNRC, thanks for your time and effort!
Download the PostNuke Recovery Console now!
Generated on May 10, 2007.
-
PostNuke Recovery Console - Additional Feature Requests
(News)
-
then perform any repair operations by visiting the file in your browser and following the onscreen instructions, same as the PSAK.
One major improvement over the PSAK is that the Recovery Console has a countdown timer built into it which will only allow the application to be used for xyz amount of time, after which the file automatically locks out further access to the code therein. A realtime graphical timer (Javascript-based) visually shows you how much time you have left to use the Recovery Console. (The Javascript is purely for display purposes, and not relied upon for security.) As the PostNuke system does not make any checks for this Recovery Console, it could easily be left on one's server accidentally and thus, misused. To this end, the lockdown feature might be of some comfort.
A few other items of interest about the Recovery Console:
Aesthetic, CSS-based layout. Nothing hacky, very straight-forward classes.
Consistent navigation.
Fixes that require database, when no database present, are visually disabled for clarity.
Each utility shows the current status of what it's about to fix, before it fixes it, and after.
Inline explanatory texts help you make the proper fixes.
Overview of recovery-related site settings.
Informational page about the application.
Status messages tell you exactly what's going on.
Large countdown timer lets you know how long you have left to use the application.
Self-contained.
Works with PostNuke .8+ (including MS2+)
Highly accessible.
Specific fixes onboard at this time mirror those of the PSAK:
Encode Database Credentials
Toggle Intranet/Internet Usage
Broken Theme Recovery
Permissions Recovery
Disabled Site Recovery / Turning Site Back On
Modules module Recovery
The code is written so that other fixes can easily be added and thus, if you have any suggestions for other utilities to incorporate into the PostNuke Recovery Console, please share them! I'm at a point where I am commenting the file now, and that will take me a least a week more to finalize I suspect, so please post any ideas for fixes you'd like to see and I'll try to get them in for the first release.
Note that this application can be downloaded from here at the NOC, but that it will take a week or 10 days for me to get the first release uploaded.
Cheers,
- Ala
Generated on April 20, 2007.
-
Microformats in PostNuke
(News)
-
pair of span-tags and give it the class "given-name". The same you do with the last name - the class-name would be "family-name".
You can mark all parts of an address in this manner. The result is a program that knows which class is what, can split up the address and work with that. For example you can move an address to your Outlook Address Book with a single click (see Live Clipboard).
There are several of these Microformats. Only few a are fully specified by now (hCard, hReview and some formats for the description of links.) But there are about 50 in discussion.
As an example for the technique and the way you can implement it into your own modules or templates I designed 3 publication types for Pagesetter: hCard, hCalendar and hReview. You can import them into your Pagesetter installation and look at the templates. You can also build your own address books, calendars or reviews with it. I would love to see them working on the one or the other site.
Links:
microformats.or
Generated on February 3, 2007.
-
Development Update, January 2007-01
(News)
-
be productive and succesfull for all of us. And of course: a finished .8 version of PostNuke is something we are all waiting for.
MileStone 3 is waiting around the corner: A feature freeze so far has speed up the progress and only a few bugs are blocking a release. The next development update will probably be submitted after the MS3 release.
OK, here goes!
API functionality
Introduced is a pnShutDown function to gracefully terminate the application framework. This now replaces all use of exit or die and also fixes some oddities caused by PHP's shutdown process.
Mark has replaced all old themesideblock function calls with newer API call pnBlockThemeBlock. Furthermore, he has added a raw text option to the PageUtil::registerVar (former pnPageRegisterVar) system.
The AjaxUtil is now using internal json_encode() if PHP >=5.2.0.
Object Library and classes
For the SessionUtil / RandomUtil, Drak has put his hands on improving the randomness in the generation of the AuthKey and passwords. This is done by extending the possibly characters used, and the length of the key (length also now being random).
Also, the AuthKey generation makes now use of the (updated) RandomUtil class. A big advantage is that the random data generation is done in one place, so a change will affect the complete system. This is actually with the complete Object Library: changes can be made in one place with the benefit that all calls are updated.
The DBUtil has now a renameTable method and a renameColumn method for easy manipulation of table properties without having to worry about SQL code. The latter (renameColumn) is a quite new function, so there may be some adoDB bugs.
Finally, pnPage.php is converted to the PageUtil class. This means that any 3rd party module developers should update their modules to make use of the new class. A call to (for example) pnPageSetVar('title', $title_var) must be updated to PageUtil::setVar('title', $title_var). The pnPage.php does not remain for backward compatibility. Examples for the needed changes can be found in SVN submission 21099. The Wiki documentation for Page variables still needs updating however.
pnForms: functionality and documentation
Jørn has been updating the pnForms toolkit extensively. Most important is hat the documentation in the files is more complete, and the Wiki documentation page has been updated. A summary:
Added authkey checking to pnForms.
Added min/max validation for integers.
Changed "classHtml" to "cssClass" in "pnForm" plugin for consistency with the other classes.
Added a language selector "pnFormLanguageSelector".
and much more...
All plugins now render unknown parameters "as is", so you can add "onclick" and such like that the system doesn't know of.
System modules: Categories, Search and Blocks
In the Categories system, there has been added support for a 'field' parameter.
The search module is as good as finished, and also displays a sum of all search hits too. An additional parameter is added to allow for searches that aren't going to be performed on a DB. Finally, it is now possible to search in RSS feeds.
The Blocks module has been updated, and now has a user friendly functionality for drag-drop between block positions and placements in one screen. This is done with Ajax technology (thanks Frank for simplifying and enhancing this), so javascript should be enabled to use this (non-js fallback available). Furthermore a XML/XSL block has been added (a generic xml/xslt block and modifier).
ValueAddons modules
Faq: implemented custom short url handler and permalink structure
News: implemented cache handling
Feeds (was RSS): implemented categorisation in admin panel, added short url handler, added title field.
Also, the RSS module is renamed to Feeds to better reflect it's purpose and to prevent clash with rss theme when using directory based URL's.
TinyMCE: Upgraded tinymce to v2.0.9
Reviews, Referers, Stats: Converted to API and pnRender compliant module, updated table management code.
pnRender Plugins
Mark has added an output filter in order to auto-magically title the administration pages, which makes navigation a bit easier.Also, A
Generated on January 21, 2007.
-
A Time to Grow and Change: PostNuke Software Foundation Formed
(News)
-
German PostNuke Foundation, currently represented by Andreas Krapohl, Drak of HostNuke, and Vanessa Haakenson. (see short bios below)
The functions of the founding members serve a managerial and strategic function, ensuring the project goals and directions remain constant and true to the open source philosophy, quality coding, collaboration, and open standards. It's important to stress you are not required to be member of the foundation (there is currently no membership option) to contribute to the project.
As a result of our combined experiences over the last four years the founding members agree the best way to move the project forward is to have a PN Steering Committee* (see details below) consisting of members of the various teams chosen from well-known, long term active community members and developers.
The job of the steering committee will be to handle the day-to-day running of the project and will be chosen by the founding members. The announcement of the appointments will be made within the next 10 days.
In closing, in the coming days look for an announcement regarding the PN Steering Committee and over the coming weeks look for announcements about a new look/feel for main PN site, a formal site for the foundation (read current bylaws here: http://www.postnuke.com/foundation/) and an updated project road map.
We have set up a forum for further discussions regarding the foundation here.
Viva la PN!
Sincerely,
Board of Directors
PostNuke Software Foundation, Inc
Harry Zink through Fizbin, LLC
Mark West, Lead Developer
German Postnuke Foundation, currently represented by Andreas Krapohl
Drak through HostNuke
Vanessa Haakenson
_________________________________________________________
PNSF Facts & Information
PostNuke Software Foundation
Non-profit registered in the State of Delaware
PostNuke Steering Committee
Advisory body made up of members of the various teams and responsibilities include:
Community management & resourcing
Determine software project priorities
PostNuke software development and direction
Provide policy recommendations
Approval of development plans
Goals/Objectives:
The Corporation is a non-profit organization organized and operated exclusively for charitable and educational purposes. No part of the earnings of the Corporation shall ever inure to the benefit of or be distributed to any member or individual having a personal or private interest in the activities of the Corporation.
Board of Directors
The Board of Directors serve a managerial and strategic function, ensuring PostNuke remains constant and true to the open source philosophy, quality coding, collaboration, and open standards. The following people/organizations serve as initial members of the corporation:
Fizbin, LLC (Harry Zink)
One of the original founders of the project, Harry has been a constant, continued project supporter. He works as a systems administrator for a large entertainment corporation and lives in Los Angeles, California. He has a Ph.D. in psychology and loves to travel to Thailand for the food.
Vanessa Haakenson
Is co-founder of Distance-Educator.com and has been an active participant in PostNuke since July 2001 consulting on usability issues and acting as a PN evangelist to the educational community. In November of 2001 she started the site Designs4Nuke.com to consolidate and share all the information and resources regarding theme design for PostNuke. With a Master's Degree
in Educational Technology she brings a unique perspective to the project having developed web based products focusing on usability, standards, documentation, and community. Over the years she has presented at conferences about PostNuke and has authored articles on effective information design. She recently moved with her son from San Diego, California to Woodland Park, a small mountain town in Colorado.
HostNuke Ltd. (Drak)
Drak has been with the project since July 2001 and was the first to create hosting accounts with PostNuke preinstalled as a way of making it easy for new users to get started. He has 19 years experience in the computer industry and devotes most of his time working for a humanitarian charity. He donates equipment and colocation to the project and is responsive for all server level security and administration.
Mark West, Lead Developer
Works as the computing officer for Systems and Operations for Kingston University and lives
in
South
West
London,
UK.
He
specializes
in
directory
enabled
enterprise
computing,
he's
taught
programming;
techniques,
data
structures
and
algorithms
to
first
year
undergrads
at
Kingston
University
and
adheres
to
a strict
style
of
programming
- heavy
on
layout,
consistency
and
style.
Believing
the
benefits
of
this
strict,
consistent
and
academic
approach
to
coding
is
a stronger,
more
stable
and
bug
free
end
product.
He
has
been
using
PostNuke
from
the.70x.
series
and
is
the
lead
developer.
German
PostNuke
Foundation
(Represented
by Andreas
Krapohl)
Andreas
Krapohl
[aka
larsneo]
is
President
of
the
German
PostNuke
e.V.
foundation
and
is
the
head
of
IT
for
a local
newspaper
in
southern
Germany.
Has
been
with
PostNuke
since
almost
the
beginning
- at
first
with
some
translation
stuff,
then
as
module
author
(phpBB_14)
and
since
early
2002
as
a core
developer.
Main
focus
is
security,
usability
and
accessibility.
He
believes
a solution
should
be
simple
and
elegant.
Current
Jobs in PostNuke
Structure
Development & Quality
Assurance
Communications & News
Moderation
Forum
Moderation & Support
Documentation
Language
Project
Marketing
Generated on August 18, 2005.
-
Interview: Lee Eason
(News)
-
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 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
Generated on January 14, 2005.
-
Suggestions Needed for Conversion Script
(News)
-
So far I have:
NSN-Nuke
OpenSiteManager
PHP-Nuke
PostNuke
Xoops
Invision Power Board
phpBB
phpwcms
Mambo
Xaraya (not sure if I'll support that yet, maybe wait until it's 1.0 release, since it has so many beta releases)
If you post a CMS or forum, please also post it's URL as well, so that I can download it to look at the SQL dump.
Thanks!
Generated on May 28, 2004.
-
phpMyadmin Version 2.6.2 Release Candidate 2: many enhancements and Bugfixes
(News)
-
Features of v2.5.6 RC 2: (here the Changelog):
-General code optimization by removing old PHP3-compatibility
-Make default functions configurable
-Visual scratchboard: show column names
-Show overhead in table list, allow to check all overheaded tables at once
-Export: can suppress dates information
-MySQL error messages improved formatting
-Printview: display linked values and other relational features
-Export: allow delayed INSERTs, and support for UPDATE and REPLACE statements
-Show result of last SHOW query when using multiple queries
a Online-Demo
Generated on February 22, 2004.