HoosierMike
03-27-2006, 12:42 PM
First, let me say that I think the script is great -- it's allowed me to customize the calendar to fit our needs. However, I've run into a problem with respect to the license key, as described below. Unfortunately, I'm caught in an endless loop between the "submit a support ticket" approach to support, and the "request a new license key" approach.
In order to help users of our nonprofit's website, we decided to change our somewhat cryptic domain name (under which I registered the script) to a URL that is much easier to remember. Unfortunately, because the license is keyed to the domain name, the script no longer works with our new domain name. I would like to update the license to reflect the new domain name. Also, because people might still be using the old domain name, I've parked the old domain on the new and would like the script to continue working with the old name (I've also registered and parked a domain name with a slight spelling variation of the new domain name, in case people mis-type the new name, and would like that parked domain to also work with the calendar).
Because the "new license key request" link says that a support ticket must first be opened for parked domains, I opened a support ticket on Saturday morning. Having not heard back by Sunday, I went ahead and completed the "new license key request" form. This morning, I received email responses to both requests and somehow fell between the cracks -- the response to the support ticket said I had to first open a new license key request, and the response to the new license key request said I had to first open a support ticket.
Sorry to clog the board with this, but I'm wondering if anyone has any advice on how to get this resolved. We're in the process of publicizing the new domain name, and I'm a bit desparate. Thanks!
In order to help users of our nonprofit's website, we decided to change our somewhat cryptic domain name (under which I registered the script) to a URL that is much easier to remember. Unfortunately, because the license is keyed to the domain name, the script no longer works with our new domain name. I would like to update the license to reflect the new domain name. Also, because people might still be using the old domain name, I've parked the old domain on the new and would like the script to continue working with the old name (I've also registered and parked a domain name with a slight spelling variation of the new domain name, in case people mis-type the new name, and would like that parked domain to also work with the calendar).
Because the "new license key request" link says that a support ticket must first be opened for parked domains, I opened a support ticket on Saturday morning. Having not heard back by Sunday, I went ahead and completed the "new license key request" form. This morning, I received email responses to both requests and somehow fell between the cracks -- the response to the support ticket said I had to first open a new license key request, and the response to the new license key request said I had to first open a support ticket.
Sorry to clog the board with this, but I'm wondering if anyone has any advice on how to get this resolved. We're in the process of publicizing the new domain name, and I'm a bit desparate. Thanks!