PostNuke

If not that then maybe an update to the PN stats to show unique visitors by day.

Just a thought, here is the link.

http://rowd.zuavra.net/proiecte/phptrack/en/

The theme explanation mentions things like:
$info = genArticleInfo($row)
$results = getArticles(where, order, limit)
$links = genArticleLinks($info)
$preformat = genArticlePreformat($info, $links)

Screw that. I didn't need any of it. Try to follow these instructions, I appologize if they're kind of rambling... :) All themes are not made the same, so I can't into specifics, but if you figured out the old theme system, this is a piece of cake once you sit and work with it a bit.

First step.
BACK UP YOUR THEME! Once you update your functions they will not completely work until you finish updating each variable.

Next
Look through your theme. Anywhere you have a variable - such as $informant, $title, or $comments, more than likly you will replace it with either a call to $info[informant], $preformat[title], or $links[comment].

Now, a brief explanation of the differences between them:
Items in $info contain JUST test. No formating.
ex: $info[topicimage] is just "announcements.gif" (no quotes)
Items in $links contain just the URL. Again, no formating.
Items in $preformat are formatted and already contain links and everything. Very handy.
$preformat[title] already figured out story id, and title name and formats it so that it's already clickable

Here we go...
Look at function themearticle()
Remove everything in the parenthesis of themearticle() and replace it with "$links, $info, $preformat." It should now look like: function themearticle($links, $info, $preformat)

Ok, your theme will be completely broken for now. I hope you saved. I made one change at a time and checked the results. Things should start appearing one by one.

Replace each variable ($cid, $hometext, $notes, informant) with the corresponding variable below. Note: if you use any of the $info or $links variables you will probably have to use them along with HTML to get links or formatting.

for instance: modules.php?op=modload&name=News&file=article&sid=$sid&mode=&order=0 will become modules.php?op=modload&name=News&file=article&sid=$info[sid]&mode=&order=0 or use $preformat[title]

If you have lengthy sections of code for formatting your article body, changes are you can just use $preformat[fulltext]

Be creative. Once you do a few, you'll be amazed at how easy it actually is.

Admin Check
Instead of using if ($admin) for your [Edit] [Delete] lines, use the following bit of code:

if (authorised(0, $storyComponent, '::', ACCESS_ADMIN)) {
echo " [ "._EDIT." | "._DELETE." ]n";
}

Note: I added spaces in the < a href> and statements


List of variables from themes.postnuke.com:

$info variables are NOT formatted. They're just raw information from the database.
$info[bodytext] - the main text of the story
$info[briefdatetime] - short version of the date and time the story was published
$info[briefdate] - short version of the date the story was published
$info[catandtitle] - the category and title of the story, in the format 'Category: Title' if the story is in a particular category
$info[cid] - the ID of the category the story is in
$info[catid] - the ID of the category the story is in (deprecated)
$info[cattitle] - the name of the category the story is in
$info[comments] - the number of comments the story has
$info[fulltext] - home text, then body text, then notes
$info[hometext] - the header text of the story
$info[informant] - the person who submitted the story
$info[longdatetime] - long version of the date and time the story was published
$info[longdate] - long version of the date the story was published
$info[maintext] - home text, then body text
$info[notes] - any editorial notes on the story
$info[sid] - the story ID
$info[tid] - the topic ID
$info[topic] - the topic ID (deprecated)
$info[topicd] - the topic ID (deprecated)
$info[title] - the story title
$info[topicname] - the name of the topic
$info[topicimage] - pathname to the topic image
$info[topictext] - description of the topic
$info[unixtime] - the Unix timestamp of the story
$info[version] - the version of the array. This can be used to see if sepcific variabels exist in the array or not.
$info[withcomm] - if the story allows comments to be posted with it


$links variables are just that. Just the URL. They are not formated.
$links[category] - list of items in the same category as the story
$links[comment] - comments on the story
$links[fullarticle] - the story itself
$links[print] - print the story
$links[send] - send the story to a friend
$links[version] - the version of the array. This can be used to see if sepcific variabels exist in the array or not.


