Topic: ez32-1 design on winXP -> serve on LINUX -> broken links

Next topic

Author	Message
cfa cfa	Friday 10 October 2003 11:45:58 pm hi, i am designing my ez32-1 site on winXP where everything is working out just fine. BUT after uploading the site to the linux server things don't work well anymore. the problems stated below did not occur when i used eZ3.1-1, uploading a site that way was a breeze! the problem seems to be images and links. - there is a problem with the path, especially in the admin section, where somehow the directory name of the winXP install is included (like http://myserver.com/winXPdirectoryName/index.php ) - uploading images won't work well, the image won't show up. (i am running another site on the same server which was setup from scratch on the linux machine and things work ok, so there is no trouble with imagemagick or so...) i do the following steps: - clear the cash from within eZ on winodws - zip the directory and FTP it - use phpMyAdmin to transfer the database - upload a special version of the settings directory (with override ini files for linux, ...) - modfix.sh - log in and clear cache again what i tried out to fix this: - manually deleted cache files in the /var directory (but cache-blocks are too many, so i never deleted them) - setting directory permissions to 777 to improve image upload .... any ideas?
Aya Brea	Saturday 11 October 2003 2:15:00 am If you just design on windoze and then move it to a nix box. Sure that your configuration file has the problems. Carefully examine it. Manually clear the /var folder again, don't worry, cache will be created again.
cfa cfa	Saturday 11 October 2003 1:14:41 pm i double checked the config file. even did a auto-search in the whole settings directory for the win-xp path name that keeps showing up in the admin-ez path under linux, but nothing could be found. now, do you recommend killing the whole cache-block directory? will eZ recreate the directory structure?
cfa cfa	Monday 13 October 2003 3:49:32 am below you will find the "site.ini.append" file from the directory "settings/override/", and two site access files "site.ini.append" which are "frontend" for the user frontend utilitzing the "mydesign" design and the other site-access file for my own administrator called "myadmin". <?php /* #?ini charset="iso-8859-1"? [DatabaseSettings] DatabaseImplementation=ezmysql Server=localhost Database=xxxx User=xxxx Password=xxxx Charset=iso-8859-1 Socket=disabled [Session] SessionNameHandler=custom [SiteSettings] DefaultAccess=frontend SiteList[] SiteList[]=frontend SiteList[]=myadmin SiteName=xxxxx SiteURL=localhost/xxxx/index.php [DesignSettings] # The standard design, is used as fallback design # if the element is not in the sitedesign StandardDesign=mydesign # The design of the site #SiteDesign=mydesign AdditionalSiteDesignList[] AdditionalSiteDesignList[]=admin AdditionalSiteDesignList[]=mydesign AdditionalSiteDesignList[]=standard AdditionalSiteDesignList[]=demo [SiteAccessSettings] CheckValidity=false AvailableSiteAccessList[] AvailableSiteAccessList[]=frontend AvailableSiteAccessList[]=myadmin MatchOrder=uri SiteAccessList[] SiteAccessList[]=frontend SiteAccessList[]=myadmin HostMatchMapItems[] [ImageSettings] NewDirPermissions=0777 NewImagePermissions=0666 SmallSizeWidth=100 SmallSizeHeight=100 MediumSizeWidth=150 MediumSizeHeight=150 LargeSizeWidth=500 LargeSizeHeight=500 ReferenceSizeWidth=500 ReferenceSizeHeight=500 ScaleLargerThanOriginal=false OriginalDir=original ReferenceDir=reference VariationsDir=variations [MailSettings] Transport=sendmail TransportServer=localhost TransportUser= TransportPassword= / ?> :::::::::: site access file for "myadmin" site ::::::::::::::::::::: <?php / #?ini charset="iso-8859-1"? [SiteSettings] DefaultPage=/content/view/full/2 LoginPage=custom [SiteAccessSettings] RequireUserLogin=true [DesignSettings] SiteDesign=admin [ContentSettings] TranslationList=ger-DE;eng-US [FileSettings] VarDir=var/mydesign [RegionalSettings] Locale=eng-US ContentObjectLocale=eng-GB TextTranslation=enabled / ?> ::::::::::: site access for my "frontend" site ::::::::::::::::::::: <?php / #?ini charset="iso-8859-1"? [SiteSettings] DefaultPage=/content/view/full/73 IndexPage=/content/view/full/73 ErrorHandler=displayerror LoginPage=embedded [SiteAccessSettings] RequireUserLogin=false [DesignSettings] SiteDesign=mydesign [ContentSettings] TranslationList=ger-DE;eng-US [FileSettings] VarDir=var/mydesign [RegionalSettings] Locale=eng-US ContentObjectLocale=eng-GB TextTranslation=enabled */ ?> :::::::::::::::::: directory tree of var/ ::::::::::::::::::::: var --cache ----codepages ----ini --mydesign ----cache ------content --------admin ----------full ------------eng-GB ------override ------template --------compiled ------template-block -------- ... ------translation --------root-36e48c5d322c489dd3ee4e51ffda1494 ----storage ------original --------image ------reference --------image ------variations --------image --storage ----original ------image ----reference ------image ----variations ------image
Claus Jensen	Monday 13 October 2003 3:59:13 am Hi, Could it be you are running into this bug? I had problems with UPPERCASE letters with SiteAccess in 3.2-1. Check here: http://ez.no/developer/ez_publish_3/bug_reports/cant_use_uppercase_in_urimatching Also ez will recreate the template-block, or whatever cache you mean, so just delete it. best, claÜs
cfa cfa	Monday 13 October 2003 7:30:21 am no, i don't think i have problems with upper/lower case. but i do think the issue is related to the cache. because i have no problems adding database records... eZ is remembering the old URL and old BOOKMARKS of database entries after i changed them. and there is the problem with images... does anybody think i have an error with my var/ directory definition which goes somewhere called var/mydesign ??? would i have to maybe change the bin/modfix.sh command to fit var/mydesign???
cfa cfa	Monday 13 October 2003 8:49:27 am hi, i just did what you said and deleted the content of the var directory. all of it. re-run modfix.sh and now... i don't see images anymore when i upload them. the directory structure was recreated automatically, as you mentioned above. but, when i reversed to the old var directory, uploading images was possible again... (the old var directory was chmod to the apache server by the sysadmin, my new var directory had 777 permissions). any ideas?
Luc Chase	Saturday 29 November 2003 12:50:54 am My problem is similar but not exactly the same as yours... some of my observations may help. I develop on WinXP and deployed to Linux. Although I had some initial problems, ImageMagick is fine now. But here is what is happening. If permissions on the var directory are set to say 777, I can add content via the xxx_admin site, but the main site only displays the first page; all links fail to return any new content and the site stays on the first page. If I delete the CONTENTS of var/cache and var/sitename/cache directories and change the permissions of the var/cache and var/sitename/cache directories to say 400; the site works properly again, finding all the existing content (including pictures); but I then can't add any NEW content (page not found errors). The Web Application Service Provider