Hi Eric
You can maintain a separate workspace for subscribed users, if you
stick with jcr you will be able to use same magnolia api as you use to
manage page content
and all services like full text search, versioning will be available.
To synchronize subscribed users on admin instance you can add admin as
subscriber and use magnolia API to activate to this particular
subscriber.
hope this helps
- Sameer
On Nov 7, 2005, at 11:45 PM, (Eric Everman) wrote:
Any thoughts on this? Is my question not clear or am I just bugging
the heck out of everyone?
--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
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
