Quote:
Originally Posted by Chuck S Why would we release an import script to go to another product we also manufacture? |
Because surely if customers aren't happy with the way vBGallery is going or they just want to run their gallery with features that vBGallery doesn't offer (like nice urls), their only other option is to go elsewhere and you lose customers?
Quote:
Originally Posted by Chuck S You are entitled to your opinions on vbgallery. However all facts speak to the contrary. We have released many versions updates and also added many new features and it has not been even 2 years yet. We added vbulletin 3.5 and 3.6 support with 4 revisions for 3.6 alone in like a year. I do not know how much you remember about the script back then but what we recieved was riddled with bugs that had not been fixed so we spent like the first 6 months just ironing out old bugs. |
Fair enough, we'll just have to agree to disagree. I'm looking at it from a customer's perspective as someone who's been using both products for several years. Ironing out the bugs is great, upgrades for 3.5 and 3.6 support is essential, but I can't help thinking that feature development has slowed massively, and it's unlikely that it'll catch up with Photopost or competitor products anytime soon.
Quote:
Originally Posted by Chuck S The present script though for you to alter the few queries to update those table names for vbgallery. |
Sounds easy enough (although I wouldn't know how to do it), but if it's that easy, why not simply offer it as a supported script?
Stuart