>> This behavior is odd. The relative path should be computed in relation >> to index.php and not to the page. Interestingly this only happens with >> clean URLs, maybe as sub-pages translate to slashes and / means path. > > You must be exactly right. The cleanUrls no doubt confuse things. This > is why I generally try to avoid providing support for cleanUrls. :)
Well, I know. I was hoping anyone else would have a clue. After diving into the realms of BoltWire for some hours (and going nuts), I can't help but say, it makes no sense to me that on the very same page $imgPath is relative and $farmPath is absolute: img: ../boltwire/farm/img farm: http://localhost:8888/boltwire/farm It's just lucky for you that it works without clean URLs. But it's not so much about clean URLs, it's about a relative path. :) Somewhere along the trail $farmPath becomes an absolute path which is good. But as $imgPath is a global of BOLTMuploads it seems to be fetched as a relative path as defined in engine.php. Can't you make both $farmPath and $imgPath absolute everywhere? I think that would solve this problem. And it shouldn't break sites without clean URLs. Maybe we can then find one index.php + htaccess combination that works universally. -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
