moving up the directory tree

Tuesday 08 August 2006 2:00:04 pm

Hi all,

We have a setup here where I built some websites on the dev server, using the address

http://dev.example.com/newsite1/

but going into production, the site will be

http://newsite1.example.com/

I've worked out that if I don't change the Site URL in design -> Look and Feel, as well as in site.ini, I'll lose the CSS and the whole thing fails to render. But even with the changes in site.ini

[SiteSettings]
SiteURL=http://newsite1.example.com/

and the changes in look and feel, I still seem to get the trailing /newsite1/ on all the links. I've cleared the cache repeatedly, using both the shell script and the GUI. Can anyone suggest somewhere else I should be looking?

Thanks,
David

Wednesday 09 August 2006 1:27:01 pm

Hi, and thanks for your reply.

I'm not actually having a problem with the siteaccess. Rather, the site is by default linking to a directory tree which no longer exists. For example, if I go to my site and I click on the 'mission' tab, rather than pointing me to

http://www.example.org/index.php/mysite/mission

the link is pointing at

http://www.example.org/38www.example.org/index.php/orpheus/mission

because originally I had been developing the site on my development server as

http://dev.example.org/38www.example.org/

(and the 38 was, of course, because it was now running ez3.8). So whereas before the root of the ezpublish install was -not- the root directory of my website, now it is. But the links have not updated to reflect that new reality - they still think all my content is one directory down, as it was on the dev server. Naturally, on my production server this directory does not exist, and so I get a 404.

Is this clearer? The siteaccess is being chosen correctly, but the ezpublish install is generating wrong links for all subcontent, based on the old directory tree.

Thursday 10 August 2006 6:35:44 am

Hi all,

Having verified, now repeatedly, that clearing the cache is not the solution, does anyone have any ideas for other places where directory tree information might be stored? Alternately, is this a bug with the product, and one of the caches is being cleared neither by script nor by the friendly 'clear cache' button? Any thoughts?

Thanks,
David

Thursday 10 August 2006 7:06:29 am

Hello,

OK - found the answer. Thanks to Kristof's comments about the cache, I decided to see if it was a problem with the cache clearing processes. I first ran the script, with a --clear-all, then I ran it from the admin interface, again, clear all. None of this worked.

I then went to var/mysite/cache and did a rm -rf *. This solved the problem.

I would consider this a bug. Does anyone have an explanation for why neither the script nor the admin interface would clear the cache adequately?

Thanks,
David

Thursday 10 August 2006 1:15:33 pm

Hi,

Yes, the user I log in as is the user that runs everything on the box, more or less. So when I cleared the cache, it should have had the same permissions as when I went in on the command line. Additionally, of course, the clearcache.sh was run as that user as well.

Thanks,
David