Thanks for responses.
I think we 're going to choose Magnolia. We're going to test a little
bit more to see if it's a real good solution.
on the other hand, my boss is not very agree to make our extensions open
source. But we're going to take part in Magnolia project in writing
documentations, extra paragraphs, ... The weak point of Magnolia.
Thanks.
Julien.
David Smith a écrit :
IMHO you'd be better off storing shopping card data in a separate
database or tie in to a business back-end process. Keep the product
info (pictures, description, etc., ...) in magnolia where you can have
people edit/publish stuff but store the shopping cart info elsewhere.
--David
Will Scheidegger wrote:
Salut Julien
On 04.04.2007, at 09:56, Julien C. wrote:
- is that possible to develop proprietary modules (license) like
shopping cart, blog, ...
I don't know if I understand this question right: You would like to
know if you can develop extensions to magnolia and the sell them?
Hm... why shouldn't you be able to do this? Of course it would be
better for the community if you would make your extensions open
source too. Who knows - maybe you would even get help developing the
extensions then. I might be interested in co-developing the shopping
cart for instance...
I don't see clearly where the data are save. in public or author
instance ( for shopping cart the products are enter in author , the
shopping cart in public, the treatment of the order in ? )
This is definitely an issue that needs to be well considered in your
design. As a quick shot I would suggest that you _manage_ your
product data in author an _publish_ them afterwards to the public
environment, just as you do with regular page content. The shopping
cart data will most likely be kept on the public side although it
should not be rocket science to "publish" the completed shopping
carts back to the author instance if you feel this is needed (e.g.
for simpler backup purposes).
- can we use 1 magnolia instance for multiple site. (We have a lot
of small site with less than 10 or 20 pages) Can we control the
website tree under Admin central according to user login.
Yes you can. Have a look at
http://www.magnolia.info/wiki/Wiki.jsp?page=SetupEditorRoleForASite
Regards,
Will
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
