Hi! I think I have a bug to report. I am in the process of making my first Zope web-site, so I do not know much about Zope yet, but I will try to explain as clearly as I can anyway. I have a folder, /Foo (actual name removed), which contains the actual project. Everything related to that site is in there, normally. In that folder, I have redefined standard_html_header and such, and created a few subfolders. One such is /Foo/FooImages. In it, I put all of my site-wide images. About half an hour ago, I added a small image in there: coin_rond_bleu. It was a blue rounded "corner" for a table. Since I was fighting with the Gimp at the time to get that "corner" just right, I had to delete the thing and re-import it from my home a few times. Eventually, I got frustrated. Modifications I was making in the Gimp did not seem to affect what I saw in Zope. I eventually deleted /Foo/FooImages/coin_rond_bleu once more, and re-imported the image as /Foo/FooImages/coin_rond_bleu2. That actually worked. It seems that petit_coin_rond, even when officially "deleted" by Zope, still survives somehow, and haunts my database. Ghastly. Now, if I import an image under /Foo/FooImages/petit_coin_rond, viewing it shows me the ghost of petit_coin_rond, get this, *scaled* to the size of the image I imported. The upshot, of course, is I can easily create blue rounded corners of all shapes and sizes... :-) Is there any way to kill it? Is this a known bug? Thank you for the software and the information, and happy coding. Jérôme Loisel _______________________________________________________ Get 100% FREE Internet Access powered by Excite Visit http://freeworld.excite.com
On Sat, 29 Jan 2000, [iso-8859-1] J�r�me Loisel wrote:
Eventually, I got frustrated. Modifications I was making in the Gimp did not seem to affect what I saw in Zope. I eventually deleted /Foo/FooImages/coin_rond_bleu once more, and re-imported the image as /Foo/FooImages/coin_rond_bleu2. That actually worked. It seems that petit_coin_rond, even when officially "deleted" by Zope, still survives somehow, and haunts my database. Ghastly.
Hmmm sounds like a client caching problem to me. Caching creates many weird not-so-serious problems, whereas database problems usually create straightforward very-serious problems. Pavlos
On Sat, 29 Jan 2000, Pavlos Christoforou wrote:
On Sat, 29 Jan 2000, [iso-8859-1] Jérôme Loisel wrote:
Eventually, I got frustrated. Modifications I was making in the Gimp did not seem to affect what I saw in Zope. I eventually deleted /Foo/FooImages/coin_rond_bleu once more, and re-imported the image as /Foo/FooImages/coin_rond_bleu2. That actually worked. It seems that petit_coin_rond, even when officially "deleted" by Zope, still survives somehow, and haunts my database. Ghastly.
Hmmm sounds like a client caching problem to me. Caching creates many weird not-so-serious problems, whereas database problems usually create straightforward very-serious problems.
Assuming this is with Netscape on Linux, it is definitely a client caching issue. 'reload' does not cause netscape to reload images -- ever. You have to open the image directly (right-click on it, select "view image") and then hit 'reload' -- then that one image will get reloaded. Luck... --- Even if you can deceive people about a product through misleading statements, sooner or later the product will speak for itself. - Hajime Karatsu
This is unfortunately probably not a client caching problem. I was schooled a few weeks back about this very issue. There is (still) a bug in the Zope code that doesn't pass the proper cache control headers to the client and therefore the cached image is always displayed even when a later version should be downloaded. Hmm. Lets see if I can dig it up again. I sort of found it, it's dated somewhere around Dec. 27 and is in the thread "dumb object aliasing question" in this list.... I can't pull up the resolution to it though (it includes a patch from "Darrell"). Please use egroups to search for it (sorry!) It's sort of my fault that the bug is still there, I neglected to put it into the Collector when a patch was submitted. We don't fix bugs if they're not in there. I am going to do that now. Glyph Lefkowitz wrote:
On Sat, 29 Jan 2000, Pavlos Christoforou wrote:
On Sat, 29 Jan 2000, [iso-8859-1] Jérôme Loisel wrote:
Eventually, I got frustrated. Modifications I was making in the Gimp did not seem to affect what I saw in Zope. I eventually deleted /Foo/FooImages/coin_rond_bleu once more, and re-imported the image as /Foo/FooImages/coin_rond_bleu2. That actually worked. It seems that petit_coin_rond, even when officially "deleted" by Zope, still survives somehow, and haunts my database. Ghastly.
Hmmm sounds like a client caching problem to me. Caching creates many weird not-so-serious problems, whereas database problems usually create straightforward very-serious problems.
Assuming this is with Netscape on Linux, it is definitely a client caching issue. 'reload' does not cause netscape to reload images -- ever. You have to open the image directly (right-click on it, select "view image") and then hit 'reload' -- then that one image will get reloaded.
Luck...
--- Even if you can deceive people about a product through misleading statements, sooner or later the product will speak for itself. - Hajime Karatsu
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Digital Creations, Inc. Zope - http://www.zope.org
participants (4)
-
Chris McDonough -
Glyph Lefkowitz -
Jérôme Loisel -
Pavlos Christoforou