<div>Problem turns out to be browser cache. If I delete all temp files and cookies the new version shows up. </div>
<div>Is there a way to make the browser always look at the server for uploads?</div>
<div> </div>
<div>Launa</div>
<div><br><br> </div>
<div class="gmail_quote">On Thu, Jan 29, 2009 at 3:01 AM, Jan Erik Moström <span dir="ltr"><<a href="mailto:lists@mostrom.pp.se">lists@mostrom.pp.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d"><br>On 28 jan 2009, at 22:41, Launa Morris wrote:<br><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">It has actually had this same problem for weeks. I also noticed that files uploaded after I upgraded last summer are listed under webservd.<br>
</blockquote><br></div>It could be that the web server is running under the "username" webservd while you have another username, let's say 'X'. If you log into your account and look at the listing (either using the command line or your ftp program) you should be able to see some kind of listing that looks something like this<br>
<br>drwxr-xr-x@ 1 X staff 4594 17 Jan 16:10 uploads<br><br>If I add some codes to that to better being able to explain<br><br>-rw-r--r--@ 1 X staff 4594 17 Jan 16:10 logo1.jpg<br> 111222333 4 55555 666666666666 777777777<br>
<br>7 - the directory name<br><br>6 - when the directory was created/changed<br><br>5 - which 'group' the directory belongs to<br><br>4 - who owns the directory<br><br>3 - what permissions all users have, in this case 'rx' = read and<br>
execute which means that anyone can look into this directory<br><br>2 - what permissions users belonging to the group have, in this<br> case 'rw' = read, write. All users belonging to this group<br> can look into this directory<br>
<br>1 - what permissions the owner have, in this case 'rwx' = read, write<br> and execute. In other words the owner can create files in this<br> directory but no one else<br><br>If it looks like this on your server and the server is set up to run as 'webservd' and you have the username 'X' it means that the web server isn't allowed to create files in that folder (can't upload). If so, you need to arrange so that the web server can write to the directory - the best way to do this varies depends on how the server is set up so you better ask the people who runs the server. (there is a simple way but it might be unsafe)<br>
<font color="#888888"><br> jem<br></font></blockquote></div><br>