PostNuke

Site search

Search results

Number of hits: 67

Welcome to Zikula   (Admin_Messages)

system (CMS). It is far more secure and stable than competing products, and is able to work in high-volume environments with ease.
Some of the key features of Zikula are:

customization of all aspects of the web site's appearance through themes, with support for CSS stylesheets
the ability to specify items as being suitable for either a single language or for all languages
the best guarantee of properly displaying your web pages in all browsers, thanks to full compliance with W3C HTML standards
a standard API (application programming interface) and extensive documentation to allow for easy extension of your web site's functionality through modules and blocks.

Zikula has a very active developer and support community at zikula.org.
We hope you will enjoy using Zikula.The Zikula development team
Note: you can edit or remove this message by going to the Administration page and clicking on the 'Administration messages' entry

Generated on December 20, 2008.

GSoC Interview: Carlos Mauro   (News)

2. What attracted you to the Google Summer of Code as a programme, and PostNuke as a project?

I looked at Google Summer Code as a great challenge. But I do not dare. Until this year, if I did. I applied to several projects related to the topic of usability. And because apply to PostNuke some years ago I work as freelance. Develop some portals for small businesses in my country using postnuke and other CMS. PostNuke is attractive because this was installed in a single attempt. I was surprised. So I think support.

3. Tell us about your project, and how you hope it can benefit PostNuke?
I'm copying what we present in my proposal:

The criteria for the evaluation usability are:
Comparison of controls on Good Practices or patterns Usability on the Web.
Include improvements within the Framework.
Create a guide to improve and documenting findings to the community PostNuke.

a. Usability
To improve the usability of Postnuke i will work graphical interfaces suggested some of the modules and the framwork which are used in the forms. Attempts to put in these modules some good practices and standards for Web usability.
I will Work with what is necessary XHTML, CSS, Ajax whether it is possible to implement and methodically.

b. Accessibility and conformance
For the accessibility i take the the Guidelines and techniques(6). After the programing process. I will make a list for test usability. I will Choose 6 to 7 cms users to test usability with the corrections. The proceeds will help create iterations for each test.

c. Maintainability
Maintenance may accelerate taking intoaccount that at the end of the draft the conclusions will be made in the form of best practices for Web usability postnuke. I will help in the incorporation and supporting of usability guide line in other modules PostNuke.

In the forums I will clarify the tasks of the project and also its scope.


4. What do you personally hope to gain from participating in the Summer of Code with PostNuke?
Many, many experience in knowing more about how a community of developers interested in do make a good product. Learning from good programming practices and especially knowing more about web usability. Of course Social Recognition.
I want postnuke as a milestone in the renewed Internet.

5. Can you see yourself contributing your talents to Open Source projects following the SoC? Will you continue to work with PostNuke in some capacity after the programme has ended?
The GSOC ends after a month of my graduation from college. I hope to finish that time almost all my tasks in the project. I would like to leave a module to test usability. I feel a duty to contribute to the community. I am confident that the project can achieve more significant improvements in its next release and then create or generate support the development of future lines. It should not be discouraged postnuke which has short market ... we see the top, be with them and then jump to heaven.

6. Is there anything else you’d like to say now, as the programme begins?
I would like to see other issues as the framework and its implementation in business or insert google app into the framework. I would like to make a strategic planning for IT postnuke. Devising strategies to make the best CMS, simply: Easy.

Not only is needed to schedule some things to achieve a well-accepted product.Need to know that is what the user wants in the next 5 years and venture into that vision. So I count on your support to work with postnuke .... And of course do my project as realistic as possible in these 3 months in the hope that is of benefit to all.

Lastly, thanks for your time – we in the PostNuke team are excited about the Summer of Code, so thank you for taking part and choosing PostNuke!

We are going ... postnuke to make the Best CMS, the easiest. GEN a social network that seems to make FaceBook a grain of sand in our seas.
I will continue reviewing more documentation and adjusting the project to postnuke with the help of my mentor Steffen Voß and

Generated on April 27, 2008.

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.

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.

HTML for Module Developers - A Discussion   (News)

ideas about good HTML. I haven't seen any layout tables for months. Many module devs even try to put semantics into their work.

