PostNuke

Site search

Search results

Number of hits: 161

Welcome to Zikula   (Admin_Messages)

Zikula is a weblog/content management 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.

Security Announcement: PostSchedule 1.0.5 SQL injection vulnerability   (News)

For .764 PGCalender or PostCalendar might be a solution, when using .8 crpcalendar, Eventliner or TimeIt may be worth to look at.

We do not support PostSchedule with this fix, you use it on you own risk. It may (or may not) fix the recent exploit, but there might be others in the code. If someone wants to have closer look at it, feel free.

Generated on April 29, 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.

Url rewriting on Postnuke 0.8   (News)

Main principles of the mod rewrite


For information, the URL rewriting is a module that you can activated in your apache to rewrite the links of a site in order to simplify their reading.

The idea is that the Pn Team also thought that the mod rewrite was not necessarily available / activated on all types of servers (particularly on Windows servers). Indeed, the Postnuke team offers rewritings based on tips already heavily used in management systems like blogs.

Before you begin, here is the format of a link without rewriting.


without rewriting
index.php?module=Users&func=logout Index.php? Users & module = func = logout


URL rewriting without mod rewrite

This rewriting reproduced a "virtual" Folders system on your site, links look like this


URL rewriting without mod rewrite
index.php/Users/logout



In terms of mechanism, it is very simple, when your Web server receives a request for a link, it loads instinctively page "index.html". In this index.php, the parameters of the request are recovered via the header (you can look in "phpInfo" there is a field $ _SERVER [ 'REQUEST_URI'] which corresponds to this information).Then these parameters are interpreted , between the first two "/" is the name of the module, between the two others, the function name. Now Postnuke know the name of the module and function to launch.

You can pass parameters too, for instance, if you want to load a forum with id=2, the links will look like this

URL rewriting without mod rewrite
index.php/Forum/viewforum/forum:2




Note that the url rewriting uses ":" to represent the parameters in a url. So you can't pass variables like this "index.php?variable=filter:3". (be carefull if you are using Pagesetter and his filters system).



URL rewriting with mod rewrite

Optimizing the previous version

In the previous example, all links contained index.php ... but it's ugly, and functionally this file contains no
information useful to load the asked module.This trick is useful when you have no mod rewrite, but if one has an "mod rewrite enabled" server,you can use a "lighter" version of the previous rewriting without an "index.html"



Here is an example



URL rewriting with mod rewrite :Optimizing the previous version
/Users/logout




