PostNuke

PN needs a module that can be used for client/company relations, something customizable through an admin tool and having a wide range of prospective uses. It could have different fields, giving the company the choice of what that field is called, what pertains to that particular field, and how it effects or is effected by other fields within the module and database. After the customization is applied, a database table(s) is created with the customized module and ready to go. One option for such a module could be a whole sale company giving clients log in access to their accounts, the ability to order/reorder items, check current balances, or the availabilty of merchandise or services all from their browser where ever they may be located. While another company could be using the same module for something totally different, or similar but fitting more to their needs. I think in order for PN to go to such a level, the module must first be able to be made to fit their needs, and then allow them to choose what they do need. This was just something I thought of while discussing PostNuke with some colleagues and explaining to them how far it could actually be taken. The rest of PN would compliment something like this very well, considering everything else it already offers. I am not knowledgable enough of php to actually be able to do something like this, but I thought i'd at least mention the idea. I'm sure I'm not the only person to think of something like this and apologize if it has already been suggested before now.

To achieve our goal, we will use a global variable named HTTP_ACCEPT_LANGUAGE which tell us the prefered language of the user.


Now we need to hack the file pnAPI.php (under the includes directory).

Go to the pnInit() function and add this line somewhere at the first lines:

global $HTTP_ACCEPT_LANGUAGE;



Now that we know what is the language that the user wants, we just need to set the PostNuke language to it or to the default site's language if we do not support it.
This can be done with a simple switch by replacing the original lines (under pnInit() function) :
this are the original lines

// Load global language defines
if (isset ($lang) && file_exists('language/' . pnVarPrepForOS($lang) . '/global.php')) {
$currentlang = $lang;
} else {
$currentlang = pnConfigGetVar('language');
pnSessionSetVar('lang', $currentlang);
}

with something like this:

---

This examples search for English, Spanish and German languages.

// Load global language defines
if (isset ($lang) && file_exists('language/' . pnVarPrepForOS($lang) . '/global.php')) {
$currentlang = $lang;
} else {
$BrowserLang=substr($HTTP_ACCEPT_LANGUAGE,0,2);

switch ($BrowserLang) {
case "es" :
case "ES":
$currentlang = "spa";
break;
case "en":
case "EN" :
$currentlang = "eng";
break;
case "de":
case "DE" :
$currentlang = "deu";
break;
default :
$currentlang = pnConfigGetVar('language');
} // fin del switch
pnSessionSetVar('lang', $currentlang);
}


As you can see with only a few lines of code your users will not have to click on their flag to choose their favourite language.


For those about to Nuke....we salute you
Jorge Alvarez
jalvarez at regamallorca dot com

Primera Technologies has been creating PHP and mySQL software for years. Now we have installed PostNuke for our community site where we communicate with our customers. Check the Community link at www.primeratechnologies.com.

Footnote: 1

Vision:
pnCommunity is a "super-module" or suite of integrated modules aimed at strengthening communication and project management across the entire Postnuke Community - developers and end-users alike. On many levels, pnCommunity should serve as a replacement to SourceForge.net built around the core Postnuke product. While initially built to serve the Postnuke community, pnCommunity will also be an aggressive first step towards a corporate "killer app" which can further strengthen Postnuke's growing foothold on corporate Intranets.

Many of the components listed below exist either as current PN or PHPNuke modules or as other open-source projects. To build pnCommunity, we need to bring the best elements of each of these apps together under a common, tightly integrated platform which further dovetails cleanly into the pnCore.

Preliminary Components:

01. pnCVS
Building on Jan Schrage's work, this will tie CVS release management to project milestones.

02. pnFunctions
A dynamic function library for developers ... similar to the function library found at PHP.NET bur dedicated to PN functions.

03. pnProject
In many ways the spine of pnCommunity, pnProject provides project management tools like task tracking and resource assignment.

04. pnFeedback
Tied closely to pnProject and potentially many core modules, pnFeedback will provide robust tools for generating, tracking and acting on bug reports, feature requests and documentation requests.

