Guys,
I have read your discussion here and have some questions to everyone:
1. Phil, can you describe what is - "sitedomain order origin" and
"language order origin"?
2, It's not very healthy to limit the option to sell / show the same
products or links (so forth) on different Site Domains. What if I need
to sell something on 2+ sites domains which have different Domain,
Theme, Language and so on. I believe it was the original approach for
SiteDomains and they way they are working now.
What are your thoughts.
DA
On Oct 12, 2:53 am, Alexander Obuhovich <
aik.b...@gmail.com> wrote:
> *Alex, your story about Russian way of doing is not surprising me at all,
> and I can add that if we use the "section" tab to place a flower product in
> a subdir of "cars" category, this would do the trick, isn't it?
> *
> Nope, since url to a product will be build using it's primary category,
> which will match only one site domain.
>
> We'll be working to make site domains and In-Portal better and more user
> friendly with each release. Documentation (of In-Portal) would be really
> helpful, but due the limited resources we can improve In-Portal and write
> documentation in same time.
>
> On Fri, Oct 8, 2010 at 11:20 AM, Phil --
wbtc.fr -- <
p...@wbtc.fr> wrote:
>
>
>
>
>
> > thanks guys for your positive comments.
>
> > As you have probably noticed I'm pushing things forward for this function
> > from the beginning, because this is one of the futures for e-commerce.
>
> > Alex, your story about Russian way of doing is not surprising me at all,
> > and I can add that if we use the "section" tab to place a flower product in
> > a subdir of "cars" category, this would do the trick, isn't it?
>
> > There is another main reason for all this: if you run more than on website,
> > selling the same products, then you'll mechanically take more place in
> > google results for your products :-)
>
> > Then for all these reasons, I think In-Portal can now fit bigger projects,
> > with a real difference on Magento, which is a good product, but needs really
> > more resource for the same result, not to talk about complexity for
> > installation/implementation/maintenance.
>
> > 2010/10/8 Alexander Obuhovich <
aik.b...@gmail.com>
>
> > Outstanding job Phil.
>
> >> I don't know how it's done in US, but in Russia it's a popular business
> >> model to have multiple shops end up in single database. Here is an example:
>
> >> - I'm a big reseller and got 5000 products including: cars, flowers,
> >> clothes
> >> - that's pretty stupid to sell them all in one e-shop, since they kind
> >> of not related to each other
> >> - I create 3 sites:
www.cars.com,
www.flowers.com,
www.clothes.com
> >> - In "Structure & Data" section I create top categories called the
> >> same as site names:www.cars.comand so on
> >> - I place appropriate products in appropriate categories (each of them
> >> can have their own and independent category structure inside)
> >> - I create site domains and set, that actual root of each site domain
> >> will be one of categories I've create before
>
> >> There are several limitations here:
>
> >> - you can't have another site, that will allow to sell all products
> >> from other sites
> >> - you can't sell same product on different sites
>
> >> Real problem in implementing this is module root categories, that only
> >> creates useless abstraction above all this and idea to have them specified
> >> for each domain is even more frightful.
>
> >> In
> >>
http://groups.google.com/group/in-portal-dev/browse_thread/thread/2c3...I'm proposing to get rid of them, so they won't be preventing
> >> site domains from expanding further.
>
> >> On Fri, Oct 8, 2010 at 2:39 AM, Dmitry Andrejev <
dandre...@gmail.com>wrote:
>
> >>> Hi Phil,
>
> >>> Thanks for all this work summarizing things ;)
>
> >>> This sounds very much like ability to run multiple sites / stores which
> >>> are not even related to each other :)
>
> >>> While I like the idea of In-Portal doing this - to be honest Site
> >>> Domains is not really was meant for this.
>
> >>> DA.
>
> >>> On Thu, Oct 7, 2010 at 5:45 PM, Phil --
wbtc.fr -- <
p...@wbtc.fr> wrote:
>
> >>>> (based on this<
http://groups.google.com/group/in-portal-dev/browse_thread/thread/fce...>,
> >>>> this,<
http://groups.google.com/group/in-portal-dev/browse_thread/thread/448...>
> >>>> this<
http://groups.google.com/group/in-portal-dev/browse_thread/thread/e84...>,
> >>>> this<
http://groups.google.com/group/in-portal-dev/browse_thread/thread/cbb...>,
> >>>> and this<
http://groups.google.com/group/in-portal-dev/browse_thread/thread/395...>threads)
>
> >>>> Hi guys,
>
> >>>> Here is a resume of actual Sitedomain functions, and the suggestions
> >>>> already made + new ones.
>
> >>>> *Actual Specifications
> >>>> *- configure multiple Domains that this website is running on
> >>>> - SSL URL
> >>>> - sender's email for messages sent by system
> >>>> - each domain can have a specific value for:
> >>>> - geo-location match - by IP or country (location)
> >>>> - primary theme (drop-down) + available themes
> >>>> - primary language (drop-down) + available languages
> >>>> - primary currency (drop-down) + available currencies
> >>>> - payement type(drop-down) + available currencies
> >>>> - available billing country (only 1)
> >>>> - available shipping country (only 1)
>
> >>>> *Future things already on Mantis
> >>>> *- specify which agents are allowed to be run on which site domains
> >>>> #883
> >>>> - language specific ModRewrite URLs #638
> >>>> - Domain-specific configuration variables #847
>
> >>>> *Suggestions (new and old ones)
> >>>> *- ability to select a default pricing group
> >>>> - sitedomain drop-down on top of config pages
> >>>> - root folder for each module, per site (or maybe available folders, via
> >>>> checkboxes in a three view?)
> >>>> - permission tag for tpl to select sitedomain access
>
> >>>> *Things I'm not sure about*