Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion Close and nav buttons aren't displayed in IE due to path problems
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
;Op  
View profile  
 More options Mar 11 2010, 6:14 am
From: ";Op" <olivier.potonn...@gmail.com>
Date: Thu, 11 Mar 2010 03:14:13 -0800 (PST)
Local: Thurs, Mar 11 2010 6:14 am
Subject: Re: Close and nav buttons aren't displayed in IE due to path problems
This is a *BLOCKING ISSUE* for me: I want to use fancybox in different
pages, at different directory levels. Of course I want to have a
single copy of fancybox installed, so I would like to refer its images
either relative to the fancybox installation (ie relative to the CSS
or JS files), or with an absolute path. But I work on different web
sites, and the root directory for static resources is different on
each of these sites. Furthermore, this root is different on
development and production servers. I'm doing the dev, but I don't
control production servers: I can't even know "a priori" the absolute
path on them...

As I understand it, there are 4 alternatives to solve the
AlphaImageLoader.src path issue:

1. put fancybox images within the directory (or directory tree) of
each HTML page that uses it. But there are many (actually ALL pages!),
and this is very intrusive: I'll have fancybox files copied (or
linked) many times. This is both cumbersome to install and update.

2. edit css to replace the relative path by absolute image path. But
this path will be different for all my different servers, and also for
dev and prod modes... And I don't know (and don't want to care about)
the absolute path on production servers.

3. URL rewriting in .htaccess. I did not experience this method
mentionned by Roman, but I think it has the same defects as solution
2, plus it is "apache" specific.

4. Javascript in CSS: I've seen http://drupal.org/node/185866 but
still did not experience it. It seems possible to provide
programatically (in javascript) the URL. This sounds interesting, and
could probably be included in fancybox itself: the path to look these
images into could be relative ("fancybox/" as it is today) by default,
but could be overridden with a configuration dependent path prefix
(usually an absolute one), which could itself by computed by another
mean (not a fancybox matter).

Does anyone have another solution to propose? Has anyone experimented
solution 4? Would fancybox team consider doing it?

Thanks for this nice library anyway


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.