PostNuke

...however, now it is available just in the Brazilian Portuguese language.

Inform the paste of your computer where is installed PostNuke, the language that will be used as base of the translation and the language for which it will be translated, and ready! WinLang imports all the variables and it organizes them in way to activate the identification of the disputes and eventual mistakes.

In the export process, the language files are generated automatically in a standardized way and it cleans!

In this first version they are available 3 reports that will serve as documentation base and reference.

Minimum requirements:
Windows 95/98/NT/ME/XP/2000
16Mb RAM and 10Mb available in HD

Site: <a target=_top href=http://www.winlang.hpg.com.br>http://www.winlang.hpg.com.br

I have received suggestions in support forums for setting up multiple sites, but no one seems to know exactly how to use the multisite module to accomplish this. (see me question & response here: http://postnuke.com/modules.php?op=modload&name=PN_Cyboards&file=flat_read&board=3&id=9091&thread=9087)

The problem is with 5 sites, I would have to upgrade all of them everytime there was a tweak to Rogue *and* each module and I'm hoping to avoid this.

Possible? Maybe the fellow that created the module could offer a hint? Most appreciated.

Suppose I have a website about Internet news. I post stories about new websites (http://www.MYsite.com/search.php?query=&topic=1) and about sites that stop/go bankrupt (http://www.MYsite.com/search.php?query=&topic=2).

You have a website about trains (http://www.YOURsite.com/search.php?query=&topic=1) and about planes & automobiles (http://www.YOURsite.com/search.php?query=&topic=2).

I can create a Topic trains on my site and I'll display the news that I call from your website (the full article and people don't have to leave my site). You'll be able to create a topic called New Websites and syndicate my news. We both help each other with content, we keep our visitors, we both have a richer site and less work. It's a win-win situation and everybody's happy. Isn't life swell?

Of course, webmasters would have to be able to grant permission to syndicate their news -or- a source has to be mentioned at all times.

Just my 2 cents... I'm not a programmer so I don't know how and if this is possible, I'm just The Man With The Plan. Muhahaha!

These fixes apply to 0.7.2 and possibly other Rogue versions too.
As usual the GPL blurb applies. I take no responsibility and make no guarantees etc. etc.
It is possible that the language fixes may contain some British English rather than American
English. Although I can think of no specific instances it is a possibility.
All of these fixes will be in use at <a target=_top HREF="http://www.southwest.lug.org.uk">http://www.southwest.lug.org.uk after 1st Jan 2002.
If you are using Linux please do not forget to set the permissions for each file.
The following files are included in the archive:

article.php - Comments were broken so are now disabled. For people who keep article.php for backwards compatability with 0.64.

global.php - (from Stats module) Language clean up for Stats page.

global1.php - (global.php from News module) Language fix for News articles.

wl-navigation.php - Puts Web Links navigation links on a new line.

Fixes for the Brittania theme

theme.php - Various fixes for Rogue usablilty.

style.css - A few colour changes for the theme to make some text readable.

A description and where each file goes is included in the archive.

You can download these <a target=_top HREF="http://www.southwest.lug.org.uk/DJ/PostNuke Rogue 0.7.2 Fixes(Unofficial).zip">here and e-mail me here.

Below is my 'goodbye' to PHP Nuke. You'll likely never see it over there, because I submitted it as news, which means it's moderated:

After recoding most of PHP Nuke 5.0 to force it to work, dealing with docs that are almost incomprehensible in English, putting up with slow support response, horrible testing and coding procedures, lack of code documentation, and the disgusting implementation of an upgrade path from 5.0 to 5.3, LinuxLaboratory.org will be moving over to PostNuke. Read on for more details.

When I got 5.0, almost nothing worked properly. After spending about a month - fulltime - with 3 other guys recoding and bugfixing and testing, I finally got something that, for the most part, works.

Today, I posted in nukeforums or nukesupport (don't remember which) that I had a question regarding the upgrade path from 5.0 to 5.3. The answer I got was something like 'You'll have to go through all of the upgrades in between to get to 5.3, but I would just go to 5.2 until they work out all the bugs'. This prompted me to look around and see what the feedback was like from the community upon the 5.3 release, and sure enough, there were just as many bugs as there were in 5.0, and they were just as serious, and as always, it appeared that the fixes were coming NOT from the developer, but from the community (again).

I understand that this is all for free and all of that stuff, and that's great. But don't expect people to use and be happy with a product just because it's free. Crap is free. Doesn't mean I want it on my doorstep.

I wish the PHP Nuke community luck in all future endeavors, and will still help those in need, as I've helped others who have contacted me in the past. However, as PHP Nuke evolves, I will inevitably become less and less useful.

I hope someday things will change with PHP Nuke, but until it does I find myself with only 2 choices:
1. Download all versions between 5.0 and 5.3, hope all of the upgrades go ok, and then debug, test, recode, retest... PHP Nuke 5.3, or
2. Upgrade to Postnuke .702, upgrade my current site with their handy-dandy script (already tested and works), and move on.

I will be doing the latter.

Best wishes.
njcajun

------------- end ---------

This is not to say that Postnuke is perfect either. I have some real issues with it, some on a fundamental level (code docs, while much better, still fall short in some places), and some on a purely subjective level. However, if I'm going to have to recode things for either reason, I think I'm doing myself a favor going with Postnuke as a base. If niceguyeddie is willing and has time to introduce me to their CVS stuff, I'd be happy to submit code as I write it. This was an option I was NOT given at PHP Nuke, so only about 10 people worldwide that I know of have a PHP Nuke 5.0 site that works as well as mine :-) I'm happy mine works, but it's frustrating to see all the other users out there who fell prey to a nice look and feel without knowing anything about what goes on behind the scenes. The frustrating part is that I don't have time to help everyone, and my code only got to those who sifted the site looking for answers in News posting comments and found 'at line x in file y do this' postings by myself and a few others. CVS would've been a big help.

Anyway, hope to see you all at the site in March.
njcajun

It took me a while to find out were I could put it, is n't it possible to somehow send this the sourcefirge? or another central location?
I am currently really confused were to get (and send) what.