PostNuke

Site search

Search results

Number of hits: 121

Trac - NOC Replacement   (News)

hard to maintain. We're hoping you'll find the trac installation easy to use and navigate, and an improved NOC in all respects.

From the perspective of third party developers, trac provides a useful administration interface from which you can administrate all aspects of your project, from it's description to SVN commits list and file downloads. Trac also has much better milestone and target tracking for bugs and releases.

As a user, you can search the available projects, and use the clean navigation to find your way around. There's also an online SVN browser where you'll be able to look at a project's source code.

Chris is looking to begin converting projects over from the NOC as soon as possible. On request, he can import tracker and SVN history, or alternatively you can start afresh. He'd like to talk to people as he makes the conversion so that if anyone's missing something useful, or has suggestions he can improve the Trac installation for everyone.

Looking to the future, we'll convert the core PostNuke project over to Trac. We'll also try to get single sign on between community.postnuke.com and Trac working if possible.

If you are a third party developer, be aware that we are planning to close the NOC in the future. If you have active projects

Generated on May 4, 2008.

OpenID for PostNuke   (News)

If you haven't read that yet and is interested in OpenID then please read it here - it will explain the whole OpenID background.

For those of you that haven't heard about OpenID yet, here is the very short explanation: OpenID is a relatively new web-technology for managing your online identity. It's primary purpose is to facilitate Single Sign On across independent websites. This means you can create yourself an OpenID identity and use that for login in to different websites without having to retype your password over and over again.

When I wrote the last article I promissed to deliver an OpenID implementation for PostNuke, and, well, here it is! You can now download OpenID from the NOC OpenID project page.

By installing this module you enable your users to:


Register an OpenID with their PostNuke account and login with this OpenID. The OpenID manager page can be found in the user account panel (Profile).

Create an account on your website using OpenID's registration process.


The OpenID module requires PostNuke version .8 from SVN (april 15th) - and probably also PHP 5.x since a required extension "domxml" is not delivered with PHP 4.x.

So don't hesitate - get your website OpenID enabled today and save yourself (and your customers) the hazzle of managing multiple user accounts.

Intra-web usage
You can use OpenID for Single Sign On between closed "intra-webs". For this
you must have a trusted OpenID Identity Provider (IP) - either your own or an
external one. Then you add a filter on the OpenID admin pages - this filter
should allow access from your trusted IP and deny access from any other
provider. In this way only users from your trusted IP will be allowed to access
your website.

Read more

You can find lots of information about OpenID around the web. The most obvious place to start is of course openid.net. But at openidbook.com you can get a free copy of the 200+ pages OpenID book from Rafeeq Ur Rehman. This should satisfy even the most curious people

Enjoy, Jørn Wildt

Generated on April 16, 2008.

Going OpenID   (News)

(if you already know OpenID then jump directly to the last section about
OpenID in PostNuke)
OpenID - a Free, Decentralized Online Identity
OpenID is a relatively new web-technology for managing your online identity. It's primary purpose is to facilitate Single Sign On across independent websites. This means you can create yourself an OpenID identity and use that for login in to different websites without having to retype your password over and over again.
Your OpenID consists of a URL, e.g., http://jornwildt.myopenid.com, and the OpenID technology makes it possible for you to prove that you own this URL. So, when you want to log in to a website supporting OpenID, you type this URL and then the website takes care of the rest (almost). EnThinnai Blog compares OpenIDs to credit cards: credit cards are issued by someone, it proves your identity at the issuer, you can have as many cards as you want, and in OpenID's case you can even use them to get access to places.
You can also use your OpenID to sign a weblog comment without the need to register as a user on that website. No one else can do that with your URL so your comments cannot be spoofed by anyone.
Take a look at these demos of how it works in some applications: OpenID for WordPress.
OpenID on blogger.com.
OpenID at
plaxo.com.
On Simon Willison's website you can also see some good examples of what OpenID can be used for.
One very interesting thing is that OpenID has just been adopted by Yahoo! So now each and every one of the 250 million Yahoo! users have their own OpenID identity. Even Google, IBM, Microsoft, and VeriSign have signed up to support the new technology. With that kind of backing OpenID is no more a kids toy.
OpenID is of course not the perfect solution for everything
(see for instance idcorner.org) but I would say it is close to perfect for Single Sign On and signing comments in the web/PostNuke world I live in.
If you want to start using your own OpenID then get one at
myopenid.com - it's free and it's all you need.
OpenID in a PostNuke world
PostNuke should of course also have such a thing as OpenID for Single Sign On, user registration, signing comments and so on. So a new OpenID module for Single Sign On and user registration is on it's way (expected release in March or April). Have fun with it.
An OpenID implementation with PostNuke should also enable you to use your PostNuke installation as an Identity Provider, meaning that your OpenID could be YourName.YourSite.com. Hopefully the OpenID module will support this.
Other uses for OpenID in PostNuke could be to sign comments using the ezComments module or pre-allow access to certain Mediashare photo albums through your friends OpenIDs. Only the sky is the limit and OpenID is free for you to use and invent with.
Regards, Jørn Wildt

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

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.

