X3Photo Gallery Forums

Good question. The term "gallery" certainly could have a few different meanings. It may be used for the entire gallery installation with folders and subfolders, while some may use it strictly for a single "folder" in their portfolio. We generally refer to a gallery as a single link representing an array of files and folders. If there are separate links representing separate content, I would refer to this as separate galleries, and therefore "multiple galleries".

Multiple imagevue galleries, can either run from the same core imagevue script files(on the same server), or on separate imagevue uploads(on same server and/or different domain altogether).

Why would one have multiple galleries?
There are a few aspects to this. A single client may have the need for multiple galleries. For example, a wedding photographer can provide separate gallery links to their clients, representing images from the last gig. If a photographer has fixed customers, he/she may want to provide separate galleries for every client, each with its own folder structure of events. Generally speaking, a user may want to separate their content - Perhaps a private gallery and a public gallery? And then in more conventional terms, some imagevue users may be web designers setting up multiple galleries for multiple clients(mostly on separate servers).

Gallery licence
Generally, a single licence may be used as desired on a single domain. There can be multiple gallery instances in any way. When using multiple galleries across multiple domains, we consider these galleries separate projects or separate clients, and therefore require separate licences for separate domains. There are currently two options for multiple licences as a benefit to customers: Consecutive and Unlimited

mjau-mjau wrote:Good question. The term "gallery" certainly could have a few different meanings. It may be used for the entire gallery installation with folders and subfolders, while some may use it strictly for a single "folder" in their portfolio. We generally refer to a gallery as a single link representing an array of files and folders. If there are separate links representing separate content, I would refer to this as separate galleries, and therefore "multiple galleries".

Multiple imagevue galleries, can either run from the same core imagevue script files(on the same server), or on separate imagevue uploads(on same server and/or different domain altogether).

Why would one have multiple galleries?
There are a few aspects to this. A single client may have the need for multiple galleries. For example, a wedding photographer can provide separate gallery links to their clients, representing images from the last gig. If a photographer has fixed customers, he/she may want to provide separate galleries for every client, each with its own folder structure of events. Generally speaking, a user may want to separate their content - Perhaps a private gallery and a public gallery? And then in more conventional terms, some imagevue users may be web designers setting up multiple galleries for multiple clients(mostly on separate servers).

Gallery licence
Generally, a single licence may be used as desired on a single domain. There can be multiple gallery instances in any way. When using multiple galleries across multiple domains, we consider these galleries separate projects or separate clients, and therefore require separate licences for separate domains. There are currently two options for multiple licences as a benefit to customers: Consecutive and Unlimited

Hmm, does this means I can use the script on subdomains for the domain it is licensed for, but in the same time use the script for the base domain? I have a private license for photogallerix.com can I then use it for subdomains to that domain for example something.photogallerix.com. Is this allowed when using a private license?

Felix J wrote:Hmm, does this means I can use the script on subdomains for the domain it is licensed for, but in the same time use the script for the base domain? I have a private license for photogallerix.com can I then use it for subdomains to that domain for example something.photogallerix.com. Is this allowed when using a private license?

Yes

Sorry to bring up an old thread but it might be better to do this than opening a new thread with addition to the original question.

So, if it IS ALLOWED to install multiple instances of imagevuex on the same license domain (eg. main domain + another installation on sudomain)... are we breaching the license if I own an add-on domain name on the same server and use an Iframe to cloak the original URL?

Obviously, the NAG screen will pop-out if I access the other domain name directly with the imagevuex installed but if I access the same installation using the maindomain.com/subdomain of course the NAG screen/authorization will be gone.

It will be installed on the subdomain, I just want it look like hosted as different gallery altogether on my other domain name. Please clarify... thanks!

localhost wrote:So, if it IS ALLOWED to install multiple instances of imagevuex on the same license domain (eg. main domain + another installation on sudomain)... are we breaching the license if I own an add-on domain name on the same server and use an Iframe to cloak the original URL?

No. We only require additional licenses if you are using the gallery for additional clients or separate website projects. If you have the same gallery on multiple domains, it does not matter. If you use an iframe to cloak your original domain, this is up to you and it does not affect Imagevue in any way ...

localhost wrote:Obviously, the NAG screen will pop-out if I access the other domain name directly with the imagevuex installed but if I access the same installation using the maindomain.com/subdomain of course the NAG screen/authorization will be gone.

You will just have to authorize all the domains from where you are running Imagevue. It's that simple.
[LINK REMOVED]

localhost wrote:It will be installed on the subdomain, I just want it look like hosted as different gallery altogether on my other domain name. Please clarify... thanks!

I can't see how this would be a problem.