First, please note that I had posted this yesterday already with "Private" checked, but then no view other than my own, and certainly no response. Maybe that "Private" thing doesn't work. So, here I am without it and in "public", I hope.
The thing is that I need an answer pretty soon (before the end of today, if possible) as I need to make a decision and then get going with my project.
So, please take a look at this... at least the points #1, #4 and #5 are important, obviously.
Thanks.
Hi,
I'm on a project to get a medium-sized organisation to use a web-based subscription system. Since a few more people will have to deal with managing the subscribers/subscriptions on a day-to-day basis and none of them should need to touch the Joomla backend, Emerald is winning the first points for its frontend access. :)
Few question are open after browsing the docs and demo, though. The briefest of your answers will be appreciated!
1.) EU tax laws: Is Emerald compliant?
The demo doesn't let me access the config. Duh.
Then I saw somewhere (forum post?) that v9.x does not have them implemented, yet. Really?! If not now, when... these laws are anything but new.
I think I also saw reference to it getting implemented in v10. Well, even if v10 were available next week, I don't think I'd want to hang this client with 15k+ subscribers (and myself) onto a brand-new version... not within the first 3-6 months after launch, anyway.
In other words, and IMHO, v9 must have, or instantly get, EU tax law compliance. If not, I'd be very disappointed about what calls itself "the best" and is factually one of the most expensive extensions in its category.
It might as well be a deal breaker.
2.) Purchase multiple subscriptions at once: I think I know the answer - it requires a cart, and that's not built in. Well, then I'm an avid HikaShop user... and that would do it, correct?
3.) "Extended" frontend management: There's quite a bit of frontend management already, but we'll need a lot more. A ton of fields for subscribers with multi-level ACL, more lists with filters, more statistics, map views, etc. No worries, I don't expect all that to come with Emerald!
Sure, view overrides could be made. But I'm planning to use Emerald as the "core", then add a CCK/app builder like Cobalt or Fabrik (I'm pretty 'compatible' with Fabrik - Cobalt would be totally new for me...). Question: Do you foresee any problems with reading/writing Emerald DB tables/fields with a tool like Cobalt or Fabrik? Without changing Emerald's existing DB structure, of course.
4.) The next version: It looks like v8 -> v9 wasn't just an "upgrade" but required more of a migration. So, once v10 comes, will v9 -> v10 be a walk in the park, or will it be a similarly "major" migration, perhaps a different DB structure, affecting the frontend in some drastic way as well, possibly requiring me to sort of "start all over" if UI/UX shall remain the same?
5.) In case of a not-so-great answer to #4, if we then decided to stick to v9 for as long as possible, how long would we be able to do so? In other words, how long will v9 be supported, e.g. in case Joomla "security" updates were required and brought some other code changes with them, like we've seen in the past?
Thank you very much for a response in the near future. Again, the briefest form is fine!
First, please note that I had posted this yesterday already with "Private" checked, but then no view other than my own, and certainly no response. Maybe that "Private" thing doesn't work. So, here I am without it and in "public", I hope.
The thing is that I need an answer pretty soon (before the end of today, if possible) as I need to make a decision and then get going with my project.
So, please take a look at this... at least the points #1, #4 and #5 are important, obviously.
Thanks.
Hi,
I'm on a project to get a medium-sized organisation to use a web-based subscription system. Since a few more people will have to deal with managing the subscribers/subscriptions on a day-to-day basis and none of them should need to touch the Joomla backend, Emerald is winning the first points for its frontend access. :)
Few question are open after browsing the docs and demo, though. The briefest of your answers will be appreciated!
1.) EU tax laws: Is Emerald compliant? The demo doesn't let me access the config. Duh. Then I saw somewhere (forum post?) that v9.x does not have them implemented, yet. Really?! If not now, when... these laws are anything but new. I think I also saw reference to it getting implemented in v10. Well, even if v10 were available next week, I don't think I'd want to hang this client with 15k+ subscribers (and myself) onto a brand-new version... not within the first 3-6 months after launch, anyway. In other words, and IMHO, v9 must have, or instantly get, EU tax law compliance. If not, I'd be very disappointed about what calls itself "the best" and is factually one of the most expensive extensions in its category. It might as well be a deal breaker.
2.) Purchase multiple subscriptions at once: I think I know the answer - it requires a cart, and that's not built in. Well, then I'm an avid HikaShop user... and that would do it, correct?
3.) "Extended" frontend management: There's quite a bit of frontend management already, but we'll need a lot more. A ton of fields for subscribers with multi-level ACL, more lists with filters, more statistics, map views, etc. No worries, I don't expect all that to come with Emerald! Sure, view overrides could be made. But I'm planning to use Emerald as the "core", then add a CCK/app builder like Cobalt or Fabrik (I'm pretty 'compatible' with Fabrik - Cobalt would be totally new for me...). Question: Do you foresee any problems with reading/writing Emerald DB tables/fields with a tool like Cobalt or Fabrik? Without changing Emerald's existing DB structure, of course.
4.) The next version: It looks like v8 -> v9 wasn't just an "upgrade" but required more of a migration. So, once v10 comes, will v9 -> v10 be a walk in the park, or will it be a similarly "major" migration, perhaps a different DB structure, affecting the frontend in some drastic way as well, possibly requiring me to sort of "start all over" if UI/UX shall remain the same?
5.) In case of a not-so-great answer to #4, if we then decided to stick to v9 for as long as possible, how long would we be able to do so? In other words, how long will v9 be supported, e.g. in case Joomla "security" updates were required and brought some other code changes with them, like we've seen in the past?
Thank you very much for a response in the near future. Again, the briefest form is fine!