05. pnForums
Built on the forthcoming Comments API, pnForums will eventually replace current support and development forums. Tight integration will allow moderators to generate bug reports, feature requests and other key information from forum posts. Conversely, other elements of pnCommunity will auto-generate topics/posts with in pnForums.

06. pnKnowledge
Fed by pnFeedback and pnForums, this tool should help expand and flesh out online Postnuke documentation.

07. pnDevelopers
Developer-specific member list and user details. Think of it as a developer resume which can be used by project leaders. Allows users and devs to rate developers much like the Developer Profile on SourceForge.net.

08. pnPortfolio
The next generation YAPNS. Creates a gallery of categorized Postnuke sites. Provides an announcement tools for new or updated PN-based sites.

09. pnLibrary
A tool for posting and announcing new Themes, Modules and Blocks. Submission to pnLibrary will automatically post a News article in the appropriate PN subdomain and potentially generate a topic in pnForums for discussion of the new release.

10. pnJobBoards
A place for developers to announce their availability and for end-users to post Postnuke related projects/jobs. Think www.guru.com, but Postnuke-specific and tied into pnDevelopers.

11. pnRatings
Built on the Ratings API, pnRatings will allow user rating of the various elements of pnCommunity.

12. pnPrinter
Online resources (particularly documentation) will be made readily available in a printer-friendly format.

To review the first draft of the pnCommunity vision document in it's entirety, please visit <a href="http://developer.hostnuke.com/modules.php?op=modload&name=XForum&file=viewthread&tid=6" target=blank>developer.hostnuke.com: Dev Forums.

As a final note, this will be no small project. The pnCommunity team always welcomes folks from all corners of the Postnuke community to join our ranks. If you are interested lending your talents to this project, please email Doug Daulton (apakuni@ursastudios.com).

Thanks to the pnCommunity Team and additional project sponsors Gregor J. Rothfuss (Gregor) and Steve MacGregor (Grape).

Regards,

Doug Daulton (Apakuni) - Project Manager
Curtis Hays (stratagem) - Team Lead, Website Services

Footnote: 1

Administration:

John Cox - Project Manager
Email: john.cox@postnuke.com

Gregor J. Rothfuss - Director of Technical Operations
Email: gregor.rothfuss@postnuke.com
nick: gregor

Steve MacGregor - Director of Support Operations
Email: steve@grape.dyndns.org
nick: grape

Technical Operations Teams:

Module Development:
Gary Mitchell - Team Leader
Email: gary.mitchell@postnuke.com
nick: wb9tpg

Core Development:
Greg Allan - Team Leader
Email: adam_baum@ndezign.com
nick: adam_baum

CVS:
Jan Schrage - Team Leader
Email: jan.schrage@postnuke.com
nick: jan

Theme System Development:
Marty Vance - Team Leader
Email: dracos@thedragonsforge.com
nick: dracos

Security:
Brian Erdelyi - Team Leader
Email: brian_anon@hotmail.com
nick: Bog_

Server Operations:

Position Open

Quality Assurance:
Frank Besler - Team Leader
Email: besfred@gmx.net
nick: besfred

Support Operations Teams:

Documentation:
Drew Vogel - Team Leader
Email: andrew.vogel@uc.edu
nick: vogelap

PR/Marketing:
Steve MacGregor - Team Leader
Email: steve@grape.dyndns.org
nick: grape

IRC Services:
Curtis Hays - Team Leader
Email: stratagem@postnuke.com
nick: stratagem

Website Services:
Curtis Hays - Team Leader
Email: stratagem@postnuke.com
nick: stratagem

Developer Relations/ Staffing:
John Robeson - Team Leader
Email: john.robeson@postnuke.com
nick: Johnny

Customer Service:

Position Open


For further information please contact steve@grape.dyndns.org

Footnote: 1

Footnote: 1

Note: We have actually been phpnuked and post nuked for over a year or so. We have simply waited til stuff was really screwed up before we announced on YAPNS.

Footnote: 1