PostNuke

Site search

Search results

Number of hits: 339

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.

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.

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.

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.

PostNuke 0.8 RC3 Released   (News)

PostNuke 0.8 RC3 Upgrade Pack Download
Download (ZIP)
MD5: 02629a822154f9f88a72ebea7f562470
SHA-1: 7ca9de7e7285778122e3d711c1b48f9ee4342396

Download (TAR.GZ)
MD5: eaf730995aec0acebca26f62a9f5ec98
SHA-1: 2245191875cb66d4c2cbda769321b3f0ccb7dc33


PostNuke 0.800 RC3 Core Download
Download (ZIP)
MD5: 95000958fa40f442a40282db5aae1799
SHA-1: aaa57406204bdc1220a6768d6de2021736ffe1cc

Download (TAR.GZ)
MD5: e563098769d0ce448c31a39a92f9b0ab
SHA-1: 5fe83c58707de118a28ba0dd8c72138706d90388


PostNuke 0.800 RC3 ValueAddons Download
Download (ZIP)
MD5: 195a63ac59c1ddce7507ad50b21032d1
SHA-1: 8f64584642ea3959b13a98b1649dfe50921ffa31

Download (TAR.GZ)
MD5: f7436f01187f81f34eb80c4959d46d37
SHA-1: 5ebce8c82fa1599ad81b3bce771d418b6e496329


Release Highlights
There are a number of improvements in RC3 over RC2, these include an enhanced upgrade script, the new Tour module and some last minute categories module improvements.

New Upgrade Script
The two upgrade scripts, upgrade76.php and upgrade.php have now been combined into a single file. In addition to this, a number of interface improvements have been made to make the process of upgrading your .7x series websites simpler and more reliable. The new script also solves some long standing bugs with the update proceedure, so we invite anyone who had problems with the upgrade proceedure previously to try again with this new version.

Tour Module
In an attempt to reduce the learning curve when first starting with PostNuke, a new module has been developed to introduce you to this new release of PostNuke. It provides a first time tour of PostNuke, introducing you to common terms like block, module and theme with which new users may not be familiar and also gives some basic hints and tips on where to start.

For more experienced users, there is a 'New In PostNuke 0.8' section, where you can discover more about this release of PostNuke, and a distribution tour, where authors of distributions can describe the purpose of their package and how it benefits you as a site administrator. The distribution tour page is stored in docs/distribution/tour_page1.htm, and an example is included in this release. This file is not intended to be viewed outside the Tour module, as the Tour module adds navigational elements around the page.

Finally, module and theme developers can include tours for their module, to introduce users to key features, or help them familiarise themselves with the basics. It is intended to serve as a crash course for all modules - be they complicated (such as pagesetter) or more simple (such as the Pages module). Certain modules have hidden features about which a user may not necessarily be aware, and we hope that the tour module will allow module developers to better promote the features their modules contain.

The tour module supports multipage tours for all modules - simply store tour_page1.htm and any subseqeuent pages in modules/yourmodule/pndocs/, or themes/yourtheme/docs.

Categories Improvements
The categories module received a few last minute improvements in SVN just before the release of RC3. These improvements are

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

Big Final Bug-Fixing Weekend   (News)

We will then try to test the changes and make the final release as soon as possible.

We hope not only to attract Core developers - also module developers and themers might join and have a productive weekend with some nice chatting.

What you can do

We open a Bug-Fix-Weekend Chat in Skype - If you want to join, drop me a line via PM and tell me your skype name
Test everything you need for your sites with the RC2 or the latest SVN version and report all bugs in the noc.

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

Postnuke .8 RC2   (News)

compared to RC1 a lot of bug fixes, a rewritten and simplified categories module and an improved upgrade for users of Postnuke .764.

Downloads
There are 3 packages available:

The core pack contains only the bare system and no content modules. It's supposed to serve as the basis for a new site. So you only have to upload all the modules you personally need.

.zip
.tar.gz


The value addons contain all the content modules from .7x in their latest version fit for .8. So if you need Quotes or FAQ for your site, this is the place to find them.

.zip
.tar.gz


The upgrade pack contains everything you need to update an existing .764 site. It is the core pack and the value addons in one package. Please note: DO NOT UPGRADE YOUR LIVE SITE.
This is still not a final release and is not supposed to be used in live enviroments. If you intend to upgrade your site with the final version you should test the upgrade with the RC2 and a
local copy of your .764 site.

.zip
.tar.gz

Please test!. The more you test now with the RC2 and the more bugs you report, the less trouble you will have with the final version.

Checksums
MD5 Checksums

6cf82ee1883136c4c0bf69e13f1d91ba PostNuke-0.800-RC2-FULL.tar.gz
dd7f4b50e4ddfdbd3d96b017287f1a7c PostNuke-0.800-RC2-FULL.zip
6ebf2a51234a6401b7c96c89781d7165 PostNuke-0.800-RC2-CORE.tar.gz
14e65ef97d88470e0080c8e9538c9147 PostNuke-0.800-RC2-CORE.zip
89a6d51fa3f10286b09c29ea312ff7c9 PostNuke-0.800-RC2-ValueAddons.tar.gz
e06a81aec7e50292dfd63fd40a7c88b9 PostNuke-0.800-RC2-ValueAddons.zip

SHA1 Checksums

dd75378f3fa87df7b4b827e74adc0e162c29e861 PostNuke-0.800-RC2-FULL.tar.gz
2de3a2132265b920ab5333f6d2ec692e1c3061e1 PostNuke-0.800-RC2-FULL.zip
90ee7897b7abf29a4a136029823cb8a337a4076f PostNuke-0.800-RC2-CORE.tar.gz
376ae9f296c2533965d95972ddf05937a9cae4b4 PostNuke-0.800-RC2-CORE.zip
de878d7472ae9d2fc54bcf7322cbd5e8df015e32 PostNuke-0.800-RC2-ValueAddons.tar.gz
78ba886356e44da4798abf9577ab45b68756c741 PostNuke-0.800-RC2-ValueAddons.zip


Notice
The upgrade will only work for .764 sites. If your site is based on an older version this is the time to start your upgrade. If you have any questions about the update, visit the forums.
There will be no major changes from RC2 to the final release. The RC is bug fix only. If you intend to write modules, themes aso for Postnuke .8 you can start working with this RC

Generated on December 12, 2007.

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.

Page 1 / 34 (1 - 10 of 339 Total)