PostNuke

Please stay tuned for further developments and checkout: MaxDev and Spidean

This is a very exciting prospect and I look forward to participating, and along the way bringing the PostNuke, PHP-Nuke, eNvolution and MaxDev versions of AutoTheme together to be fully compatible and contain the same feature sets, commands, etc.

Also in the works is an alignment of the GPL and Commercial AutoTheme versions to work easily together and be portable across the platforms. Look for AutoTheme 1.5 Beta 2 and AT-Lite .7 very soon!

Good news for theme designers: the new versions and their themes will function and be optimized for PostNuke, PHP-Nuke, eNvolution and the new MaxDev project. Great features, great portability and great choices!

Footnote: 1

POSTNUKE COMMUNITY CODE OF CONDUCT

PREAMBLE
Your commitment to this Code of Conduct in all Community areas, which shall apply to all forums, chat areas, comments, mailing lists and/or other message or communication facilities designed to enable you to communicate with the Postnuke community (collectively, "the Community"), ensures a positive experience for all our users.

Postnuke, postnuke.com, The Postnuke Project and the Postnuke staff (hereafter referred to collectively or singularly as "Postnuke" or "PN") are not responsible for the content or activities of users in any such Community area.

RESPECTING OTHER USERS
Members of the PN Community shall be obliged to treat each other with mutual respect. Using the Community to threaten, harass, stalk, or abuse other members or PN developers or staff participating in any Community area will not be tolerated.

PN will not tolerate disruptive activity, such as persistent off-topic comments and postings or statements that incite others to violate this Code of Conduct or participate in activities that are not conducive to the well being of the Community as a whole. Registered users must certify that they are over the age of 13, and are expected to act accordingly. This Community is a vibrant and positive place. We'd like to keep it that way.

The PN Community is a place where developers and users can collaborate, integrate and participate in the design and progress of Postnuke and support each other in furtherance of same. PN is not a forum to air your political views. Comments that derogate another member or group with regard to race, gender, religion, age, national origin, sexual orientation, disability or socio-economic background shall be considered a de facto violation of this Code of Conduct and will be dealt with accordingly.

The PN staff will delete posts and comments that do not comply with this Code of Conduct. Repeated violations may result in further action, up to and including banning users from the Community.

NO SPAM
Please don't spam the Community. Spamming includes sending identical and/or irrelevant submissions to many different forums or mailing lists. Usually such postings have nothing to do with the particular topic of the group or are of no real interest to those on the mailing list or forum.

PN reserves the right to take such action as PN sees fit up to and including removing offensive messages and/or banning a user at any time, with or without notice, from any or all Community areas for spamming.

The Community areas may be used to provide supplemental information regarding your own business (provided that you do not use spam to provide this information); however, the Community areas are not designed to be used as the primary mechanism for operating your business or providing core information about your business. Any use of the Community areas for commercial purposes is solely at your own risk and PN has no liability for such use.

The preceding shall not be construed to prohibit or discourage members from posting links to their own websites where commercial services may or may not be offered. Building web sites is, after all, what PN is about.

ENCOURAGE, DON'T ABUSE
PN's core developers spend countless hours to provide you with a robust content management system. They are not paid for their work. Many of our module, block and theme developers also offer their hard work to the Postnuke Community with no expectation of any compensation other than the satisfaction of creating something that will be enjoyed and utilized by PN users worldwide. Likewise, many of them are not paid for their work. They do not owe you anything, however when you choose to use Postnuke or the modules, blocks and themes that are offered for free to you, you do owe the developers, at a bare minimum, respect for the time and effort that they have spent. Abuse or harassment of developers regarding their efforts or their release timelines will not be tolerated.

YOU ARE RESPONSIBLE
You are responsible and liable for all of your activities while participating in the Community areas.

PN reserves the right to remove at any time, with or without notice, any posting that violates this Code of Conduct.

You are responsible for any actions you may take based on advice or information you receive online. Use your own good judgment when evaluating information provided through any Community area; remember that the information provided could be from people of any age and experience level. The decision to conduct transactions with anyone is your own and you should conduct your own research prior to making any decisions.

UPHOLD THE CODE
]In helping to make the Community a great place to meet, collaborate, support and share, you must do your part to uphold this Code of Conduct.

