OK - I see one potential issue here: Magnolia doesn't seem to
support at Date data type.
I was hoping that an administrator could use the Magnolia admin
interface to manually edit customer subscription changes, but without
a date type, that would be difficult.
Any other thoughts on this?
Thanks,
--ee
On Nov 5, 2005, at 9:10 PM, (Eric Everman) wrote:
Hi-
I'm considering a project in which a for-pay subscription list is
maintained and is used to allow or deny access to portions of the
site as well as send emails. I was thinking that Magnolia's
content repository would work great for storing and managing the
subscriptions, except that all of that information would stored in
the public instance because that is where the user would actually
subscribe and submit their payment.
Is this a good approach? I've always thought of the public
instance as a 'throw away', in that I could always install it fresh
and activate my content from the admin instance. Would it be
possible to have the public instance list the admin instance as a
subscriber (Magnolia subscriber, that is) so that the public
instance could backup its customer subscription list to the admin
instance?
Has anyone else worked with storing custom data to the CMS from the
site (ie, store user information) or attempted to send email
versions of Magnolia pages?
Lots of questions...
Thanks Again,
Eric Everman
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