pnMeeting 2007: The Videos are Online   (News)

informative videos. But maybe you can nevertheless gather some information from it or at least feel the atmosphere of this years meeting.

Mark West's Keynote
Jørn Wildt explains pnForms
Robert Gasch on CategoryUtil
Robert Gasch on DBUtil and the Object Model in .8
Mark West: Porting an Open Source Template to PostNuke .8
Jørn Wildt Proposes New Content Module
Albert Perez Monfort introduces the "Intraweb" project
Mark West talks about .8/.9
Axel Guckelsberger on EasyDist, EasyInstaller & the ModuleStudio
Joseph on Beat Boxing

We hope you enjoy the presentations anyway ;-

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

Using PostNuke and MySQL in Unicode (UTF-8)   (News)

MySql and UTF-8

by: Bernd Plagge
www.choicenet.ne.jp

MySql introduced support for different character sets and collating rules in version 4.1. While this has many advantages databases sometimes need to be migrated and then we have to ensure that the correct character code is set for the new database. We are mainly using UTF-8 and hence you may have to adapt this information to your situation!

What is the problem?

MySql uses as default Latin1, swedish flavour.
How do we check this?

run mysql.
mysql> show variables;

How to check the character set for a particular database?

run mysql.
mysql> show create table


The character code can be set in various places - so where is the best place for this?


We always use UTF-8
------------------------
In this case it makes sense to set the character code for the whole server to UTF-8. MySql actually sets the character code at different levels:
server
client
database connection
database

The character encoding for server, client and the connection work hand in hand to ensure that the data is interpreted correctly. It seems that MySql makes no effort to determine the correct character set but will convert data in accordance with it's configuration. This leads to problems for old databases if the database character code differes from the one configured.

The easiest way to configure MySql for UTF-8 is to put the configuration inot the main configuration file (/etc/mysql/my.cnf).
In my.cnf there are different file sections. So you can't put it just anywhere.

[mysqld]
character-set-server=utf8

[client]
default-character-set=utf8


Setting UTF-8 for one Database
--------------------------------------
You can check the default character code for a database either by dumping the data and then changing the schema file or you can do this online.
You use the 'alter table' statement to change the database using mysql.

run mysql
alter database
default character set utf-8
default collotion_name utf8-general_ci;

note: you may omit the word 'default'.


It is also worth noting that e.g. mysqldump silently adds the default character code when exporting data!
This can causes problems if the character code defined and the database content are different. In such cases MySqldump will try to convert data to it's default character code!
However, you can disable that by adding the character code option when using MySqldump.
e.g. mysqldump --set-charset.

In the same way you may explicitely set the character set.

mysqlimport --default-character-set = utf8
mysqladmin --defautl-character-set = utf8 create


Setting the character code at server start
-----------------------------------------------------
You can start the server with:
character-set-server
collation-server

The current values can be determined with the command

run MySql:
mysql> show variables;


Values may be changed with commands like:

set character_set_server = utf8;
set collation_server = utf8_unicode_ci


Setting the character code within Applications
----------------------------------------------------------
You want ensure that the correct character code is set when connecting to a particular database.

Connect to the database and issue the following SQL command:

mysql>SET NAMES utf8;


SET NAMES is equivalent to the 3 commands:
character_set_client
character_set_connection
character_set_results


How to run PostNuke in UTF-8
-----------------------------------
Several things have to fall into place for this to work correctly.

1) the database encoding needs to be set to UTF-8
2) the application language needs to be encoded in UTF-8
3) PostNuke needs to be told to use UTF-8

ad 1)
see above for details!

ad 2)
The character code for a given language is set in language//global.php (PN 0.76x) or in language//core.php (PN 0.8). Search and adjust the following 3 define strings:
define('_CHARSET','UTF-8');
define('_LOCALE','en_US');
define('_LOCALEWIN','eng');

Of course it is not sufficient just to change the _CHARSET to UTF-8. The text strings themselves need to be encoded in UTF-8. This can be done in a number of ways:
a) use 'recode' or 'iconv' on every language file
b) use the pnlwb (PN Language Workbench) to extract and convert all language files