PN reserves the right to immediately terminate or suspend access to any Community area for violations of our Code of Conduct, or at the staff's discretion to deal with situations or behaviors that do not comply with the spirit of this Code of Conduct, although such situations or behavior may not be addressed specifically herein.

PN also reserves the right to amend or change the Code of Conduct at any time with or without notice. You agree to periodically review this document to ensure you are doing your part.

P.S. Anyone have a suggestion for an OpenSource Dating and an OpenSource Classifieds module that will work with PN v.7.2.3 or .7.2.6?

Those are the only two additional modules I would like to add at this time.

Footnote: 1

Credit where credit is due goes to:

- Drak at HostNuke.com - he's not only donating the servers and bandwidth for the main site (now, two fully dedicated boxes), but we also thank him for all the time he dedicates to the project.

- The team at PNphpBB (CarlS and BatPuppy) for working tirelessly in upgrading the software at the heart of our support forums. It's not an easy task and we really appreciate all their time and energy spent on coding pnPHPBB, continually improving it, and making it work for our support forums so we can support you guys. They just recently released PNphpBB2 v1.2 and work has already begun on v1.3. Way to go, guys!

So on behalf of everyone at PostNuke and the community of users, a heartfelt THANK YOU goes out to all of you to express our appreciation!

This release has security updates, several cosmetic changes as well as usability changes we're sure you'll enjoy using. You can download here: http://download.postnuke.com/pafiledb.php?action=category&id=45

Change Log
HTML 4.01 & CSS Compliance: Credit to Mark West, Brandon Harvey, and larsneo for taking on the project. This was a task that required touching many files within the system to make sure it all parsed correctly and validated.

Permissions Systems Updates: Credit to Marc Maes who contributed the code on the main mods site and thanks to larsneo for integrating into the main core. Additional credit goes to Adam and Mark West for code refinement. The new permissions provides enhancements to inserting permission, in-table editing/inserting and adding of permissions, filtering of shown permissions allowing you to show all the permissions that apply to a specific group. There are layout refinements and updates the configurations.

A note of special thanks and credit goes to Andreas (aka larsneo) who went through every module ensuring that all have the relevant permissions calls and the WHERE clause fixes were applied to all modules as appropriate to prevent any potential SQL injection issues.

ADOdb – Credit to larsneo Database Abstraction Layer Upgraded to 3.60: More Information about ADODB can be found at http://php.weblogs.com/ADODB_Manual

AvantGo - Mobile News Module Update: Credit to larsneo .726 note: permissions for 'Stories: Story’ and 'Topics: Topic’ components are fixed

As many of you know the AvantGo module allows you to pull information from the web to read on your PDA, Pocket, or next-generation phone.

Autolinks Permissions Updates: Credit to larsneo. Fixed permission schema, enhanced module security against script injection

Admin Message Update: Credit to aarrog. Applied patch #275 (use permissions to view admin messages)

A big thanks and credit goes to Michael Cohen – for providing basic source code auditing and due to various security related fixes over the complete code base an update is highly recommended.

New System Admin Icons: Credit to vworld.

- Various fixes and updates to language files
- Print Page Update
- New stats icons added
- New print page and refer article icons added
- Increased size of submit boxes
- New members list icons
- New members list title icon
- Updated topic images for a more unified look/feel
- Fixed empty line behind closing ?> tag (thx to geekster)
- Updated WHERE clauses [larsneo]
- Added default table type entry for pnconfig array
- Fixed TEXTAREA problem in error.php
- Minor fix in footer
- Backport of .8 fixes
- Additional HTML compliance fixes
- lensdebug.inc.php - backported .8 fixes
- pnAPI.php - removed re-correction of & html entity for html
compliance. - pnHTML.php - backported .8 fixes
- pnMod.php - added array check on args (thx to rabbitt)
- pnUser.php - fix for bugs #339 and #389
- queryutil.php - backported .8 fixes
- security.php - fixes for generic/specific permission checks (thx to
Ben Wynn)
- banners.php - fixed permissions
- big.php - fixed permissions
- rss.php Addresses patch #233 (CDATA tag not removed when fetching
RSS) - Includes/Search: HTML compliancy issues fixed and permissions
issues regarding results count.
- Install Issues: Fixes and installation updates
- Web Links Updates included HTML compliancy issues and log message
issues.