No matter there are some things, I'd like to point out and discuss with you.


"Divitis" is the name of a HTML coding style that puts every possible Tag into div-Tags. I personally only use divs for the general positioning of my layout: header, content, left block, right blocks, footer. Anything else doesn't need divs around it. You can position every other tag in any way you can position and style divs.

Some of you use a separate class or ID for every single piece of content. This makes the code seems bloated and hard to maintain. Please use only as few classes as possible.

Some modules have a very great design but it doesn't really adjust to my own themes. Please don't define the style of h-tags, p, ul, ol aso. in terms of color, line-height or font-size and style. I think most webmasters already have a site wide definition for these tags and want all h2-tags look the same all over the site.

Use the CSS inheritence system for a slim style sheet: In .8 everything your module produces is put into a div:

[code][/code]

So if you want to style you module use e.g.:

[code]#pn-maincontent.pn-module-YOUMODULE * h2 {}[/code]

to make every h2 look the same in your module.

Please don't use h1 - h1 is the site's name.

These are no official guidelines - only my personal opinion which I wanted to discuss, in order to develop a list of tips for

Generated on November 21, 2007.

Branding - What is PostNuke really?   (News)

Joomla was chosen as the "most lowed" CMS - I am asking how PostNuke should relate itself to Joomla (and other CMS's for that sake).

PostNuke .8 and Joomla are, as I see it, quite close to each other. They both boost table-less designs, templating, complete use of CSS, user friendliness, modular etc. etc. So what's the difference? There's surely a lot of technical stuff to be said about this, but I'm looking at the marketing side this time.

The three most obvious positions has already been taken: the most-loved/best CMS (for beginners), the most professional, and the best blogging system. So how should PostNuke be positioned? If we try to head for the "best CMS" then we compete directly with Joomla and that's going to be a hard battle to win: Joomla has (apparently) gained a lot of momentum recently and competing with that is difficult.

So is there another position for PostNuke to take up? What should be the one-line slogan for PostNuke?

One position could be: "PostNuke - the most versatile CMS". That is not really correct wrt. Typo3, but it fits with current work on 1) cleaning out the PN core, and 2) making different distributions of PostNuke, and it sounds more "for the end user" than calling PostNuke an "application framework" (which the core is). You can get a complete blogging system for PostNuke, you can have a community site, you can make a photo site, and you can make something completely different, like for instance www.turmappen.dk which only uses the PostNuke core and some home grown modules (never miss a chance to make some advertizing for your website :-)).