ad 3)
Following the database initialization you need to issue a "set names to 'UTF-8'" command. As this is done in includes/pnAPI.php we need to patch that file.

PN 0.76x
----------

// load security functions.
include 'includes/pnSecurity.php';

// Load our language files
include 'includes/pnLang.php';
pnLangLoad();

//bplagge 2006-01-31 - charset fix for new MySql version
$dbconn =& pnDBGetConn(true);
$info=$dbconn->ServerInfo();
if ($dbconn->ErrorNo() != 0) {
echo "Error: "; echo $dbconn->ErrorNo();
}
// print_r($info);
$c = _CHARSET;
// Mysql uses non-standard name for UTF-8!
if ($c == 'UTF-8')
$c = 'UTF8';
$query = sprintf('SET NAMES \'%s\'', $c);
$dbconn->Execute($query);
if ($dbconn->ErrorNo()!=0) {
echo "Error: "; echo $dbconn->ErrorMsg();
echo "check pnAPI.php";
}
}
// end bplagge - mysql charset adjustment


PN 0.8
-------

if ($stages & PN_CORE_LANGS) {
// Load our language files
pnLangLoad();
}

# bp 2007-06-01
# need to "set names '' " to ensure correct data handling
$query = sprintf('SET NAMES \'%s\'', 'UTF8');
$result = DBUtil::executeSQL($query, -1, -1, true, true);

Please note that the MySQL character code names are NON STANDARD!

How to check?
----------------
I always found that phpMyAdmin is an excellent tool for MySQL databases. If the data entered in PostNuke is also correctly displayed in phpMyAdmin table browse mode I'm quite confident that everything is fine.

Generated on June 6, 2007.

First supported version of CoType released   (News)

A document consists of nested sections, so you always end up with a
structure like this:

Document
+- Section 1
| +- Section 1.1
| | + Section 1.1.1
| +- Section 1.2
+- Section 2

You can also add "boxes" to your sections. These boxes contains images
(references to multimedia files from Mediashare), program examples, or simply
some text. Boxes can be positioned in various places of their containing
sections - top left, top right, above and bottom.

CoType is designed to cover the grounds between a Wiki and a single document.

Wiki elements:
- With CoType you can collaborate on document creation since every person can edit their own sections (can also be open to anonymous users).
- With CoType you can easily link different sections and boxes (there is a toolbar button for this in the editor).
- CoType has a complete revision history for each section and you can see who edited what, when and from where.
- Everything is instantly online.

Single document elements:
- All sections in a CoType document can be printed, exported or downloaded as
one single document for off-line use (not feature complete yet).
- You get a nice structured table of content.
- You can read the text linearly from section one and forward.


Features:
- Create unlimited number of documents
- Add unlimited number of sections to documents
- Add floating figures with images and text
- Organize sections hierarchically by drag-and-drop
- Automatic table of contents
- HTML WYSIWYG editing using FCKEditor
- Insert cross references
- Support for PostNuke .8 search API
- Complete revision history
- Only one person at a time are allowed to edit the same section. No more
overwriting of other peoples work (depends on PostNuke .8's PageLock
mechanism).


Download here.

Support site: www.elfisk.dk.

Enjoy, Jørn

Generated on May 24, 2007.

Demo version of CoType module   (News)

|    + Section 1.1.1  |    +- Section 1.2  +- Section 2CoType is designed to cover the grounds between a Wiki and a single document.

Wiki elements:
With CoType you can collaborate on document creation since every person can edit their own sections (can also be open to anonymous users).With CoType you can easily link different sections (there is a toolbar button for this in the editor).CoType has a complete revision history for each section and you can see who edited what, when and from where.Everything is instantly online.

Single document elements
All sections in a CoType document can be printed, exported or downloaded as one single document for off-line use (not feature complete yet).You get a nice structured table of content.You can read the text linearly from section one and forward.

Features:
Create unlimited number of documentsAdd unlimited number of sections to documentsOrganization sections hierarchically by drag-and-dropAutomatic table of contentsHTML WYSIWYG editing using FCKEditorInsert cross referencesSupport for PostNuke search APIComplete revision historyOnly one person at a time are allowed to edit the same section. No more overwriting of other peoples work.

Future features/ideas:
Working with images and figures using MediashareFootnotes/end notesBibliographyExport to DocBook/Html/LaTeX/PDF/Word
You might ask "why a new wanna-be Book module - there's already one (and many other content modules)?". Well, there's a couple

Generated on March 18, 2007.

Page 1 / 13 (1 - 10 of 121 Total)