Last but not least thanks to InfoPro, pnCorps, and the community for testing, support and feedback on the release. And I apologize in advance to anyone I didn't mention in this post. Everyone has done a great job and deserves every bit of recognition they receive in the community and Open Source world!

Another major part of telekiosk Project is the telekiosk website. Telekiosk website is based on Postnuke .723. In telekiosk website, you can find all information about Afghanistan. Its a kind of portal linking the Afghan community to the rest of the world.

I am the web developer for this project. If anyone of you is interest or willing to help me in localizing Postnuke to Dari and Pashto languages (Afghanistan national languages), please feel free to contact me at farshid@afg-consulting.com or ahmad.farshid@undp.org.af

Thanks to Postnuke Development Team!!!

Being new to PostNuke, the first thing I did was to download the site to my PC so I could play with IT. DoctorVAR.com consists of 28 subsites or separate PostNuke installs linked together. We're using the Pixel-Rave-02 theme from PixelMayem (<a href="http://www.pixelmayhem.com/gallery/"target='_blank'>http://www.pixelmayhem.com/gallery/). I began to explore all of the directories and files. I found that in each of the subsites the Pixel-Rave02/ folder contained a theme/ folder. In the theme/ folder there was a file named style.css. This was the file that held the properties of the link colors.

I opened up the program "The GIMP" - a free image manipulation program that comes with most major Linux distributions and used it to find a new color. I looked up the hex value for the new dark blue color in the format #XXXXXX where the X's are hexadecimal numbers and substituted it.

I had a hunch that all of the css files in each of the subsites would be identical to the one that was used for the home page, but just to make sure I used the unix 'diff' command to check to see if they were all of the same. They were, which made my life easier since I could write a simple shell script to do the propagation of the files. I ssh'ed back into the server and created my new script in the home directory, like this:

vi propagate_script.sh

This brings up a new file named 'propagate_script.sh' in the vi editor. I pressed 'i' to enter insert mode, and typed:

cp /var/www/html/themes/Pixel-Rave-02/style/style.css /var/www/html/subsite1/themes/Pixel-Rave-02/style/style.css

cp /var/www/html/themes/Pixel-Rave-02/style/style.css /var/www/html/subsite2/themes/Pixel-Rave-02/style/style.css

and so on for all of the subsites (using copy and paste). I closed vi by pressing Escape, and then typing ":wq" to write out the file to the disk and quit. I made the script executable with the command:

chmod 700 propagate_script.sh

Then I opened up the style.css file that governed the home page with:

vi /var/www/html/themes/Pixel-Rave-02/style/style.css

I put in the new text color value (#xxxxxx format) in the 'A:link' line after the COLOR: parameter. I also made alterations to the 'A:active' 'A:visited' and 'A:hover' lines. I changed the 'TEXT-DECORATION: none;' parameter to 'TEXT-DECORATION: underline;' on the 'A:hover' line to make the links underlined when the cursor moves over it. Originally it was:

A:hover { FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: #1E90FF; FONT-SIZE : 11px; TEXT_DECORATION: none; BACKGROUND: none; font-variant: normal; font-weight: bold;}

and I changed it to:

A:hover { FONT-FAMILY: Arial, Helvetica, sans-serif; COLOR: #1E90FF; FONT-SIZE : 11px; TEXT_DECORATION: underline; BACKGROUND: none; font-variant: normal; font-weight: bold;}

You can see what change I made in bold. To change the color you change the value (in this example #1E90FF - a light blue) after the "COLOR:" parameter, use "font-weight:" to make the text bold, and so forth. Next, I made sure that I was in the correct directory and typed:

sh ./propagate_script.sh

to run my script. It propagated all of the changes to all of the subsites. I manually checked to make sure that it worked as desired, and it had. The link color changes were complete.

We're slowly building our website theme, adding new blocks and allowing committee members content submission access to achieve a site that is self maintaining.

If anyone is interested in helping develop the site's theme please contact info@dragonmeet.com.

Finally we'd like to offer our thanks to the PostNuke programmers and designers!

Click Online can be seen on BBC World TV at the following times (GMT):

Thursday 19:30 | Saturday 00:30 / 06:30 | Sunday 10:30
Mondayyy16:30|| Tuesday 00:30 / 07:30y| Wednesday 13:30