PostNuke

Site search

Search results

Number of hits: 244

Support   (Content)

Since PostNuke has reached the End of Life we no longer offer a PostNuke support through community forums which is where the majority of support was carried out. 
PostNuke is no longer maintained so we strongly suggest migrating to Zikula. Most people have migrated from away from PostNuke

Generated on February 1, 2009.

About   (Content)

web site and provides the webmaster with a site they can administer with a minimal amount of HTML knowledge through a web browser.

But, PostNuke's functionality can be increased by installing modules, blocks and themes. For example, you can add a forum, a gallery and contact form. You can also change how your entire site looks by changing themes. All of this can be done with just a few clicks in the administration panel saving you hours of time, both in the initial creation of the website and in its day to day maintenance.

PostNuke can do anything from traditional blog websites, to a community members' only website with hundreds of users. PostNuke

Generated on January 30, 2009.

0.7x End Of Life   (News)

From 1st October 2008
PostNuke 0.7x will only be available as a download package from code.zikula.org. New modules and themes for the .7x series will no longer be accepted into the Extensions repository after this date, and devlopers are encouraged to convert their extensions to Zikula 1.0. Any security updates to 0.7x modules will still be accepted in the repository.

From 1st January 2009
Official support for 0.7x will no longer be available. The extensions database and support forum will be archived, and new submissions will no longer be accepted.

On 1st July 2009
Official support for the 0.7x series of PostNuke ends on this date. Security fixes will no longer be provided, though it will

Generated on June 6, 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.

Development Update, 2008-01   (News)

.8 Final: the next step after RC3
Since the release of RC3, already a lot of bugfixes have been committed to the repository. The developers have agreed to address all new features to the .9 tree, where the two major changes (UTF-8 and gettext, see below) are already in active development. This should result in much shorter release cycles (and earlier release dates) also, and give module developers much more clarification on what to change in order to make their module work under the new major release. If needed, an final bugfizing weekend may still be organised for .8 final.
The upgrade from .764 installations on certain systems has been improved, by increasing the memory_limit to 64M. However, this only works for php version 5.2.1 and above.
Upgrading to .8 together with some 3rd party modules may raise problems when the modules upgrade process is not failsafe for .8 or if the upgrade function uses core functions of modules that are not available yet. Therefore the upgrade of 3rd party modules in general is avoided by following a white list of core modules.
Most site-specific data can already be easily overridden using the /config and /themes directories. The Multisites module however still needs some futher thought on the best way of running multiple sites from a single install. One method having multiple unrelated (i.e. non table sharing) sites of a single install would be to have config/site1, config/site2 etc., this will be postponed to a next release.
The Tour module is now in a state where it can be translated to other languages as well. Just translate the templates and put them in a subdir with the appropriate language abbrevation, all within the pntemplates directory.

MultiCategorization introduction and issues since
As earlier announced, a last fix for supporting MultiCategorization has been added to the core just before the release of RC3. Since those changes, another small fix was then required to be fully backwards compatible. On the module-devs list, the devs have discussed a lot on how to solve these issues. Chances are great that if the new (already committed) patches do not solve the problems, MultiCategorization might be postponed to later versions in order to fully test the new features.
For more information on MultiCategorization, visit this thread in the forum.

DOM extension to use correct paths in JavaScript
Some javascripts, eg. the lightbox, need to know the path to the system and the entrypoint as well (which can be configured in the settings), otherwise they may fail in case of short urls being enabled. Since dynamic javascript creation might be a performance problem, some inline javascript is added to the pagevars to extend the DOM:
- document.location.entrypoint: will be set to what is configured to be the entrypoint
- document.location.pnbaseURL: will point to the result of pnGetBaseURL();
Any ideas on how to make his more unobtrusive are very welcome!