$preformat variables are basically plug and play (uhg! Sorry!) They're already formatted and ready to be clicked. All AutoLinks have been inserted and everything. You're probably use these the most.
$preformat[bodytext] - main body of text, including autolinks if any
$preformat[bytesmore] - 'bytes more' link (for back-compatibility)
$preformat[category] - list of items in the same category as the story
$preformat[cattitle] - the title of the story, preceded by it's category (if any)
$preformat[comment] - info on current number of comments
$preformat[fulltext] - home text, then body text, then notes
$preformat[hometext] - initial text, including autolinks if any
$preformat[maintext] - home text, then body text
$preformat[more] - single generic status link (for back-compatibility)
$preformat[notes] - any editorial notes on the story
$preformat[print] - print the story
$preformat[readmore] - 'read more' link
$preformat[send] - send the story to a friend
$preformat[title] - the title of the story
$preformat[version] - the version of the array. This can be used to see if specific variabels exist in the array or not.

The new theming system is VERY powerful, and once you realise the theory behind it, you see it's pretty easy.

I hope this helps someone.

We decided to change our portal script to PostNuke because of the open development that seems to work much faster than development of PHP-Nuke. It have turned easier to find modules for PostNuke that are still supported and developed.

Our first impressions of PostNuke is very good. It seems more modern than PHP-Nuke. We did find blocks administration better than one in PHP-Nuke. Statistics page is nice with good information.

Our site can be found from the URL http://www.fetissi.org - It's now using Finnish and English but soon there will be both languages supported :).

We are now working on Finnish language file for PostNuke. Thank you for everybody in the PostNuke scene. Let's rock!

Footnote: 1

... there are so many problems with this system that we had to make about 100 (small/big) modifications to the code of the Rogue system.

We discoverd that almost 60 percent of the module developers do not stay with the guidelines of modules developement. That is somethink that is so frustrating, because everytime you try to drop a new module into your RUNNNING system it sometimes trashes you complete site behavior.

We (developers) need to do something about that.

Footnote: 1

http://wvware.sourceforge.net is the address of the project. So what's the potential of incorporating this to postnuke? Let's claim it that a lot of people is using the Microsoft Word Format so most of portal documents are in .doc

By introducing an extensible solution like Postnuke, you can actually help in data format migration and possibly turn them all to XML (if you want XML) or any format you want.

htt://www.siteseed.org incorporate wv on their portal system.

I wish the development community can take a look at this concern.

In addition I think this is more polite to the user, because if the administrator don't want to post the new and rejected the submission, the system can send user an email to notify user of reject submission with an optional explaination field for the site administrator.
So user don't have to wonder what is going on with his/her submission.

Do you think this is a good idea? Just curious.

- a customized members sign up page that would use a 3 page/section signup form. (members will have to at least complete the first page with the option to continue the remaining 2 pages at that time or logging in at anytime to add/change to the full list of member profile questions)

- a custom user profile page that will pull in the data collected from the sign-up form and place it in a designated area I will give you.

- a custom admin edit users form that will allow for edit and changes of the members profile information used in the member sign up.

- a custom members list to include some of the data collected from the members signup.

- from the admin in the edit users section there would need to be a way to toggle some of the information to display for a member viewing another members profile if the admin gives them permission to see that information. (in this case I want to be able to say if a user has permission to see another members contact information, and if I set it to yes then when they view any members profile page that info will show up in the appropriate spot I have you display it. If I have their permission set to "NO" then they will still see the members profile but with the contact information section missing or a graphic or languge put in its place with instructions on how to be able to see this contact information.)

- I am interested in this module being made to work with the .64 version of postnuke right now with the existing members and users modules with modifications made to those tables only and adding any additional tables that are necessary to make this module work independent of the .64 version.

- the data collected will include all the standard data that is asked of in postnuke .64 version . I just need a way to collect additional data from the user and manage that additional data on the members list, admin edit users area, user sign up , user edit info page, and members profile pages.

- I am not interested in it being rogue compatible.

Please contact us if you feel you qualify for this project to discuss fees or other options.

Please note that once this module is completed that we will be releasing it back to the POSTNUKE community :

Richard Wing: richard@richardwing.com

or

Blake Billings: webmaster@memphisweb.net

I would welcome sharing of information regarding the 'top-tier' PN sites. This should exclude PN specific (self-promotion) sites with the possible exception of postnuke.com where the traffic and performance might be relevant.

What is needed is:-

1) What are the top 10 independent sites using PN rated by numbers of dialy page impressions and numbers of subcribers/members.
2) What is the configuration of these sites (1 or more servers, load balancing, dedicated db server, memory, disks, proxying, bandwidth).
3) What are the collective experiences of developers in terms of Apache/MySQL/PHP max-out levels for given hardware configurations.

Anybody interested in contributing information?