So, Guite, hurry up and make the best of EasyDist! I love the concept - it should really be available for use on postnuke.com (and I know there's some technical details that still needs to be fixed for this to happen).

The next question is - who is the audience for PostNuke? Here is a problem since PostNuke all of sudden becomes a multi purpose tool - with different audiences for different distributions. How should that be managed? Honestly, I don't now, I'm not a marketing man. Hopefully some of you out there has some good suggestions? Or maybe a completely different view on the issue?

PS: I'm on vacation right now, so do not expect a quick response from me

Generated on September 15, 2007.

PostNuke .8 RC1 Released   (News)

PostNuke 0.800 RC1 Core Only Download
Download (ZIP)
MD5: 17d7f2eb16bf4dd886695adefab0e1f5
SHA-1: 624dcb1b29c17150e341878c727ddac83fadeb54

Download (TAR.GZ)
MD5: 9807fe2f3e0ef9f7fa88a3bbb0426815
SHA-1: 354edfc9eff87f77713bc1750cdc77144fcf0bff


PostNuke 0.800 RC1 Full Package Download
Download (ZIP)
MD5: 15718c1d68223bf5fc69b144666741f8
SHA-1: e1901b3d06dce1b82f2dfcde4d2da74e7afb9cf8

Download (TAR.GZ)
MD5: 1d983e5fd18907022fbec598c4ae7111
SHA-1: afb25ef625ce6e1564c40faf1cb29b3c1ea0ee13


PostNuke 0.800 RC1 ValueAddons Download
Download (ZIP)
MD5: 38879b481640289b7b6a605af41638a1
SHA-1: aa10e8f79d038b667aa8638347d3d12a999d8e99

Download (TGZ)
MD5: 4adc34945ae0cf42b3f96408bd21d17c
SHA-1: d4f80e0478bef1721eb29484024a9ed7a1a2e025


Please feel free to use the article below to publicise PostNuke in any web development communities you belong to. It is also published here on community.postnuke.com.


Simon BirtwistleHammerHead

About PostNuke

The PostNuke Application Framework provides a high performance, secure and feature complete framework which both website administrators and web developers can use to great effect in creating unique and attractive websites. PostNuke can be used as a CMS, adapted to blogging, ecommerce or community websites, or for more abstract tasks. It is easily adaptible, extensible and can handle situations in which performance and security are paramount. In this way, PostNuke is a reliable and robust choice for any website administrator.

The most recent version of PostNuke is 0.8 RC1, which represents a feature complete 0.8 version. Once the release candidates have undergone full testing and any remaining bugs are fixed a full release will be made available. This release will be suitable for live websites, however in the meantime RC1 is suitable for testing and development work.

Highlights For Website Administrators
The 0.8 release is more polished and up to date than ever before. With the new libraries for developers, new features should be faster and simpler to develop, reducing deployment costs. PostNuke 0.8 can be adapted to almost any need, from blogs to community websites and new third party modules are being developed all the time, constantly improving what PostNuke has to offer.

Additionally PostNuke 0.8 has a focus on the latest standards: XHTML compliance, Section 508 and Accessibility, and further enahncements have been made to both security, performance and usability.

With all core modules now templated, PostNuke 0.8 is designed to be cached, providing a huge performance boost over dynamically generating every page. Furthermore, with the templating system applied to all core modules designers will find it easier than ever to create a unique look to their websites. Gone are the days of standard 3 column layouts - PostNuke 0.8 includes new themes which are CSS, and not table, based. The new Xanthia theme engine is easier to use and performs better than ever before, while including an upgrade feature making it easy to import Xanthia themes from previous PostNuke versions.

For website administrators, this is the best PostNuke release yet, combining compliance with the latest standards and constantly improving features.

Highlights For Web Developers
The 0.8 release provides an Application Framework to allow rapid development of web solutions using the now stable PostNuke core. This allows third party developers to use the wide range of included API and utility libraries to create their own modules and extend the feature set PostNuke already provides.

Of these libraries, one of the most substantial is DBUtil, providing a cross compatible interface to the database. Selecting, updating and deleting data can all be achieved in one line, and DBUtil, combined with ADOdb will automatically create a cross compatible query for whatever database system is in use. PostNuke .8 has been tested with PostGreSQL, and further databases will be supported in future versions.

Other key features are site wide categories, supported through integration with DBUtil, the PostNuke Forms Framework for HTML forms, and other object based APIs. All of these are new since the 0.7x series and ensure third party development is both quicker and easier, and that compatibility with future versions is maintained.

For web developers, PostNuke will provide an attractive option when searching for a framework upon which complex web solutions

Generated on July 17, 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.

How to 'Pimp' Out pnForum   (News)

There are already several template sets available for pnForum:
Franky's phpBB Look
And the Cmods Devs already build some Themes with templates for pnForum
For example: AphroditeXTE - Demo

Other Themes with pnForum templates:
* G-Orange-XTE
* Cmods-dev-XTE
* Candy
* icgStation

Download them: http://www.cmods-dev.de/module-Downloads.htm
See them: http://demo.cmods-dev.de/ (Use the ThemeSwitcher)

The themes contains a folder /themes/ThatTheme/templates/modules/pnForum copy that into your own theme at /themes/ThatTheme/templates/modules/

But if you really like to have your own look & feel, I'd suggest you take a look at the standard templates. They are all named like the functions that call them. The contained JavaScript adds some complexity - although it's always optional. So the easiest way to create a new layout is to delete all the template's content and add a simple
[code][/code]
This opens a popup displaying all available variables. If you don't know how to use them you can always look into the backed up version of the template.

BTW: Frank Schummertz, maintainer of pnForum, spent alot of time creating seminatic HTML for the forum. But he's looking for someone who's good in creating a nice CSS for pnForum.

Generated on March 29, 2007.

Page 1 / 7 (1 - 10 of 67 Total)