PostNuke Upgrade Distribution
In previous articles and posts, the term '.8 upgrade pack' was used to represent a full .8 package, including 3rd party modules, to upgrade to .8 from an existing .764 installation. However, the term 'upgrade pack' is not quite correct and misleading, because it implies to be an upgrade package with changed files only, while the main parts remain as-is. The transition between .764 and .8 requires a complete exchange of all files, so the so called upgrade package is a complete distribution.
Now it remains what modules should be in an upgrade distribution, to be able to fully upgrade an existing .764 installation, including new versions of 3rd party modules. These include Downloads 2.2, pnMessages, Polls 2.0, bbcode / bbsmile, Weblinks, EZComments and MultiHook at least. This might need some additional testing with certain versions also.

Core changes and additions in the .9 tree
Mark has already overhauled some core API methods and calls. All systems modules are now using the Renderer Class instead of pnRender. Also, a first pass has been committed in changing all pn* function calls to new object method calls. For example, pnModGetInfo is replaced with ModuleUtil::getInfo and pnSecGenAuthKey is replaced with SecurityUtil::generateAuthKey.
For those who did not know: A class pnCompat.php still includes most oldstyle API calls for backwards compatibility.

GetText and Default DB Charset
Bernd is progressing rapidly on integrating gettext in de development tree, and has added po-files for all core modules. The required PHP version for .9 has already been set to a minimum of 5.1.6, and since version 5.0, MySql supports different character sets and corresponding collating orders. To run an application in UTF-8 (unicode) it is not sufficient to change the character set for PN; we needed to set the database encoding (actually server and client) to UTF-8 as well.
A user who wishes to run his site in multiple languages, needs to decide the database encoding at installation time. The default is UTF-8, because the current iso-8859-1 is restricted to too few language combinations. UTF-8 is a 'no-worry' setting because it will work with any language (as long as it is UTF-8 encoded.
This change is $PNConfig['DBInfo']['default']['dbcharset'] = 'utf-8';

To cache or not to cache, that's the question
Also discussed on the devs-list is the current (and future) state of output caching within PostNuke. Why should any application repeat the same processing tasks on a item that hasn't changed?
Not caching anything is fine if one has got infinite resources to throw at a site (and even then there are limits). But in reality there are finite resources and you need to take steps to ensure that those resources are effectively used. One method for that is not wasting precious resources repeating the same tasks time after time.
The key is effective cache management. Currently we put too much load onto the module to handle it's own caching. Once you then

Generated on March 2, 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.

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.

It's All About Distributions   (News)

Where's the HTML Editor?
There seems to be a small rally for a WYSIWYG editor to be included with the core distribution. Realistically, not every web site needs an editor. Some simply do not need the code bloat or overhead with which an editor comes. Furthermore, all editors are not created equal. In fact, if someone does not like or use the editor and wants to remove it, then work is needed to remove it. This is where distributions come into play. One only needs to create a PostNuke distribution with an Editor. Now it will be ready for the masses.
Now there are some real advantages to not including modules into the core. With a smaller core set, there is only a need to update and patch what you use. This also allows modules to add features at a rate independent of the core. Who wouldn't want features faster? For example, if there was a feature added to AvantGo that you really wanted but it was only available in the SVN, one may feel wary about using it. Now, you can have a release version of AvantGo whenever, complete with new and exciting features!
New Blood
Specialization allows new users to get what they need to start their project and start tinkering around with PostNuke, instead of trying to read endless forum threads trying to figure out how to assemble a package to start their endeavors. Specialized distributions should encourage many new website entrepreneurs to stop and take a good long look at the software. Imagine a user stumbles upon PostNuke while researching perspective engines. He looks at WordPress, a nice blog system. He finds Gallery, a nice photo gallery. Next he finds PostNuke with a nice list of different distributions. Next he finds phpBB, a seemingly good forum/portal system. Now which seems more appealing? The system with a wide range of flexibility, yet with specialized distributions or a specialized system with limited flexibility?
I'm a Winner, You're a Winner!
The advantages to separating the core from the modules outweighs the disadvantages. This is why there is a move towards specialized distribution. So people can have what they want and need, not what the core says they are getting. With the reduced core, you are getting more by getting less.
David Pahl

Generated on January 20, 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.

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