PostNuke

"As for you second problem try the following : to call a language dependant style.css you will need to modify your header.php and add the following code :





### at the top change :





global $index;





### to :





global $index, $lang, $newlang, $language;


if (isset($newlang)) {


$style = $newlang;


}


elseif (isset($lang)) {


$style = $lang;


}


else {


$style = $language;


}





### and then also in header.php change the line of the style link





echo " ";





### to :





echo " ";





That's all you need to edit but now you will need to create a folder for every language your site supports.


themes/NukeNews/english/style.css


themes/NukeNews/french/style.css


themes/NukeNews/dutch/style.css





Make sure the names of those folders correspond to the names in the language files.








OR another way is e.g. to leave the style folder as is and add language.css files in it.





echo " ";


themes/NukeNews/style/english.css


themes/NukeNews/style/french.css


themes/NukeNews/style/dutch.css"





also ppl. please change locale to locale translation for dates to ._NukeLike_ translation(maybe small date.js file will do this?).

With all due respect this seems to be a problem with phpwebsite and phpNuke as well. Given the fact that several people feel like using another forum, one that is bit more up-to-date and flexible, I think that this is the perfect linksmanagement script. Very well written. Take a look at the code at sourceforge. Easily translatable, themeable. And loads of options. Would be a perfect add-on if not replacement alltogether.

Since nuke already contains the foundation for forums (e.g. posted comments and news submissions), wouldn't it make sense to leverage this code base to create a simple forums system?





This would make a great forums system that's not to complex and it has the same feel as the news submission. It seems that this shouldn't be a difficult hack for someone who know's nuke well.





Thoughts?

All these themes have been fully revised and optimized for TheMutant(from now nothing is harcoded). Fully tested with a large variety of browsers(including N4 series, konqueror and of course Ie N6 Op5...). All(a big word no;)?) my previous errors have been corrected(missing tbody tag....)


All Feedback and errors are really welcome to help me in the future themes Dev(kodred@babylone6tem.com).



Download this pack HERE.




{8-| KodRed |-8}

Some of you might ask now: Why would this be a security leak?



Well, have a look at my userpage. You can see a small gif with text around it that says Klicke hier für Hilfe.

Can you see it? Cool, I can see you too, because this is Javascript and it allows me to see your IP-address, the time you have spent looking at that particular page, the browser, version of the browser, platform, and the referrer. If you click on the picture, a chat window opens up, but if I would try to be really funny I could open up a chat-window as well from my side.

So, the security leak is:

• By allowing anything with the src-attribute you open up a security hole.




• Almost everything that is possible with Javascript can be done with your website. This includes:




• A violation of the privacy of your website's members




• Unwanted windows might open up




• Someone could claim with my example script to be part of the staff of the website and ask for a password or do any other harm to the visitors of your site

So please don't allow all html-tags. :)



Greetings from the sunny Germany!



Sascha



P.S.: Please don't delete my account here, I will take off my javascript-signature after a few days so that everyone has had enough time to test this - I promise I won't do any harm to your websites visitors nor will I monitor them! :)

For the geeks : Here a piece of code that could be in any of the core pages. A temporary variable basically reads or collects all the current code, and then calls a function table(), the actual table that will hold and display all the code.


That function table() is defined in a page tables.php that is part of a theme. Meaning everybody that makes a theme can fool around with that tables.php as much as they want without ever having to touch any of the core pages.


An example, just a snippet of random code I copied and pasted to demonstrate the principle :


$htmlsrc .= eregi_replace("_", " ", $sites_array[category_name]);


$htmlsrc .= "  ";


$htmlsrc .= $functions_16 . $sites_array[hits_in] . "";


$htmlsrc .= "  " . $functions_17;


$htmlsrc .= $sites_array[hits_out] . "";


$htmlsrc .= "rnrnrn";





Now we put the code from the core page in the function table() as defined in tables.php


$html .= table("100%","center","",$htmlsrc);





and reset or rather unset the variable





unset($htmlsrc);





As you can see there was some html stuff in the code as well that doesn't show up in the post of course, but that's not really relevant. You probably get the idea.





I've been doing several themes for phplinks with this system (credit for the tables system goes to phpDude) and I have been amazed by the power and flexibility of it.





Not only will it make it a lot easier to make new themes. By getting ALL themeable stuff out of the core pages. Those themes will basically stay compatible with all future upgrades as well. And by just changing stylesheets you can go a long way.





And if we could get the folks at phpwebsite and maybe even phpnuke - after they cooled down probably - on board this would be a tremendous step to break away from the YANWS look of most nuke forks.





Comments ?