Jørn Wildt

Okay! i finally thought i had done all the needed things. The only think left was to move the files over to the production server. We are hosting our site exterrnally and i transferred all the files over.Photoshare runs smoothly but pagesetter gives me these messages.

Warning: Smarty error: problem writing temporary file '/home/vhosts/e/f/efront.no/www/modules/pagesetter/templates_c/3fce69be9d62f' in /home/vhosts/e/f/efront.no/www/modules/pagesetter/smarty-2.6.0/libs/Smarty.class.php on line 1144

Yes i know directory rights but it is not that, they are OK. I have tryed to adress the directorys directly and indirect but no go. I hav search the forums and tryed every tip i found , if someone has a smart tip it will be very appreciated.

I have now spent 3 hours on this problem and are giving up.

Konsulenten

It definetely is about rights -- is your templates_c directory chmodded 777? Is it empty (if not, empty it).

J?rg

I know, this should definetly be about rights. The problem is that i have checked and double cheked and triple checked and ..... It does not work i am stuck. I have the exact same rights on these catalogs that i have on the image catalogs for photoshare and photoshare works as a sharm. Can it be something else. Can it be the addressing indirectly / directly ex. 'modules/pagesetter/cache' or does it need complete path.

If i dont find out about this i have to return to paged.

Okay, now it works. And yes Jorg you was right.

I did it the hard way (I did the same thing last night but maybe it was to late and i oversaw something). I deleted the directorys, recreated them and chown/chmoded and like magic it now works. At least no error messages. Maybe a good night sleep made it clearer.

That's the fine thing about computers, sometimes you don't know why it works you just accept it. This is one of these moments.

Kjell
(Konsulenten)

I had this same sort of problem with smarty on another server. I discovered that some setting on the server did not allow remote ftp program i was using to change the chmod settings to 777. i had to go into the server via SSH, change the OWNERSHIP of the directory to match the apache server (NOBODY in my case), then chmod from the command line in SSH.

I have no idea why I had to do it that way but it worked. On the current dedicated server I am using, I never have a problem with changing chmod with an FTP program but on the old virtual private server, I did.

halfelven, you are into something here. I talked to our provider and told him what i meant about his system ;) . He said wait a minute....... O.K try now. And like magic it worked. He did something. I am not sure what

SO halfelven thanks for beleave in me, i started to think that i was losing it. :D