Dizkus

Hi everyone!

I am using 0726 phoenix and can't install 750 because I have so many modules installed and most would not work anymore, plus I have to make the language files for Serbo-Croatian, which is a huge amount of work. I am waiting for next fuly templatable version of PostNuke before I go about doing that.

My problem: I installed the Xantia and pnRender to my PostNuke but themes don't work. pnRender has been workign for quite some time as it was needed for some of my modules. I install and activate themes such as dpXanIris (found on dev-postnuke.com) Then on the theme preview I would get error: cannot write to pnTemp, I gave permissions 777 then got another error which is as follows:

Fatal error: Smarty error: [in userdb:dpXanXPStyleSilver/master.tpl line 2]: [plugin] unknown tag - 'lang' (core.load_plugins.php, line 118) in /home/lasvans/public_html/includes/classes/Smarty/Smarty.class.php on line 1883

Any ideas?

Thanks for your help.

Jadranko.

does .726 have Smarty? I see you installed pnrender and xanthia but...smarty?
does it work with a simple "vanilla" theme like pndefault?
At the sourceforge site I think you can pick and choose certain files for download. Maybe update things that way.
I don't understand why a language file for .726 is good but it won't work for .750. I only care about english and have been lucky I guess to never have to worry about that. Sorry can't help with that.

THanks for the help!

I have downloaded and installed Smarty 2.6.8 from the http://smarty.php.net/download.php

Now I still get the same error with change in line number in Smarty_Compiler.class.php Looking at it I see no 'lang' tag option in select case code, the error points exactly to this problem.

Fatal error: Smarty error: [in userdb:dpXanIris/master.tpl line 2]: syntax error: unrecognized tag 'lang' (Smarty_Compiler.class.php, line 580) in /home/lasvans/public_html/includes/classes/Smarty/Smarty.class.php on line 1088

Any ideas on thisone?

Thanks again.

Basically your missing the 'lang' plugin. This will be in the xanthia plugins directory of .750 but probably wasn't available in the release candidates built for .726. There was no formal release of XTE for .726 so you're likely to see issues like missing plugins as people write and testing things on .750.

In short your running an unsupported combination and something that was never formally released for use on production sites.

-Mark

Thanks for such a quick response. At least I now know what the problem is so that I can peacefully give up. :( Would you suggest me installing Xanthia v. 750 on my 726 Phoenix?

Is there separate download for Xanthia or I need to take it out of PN 750?

Thanks again.

I'm not suggesting anything..... As i've said your running an unsupported combination and, thus, how you choose to maintain that combination is up to you. You may get away with just the plugins directory but I can't and won't 'recommend' it.


Xanthia is an integral part of the PN distro.

Bottom line is .750 remains the latest stable and supported release of PN (although shortly to be replaced by .760).

-Mark

Thanks Mark, I am so lucky to receive your response so fast. :)

I guess I will give up on Xanthia themes for now and wait for fully templated .800 nuke release, sometime in summer?!!

Thanks a million for your help.

This was the site in question: [site removed - markwest]

Yadranko.

One last thing about still running .726....

You have made sure that you've manually applied the relevant security patches found in this advisory? .726 can no longer be considered a secure release....

-Mark

Yes, I got PN sa 1, 2, & 3

Now you got me worried again. I now may have to update sooner than I wanted. But a word on the side: up to now, my 726 workd flawelessly. knock on wood :)

Thanks again.

Not the same thing.... A further advisory was issued against all versions prior to .760rc3 including .726. A formal patch was issued only for the latest stable version (.750) - no patch was issued for .726.

I did include the code diffs so people could manually make the changes for .726 however these are provided 'as is' and totally unsupported.

The downside of open source is that you don't have the luxury of missing out steps on the upgrade path. Any security issues are always made public.

Personally if I was in your position my steps would be to make the changes in the diffs I posted and then start testing your modules on the latest .760 release candidate so you can work out what does and doesn't work ready for an upgrade to .760 when it's formally released.

The vast majority of modules can be made to work by either getting the latest version of the module or enabling support for legacy modules. Any modules that still don't work have the potential for exploitable security issues and I would consider dumping these in favour of other solutions.

-Mark

Wow, I was completely unaware of this. I gotta go back to that forum and read closely to see what I am to do. Thanks for removing my site, hopefully I don't become a victim all too-soon.

Thanks for your tips and the hard work, I greatly appreciate it.

Aloha!