Be careful, if one of your pictures is written this way and you load the page /MyModule/main/. "/MyModule/main/test.png" which will be searched. Note that you can make a rewriting that redirect all links of the form "/*/*/*.(jpg | png | gif)" to "$ 3. (Jpg | png | gif)." (but it's ugly).


Mode file


This url rewriting is the classical version already used in previous versions of the cms, The rewrited links are lists of words (module name, the name of function) separated by dashes. Note that this version uses a large number of regular expressions rules to do the rewriting compared to the other one, which may increase the load of your server Web.



One example here ...
URL rewriting with mod rewrite : Mode file
module-Forum-viewtopic-topic-2903-start-0.html





Note that the "module" which one would have thought there's no point in it, is made for the support of the "old style" loading of modules.



URL rewriting customized


So here is the coolest feature, which allows you to customize the URL rewriting depending on the module you want to load. Just create a "encodeurl" function in your API module (pnuserapi) that takes as parameters, the information needed to create for output a fully customized rewrited link.

After, the loading of each page of the CMS, a "decodeurl" function in the API part of the module takes care to reformat the encoded url in a form understandable by the CMS.



You can find an example of the use of this method in the module "Pages" of values addons


Format of a encode and decode url
function pages_userapi_encodeurl($args)
function pages_userapi_decodeurl($args)



This feature is interesting because it allows us to have the hands on your url, not only before loading the page, but after loading this page, allowing you post-processing actions rather interessant.




This method allow you to

- put keywords in the url: (see Pages module)
- have a single version of your rewrited url : Indeed, through the post treatment you can recalculate the url and it does not conform to your requirements, you can redirect to the good link via a redirect 301 "Moved Permanently headers.






Use case of a url rewriting "no duplicate"



Notes: A small problem nevertheless for the use of this rewriting, which is limited to the type url "user". (more details here)

This article is a translation from this "how to" released on Postnuke-France

Generated on February 25, 2008.

SEO for postnuke   (News)

Customize title
You can customize the general title of your postnuke, by filling in the correspondant fields in the module "settings". The problem is that, you will have only one title for the whole website ... and that's ugly (and bad for SEO).
A solution was offered by Markwest, in order to personnalize this title, on every pages.the title tag plugin

This plugin allow you to format titles like this
Classic titles
HTML for Module Developers - A Discussion :: pnCommunity :: Support at your fingertips


if you want to have shorter titles like this, you can use the other unofficial version in the comments.

Improved titles
HTML for Module Developers


If you're using pnForum, it will give you title like this

PnForum title



Customize meta "descriptions" and "keywords"
You can customize the meta "descriptions" and "Keywords" of you CMS, by filling in the correspondant field in the "settings" module, but with this customisation, you will have only one "description" and "keywords" fields for all the site.
In order to improve this, there are two plugin on the community repository, one for fixing the descriptions and the other one for the keywords tags.


Notes : As the Search engine were spammed by overloaded keywords tags, for most of them , they don't consider this tags anymore.
If you're using pnForum, it will give you this :

PnForum metas



Activate url rewriting
You can activate the url rewriting in Xanthia, go to the Xanthia module, then check the options "use short urls", and copy paste the .htaccess file from the "doc" folder to the root of you CMS.

/!\ Be careful, live search doesn't url with more than two dashes

Notes : an improved version of the current url rewriting is available in postnuke 0.8.

Duplicate content

Don't duplicate links in your portal, two differents links must not point to the same content. Indeed, some search engine don't like to see multiples versions of the same page on a website (that's called "duplicate content")

To avoid this, you can use a robots.txt at the root of the CMS
Robots.txt
User-agent: *
Disallow: admin.php
Disallow: config/*
Disallow: header/*
Disallow: footer/*
Disallow: pntables/*
Disallow: /images/*
Disallow: /includes/*
Disallow: /adlogger/*
Disallow: /themes/*
Disallow: /pnTemp/*
Disallow: /docs/*
Disallow: /javascript/*
Disallow: *.php
Disallow:module-Forum-viewtopic-topic-*-start-0.html



An other tip, "/index.php", "/index.html" and "/" redirect to the same page so you can add this rule in you .htaccess
.htaccess
RewriteRule ^index\.html$ http://postnuke.com [NC,R=301]
RewriteRule ^index\.php$ http://postnuke.com [NC,R=301]


Text formating

In your articles or templates, try to have a structured layout with H1, H2, H3 tags.


Autolink and intern link
The module "autolink" is interesting, because he allows you to create a large amount of intern links with the same source anchor, this will help to increase your rank on the given word

404 error

When you've got an important portal with a large number of pages , it may be possible some of you ranked pages doesn't exist anymore. When search engine bots come to look for this "ghost" pages, you can redirect them to the home of your website, with an "Error 404" header.

.htaccess
ErrorDocument 404 /index.html


Take off unused metas tags

For most of them, search engine bots don't read some meta like "revist-after", so you can take them of your head tags. It will not help you, but you will have a cleaner header.
xxx.html




This article is a translation from this "how to" released on Postnuke-France

Generated on January 31, 2008.

What's going on?   (News)

know the Core team released RC2 of Postnuke .8 - the Steering Committee's report we are just working on will deal with the details.

2. Jørn Wildt released a first version of his "Content" module:
"Finaly I have finished the first version of my new Content module. With this little goodie you get HTML editing, YouTube video, Google maps and more features out of the box. This module was inspired by Typo3 and the never-finished PostNuke module Publish!" -- elfisk.dk

Content is a module that you can use to create static pages. It supports several predefined layouts (1 column, 2colums + header aso) and you can also add your own templates. In the editor you then can drag and drop content items like texts, images, youTube videos or Google Maps around and place them anywhere you like within the layout.

3. Together with "Content 1.0.0" a new version of Jørn's Mediashare gallery is available. Yet it still needs an installed Topics module to run under .8.

4. pnForum 2.7(.1) is finally released. A test version served the German Postnuke community for months and now he fixed the last bugs and made a public release.

5. Sven Schomaker is about to release Scribite 2.0 - It includes openWYSIWYG v1.4.6c as new editor and new versions of Xinha (v0.94), TinyMCE (v2.1.2), FCKeditor (v2.4.3), a lot of new module plugins and languages.

6. Axel Guckelsberger finished his diploma thesis that discussed the use of model-driven software development (MDSD) for Postnuke and resulted in his "ModuleStudio". Although ModuleStudio is far from complete it is way ahead in terms of modern software development. And if it turns out right MDSD is one of the next big things after object orientation (OO).

7. User ftree started work on a new gallery (pnAlbum) some months back and now published an article about his work. In preparation of the gallery he programmed some basic functions which turned out to be suitable for everyone who wants to program a module. If you want to you can take a look at his work.

8. There's a new pnCommerce team in formation: Rüdiger Hahn, Jim Hatfield, Chris Candreva, Bernd Plagge and some others are long time pnCommerce users and all maintained their own fork of the module. Now they are trying to put all their code together and a new version out for public use.

9. Marco Kundert is still working on his .8 follow-up for Pagesetter called Pagemaster. His first release will be 100% compatible to the latest version of Pagesetter so that you can simply import all you Pagesetter content into Pagemaster. Pagesetter introduced many ideas into Postnuke that have now become part of the core: Postnuke .8 has Workflows system and the idea of Pagesetter's form framework (Guppy) can now be found as Forms API in .8 and the WYSIWYG-Editor is now in Scribite generally available - Pagemaster uses all these features and thus can be much leaner.

10. Robert Gasch is working on a commercial shop module. He allowed me to take a look at it and it looks really great. Robert made his living for the last few years by setting up shop solutions for customers and now uses this experience for his new module.

11. Mateo Tibaquirá released a first version of his port of the standalone Relay AJAX directory management application. Includes drag-n-drop files and folders, a dynamic loading file structure, thumbnail views, multiple users & accounts, batch uploads, shopping-cart/batch downloads.

I am sure I forgot some people and I know there's a lot more going on in Postnuke land. But I'd like to leave some news for further articles.

If you are working on a news-worthy Postnuke project please contact me via personal message

Generated on December 22, 2007.

Rebranding of PostNuke... thoughts and considerations!   (News)

place) will be to explain people outside the active community what is happening, why and what consequences the rebranding will have.
Thats not just a task for PostNuke.com (sorry I don't know the new name ;)
The whole community, from main community site to the most "insignificant" PostNuke support site has to take part in this massive campaign to promote the new name and to explain.
Thats a big coordination task but thats not all... the PostNuke users you don't necessarily reach with this work is our customers!
Those of us that has made PostNuke not just a way of life but also a way of living has to explain to paying customers why the CMS they have been told was the worlds best and most steady product suddenly has to be renamed.
You could shrug off this and assert that "you have earned the money... you do the work and keep on smiling"... thats partly right... personaly I have never been payed for the system or any public available modules or such only the time I invested in the projects.
Last but not least we have to reach the people that are not aware of "renamedpostnuke".
Today you have to be creative when searching for a CMS on google and NOT hitting a PostNuke site within the first 2 resulting pages.

What the above lines boil down to is... have you got a plan for this?

I certainly understand why there is so much secrecy about the new name because it's a worldwide rebranding but again I ask you to consider the fact that there are a lot of community- and support sites out there that might feel slighted or disregarded.
We (the local community sites) have put a considerable amount of work and effort into promoting and supporting PostNuke and would ofcourse want to be able to do the same for "renamedpostnuke".

If we are not able to aquire "renamedpostnuke"-dot-"countrycode" for the major community sites in the various countries then please give us the opportunity to claim a variety of the name (maybe in advance) or "certify" us or whatever.
Maybe you schould have a little more faith in us and see us as "partners" in stead of "competitors"... well maybe I'm out of line here but that's how I sometimes feel ;)

You could claim that you have considered this and will make subdomain's for the various contries but that might not be the best way to do things. Although I would like to see a closer relationship between the main community site and the local community sites we still have to be just that... "local".

As stated above this is not criticism just some personal thoughts I have had for some time now and thought schould get out in the open.
If you will take them into consideration or not is up to you... maybe they already have been and I just didn't grasp it ;)

Anyhow I think there has been too little "public" info regarding the rebranding and your thoughts and considerations.
Right now I even don't care about the new name (...who am I kidding...OFCOURSE I DO...can hardly wait ;) and maybe I'm the only person who questions the steps involved...?

With the best of intentions the deepest respect for your work and 100% loyal PostNuke community- supporter and admin
Kim Enemark
Administrator at PostNuke.dk

PS: Try to google "postnuke" ;)
Danish search (top of page 1)
English search (top of page 3)

Generated on November 19, 2007.

News from "Behind the Scenes"   (News)

Rebranding
The new name and the logo have been chosen, now the lawyers have to do their work in claiming the necessary trademarks. This is more important for Europe as it is for the US. but we will get the trademark worldwide to avoid any future problems. But, as usual, the administrative mills are working slowly, so this needs some more time. As soon as this process has been finished we will decide about announcing the new name, either immediately or together with the final release of .8 (which will in this case be renamed to $newname 1.0).

EasyDist and the extension database
Axel and Simon have written a concept paper of how to connect the EasyDist module (see [url]http://modulestudio.de[/url]) to the extension database on this site. Necessary changes on both sides are identified and will be done in the next weeks. The plan is to have this working together with the release of $newname 1.0. Among other things EasyDist will be enabled to get the latest module or theme information from the database to create up-to-date packages whenever a new version of a module or theme has been released, an admin interaction will not be required.

Release Manager
Although the EasyDist module will become a very powerful tool we still have to supply the usual download packages. For this we need someone to create, validate, upload etc. those packages. In the future this task will be done by Patrick Cornelissen (patrick.c). He will also maintain the SVN module that is internally used on this site to create the daily snapshots for the core and selected modules. Thanks to Patrick for accepting this task.

New Subdomains on postnuke.com
Postnuke.com will get two new subdomains:
- devs.postnuke.com for devs and team members to post tips, news, information etc. This is the official replacement for the old pndevs.com site. Moving this site to a postnuke.com subdomain was planned from the very beginning.
- demo.postnuke.com will be a demo installation of .8 with working admin part, including some selected modules (not yet defined). This will be almost the same as http://pn8.pn-cms.de where the database is rebuilt from a backup every night via a cron job or manually throughout the day if needed.
Both sites will be installed and maintained by Philipp Niethammer (philipp.ni) and Gabriel Freinbichler (gf).

Documentation
We know that .8 is lacking a real documentation and we want to change this. Therefore a group of interested users will be built until beginning of November to take over this part. The Steering Committee will then decide about the project leader for this and ask him or her to work on a proposal for a manual, online help, and wiki structure which should all fit together (this also includes the tools needed to do the job) until mid of December latest (earlier if possible). When this has been accepted, we will talk about an exact time frame for finally writing the docs. Here everyones input is appreciated of course!
The project leader will have to submit a regular report about the proceedings to the SC.

Bug fixing weekend
As already announced in [url]http://community.postnuke.com/Article2862.htm[/url] the bug fixing weekend will start on Saturday, 6th. Mark and Robert also want to join us (virtually) to squish out some nasty bugs, Roberts main target will be the categories module.
Interested users can also join us using Skype. If you are interested, please send me your screen name via mail or private message so that we can invite you.


As you can see, the project is active although some might have thought the opposite. We delegated or will delegate some tasks to users who are able and ready to contribute to PostNuke. If you also want to participate, please contact us, there is always something YOU can do.

If you think you have something that is worth to be spoken about in the next chats, please tell us.

Generated on October 5, 2007.

Branding - What is PostNuke really?   (News)

how PostNuke should brand itself, and 2) who the audience for PostNuke is? I do not ask why 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.

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.

Page 1 / 17 (1 - 10 of 161 Total)