Joomla Multilanguage integration

  • Posts: 253
  • Thank you received: 17
  • Hikaserial Subscription Hikashop Business
7 months 3 weeks ago #277240

-- HikaShop version -- : 3.1.1
-- Joomla version -- : 3.7.5
-- PHP version -- : 7.1.8
-- Browser(s) name and version -- : Chrome 60

Hi guys,
as all we know an eCommerce is an international commerce. Now that also Multilingual Associations feature has been released in Joomla, I think this is one of the biggest lack here in Hika , a real Joomla Multilanguage integration.

Please, Do we have any hope to see it soon ?

The following user(s) said Thank You: altrasoluzione

Please Log in or Create an account to join the conversation.

  • Posts: 61826
  • Thank you received: 8793
  • MODERATOR
7 months 3 weeks ago #277242

Hi,

I'm sure you already know that there is an integration with Falang which is quite real if you need a multilingual shop with HikaShop.

Now if your question is whether we'll build soon a solution directly integrated in HikaShop to do that, without the need of Falang, that's another question. Yes, that's something we want to do. Will it be soon ? I would say no for two main reasons:
- there is already Falang which work quite good for that
- we have other more pressing features we want to add like web services

The following user(s) said Thank You: joomleb

Please Log in or Create an account to join the conversation.

  • Posts: 253
  • Thank you received: 17
  • Hikaserial Subscription Hikashop Business
7 months 3 weeks ago #277307

Hi Nicolas,

just a note that sure you yet know, the Multilingual impovements are on Joomla 4 Roadmap , to confirm the importance of a real Multilingual vision.

Thanks for your attention...

The following user(s) said Thank You: altrasoluzione

Please Log in or Create an account to join the conversation.

  • Posts: 22247
  • Thank you received: 3464
  • MODERATOR
7 months 3 weeks ago #277309

Hello,

I wrote many times in that forum my opinion about the Joomla multilingual system. So I won't make long speech.
The way that Joomla is performing the multilingual is good for the "article" perspective but not good for an e-commerce solution.
You can do it in HikaShop if you want but it means that you will duplicate every single product for each language ; exactly like you duplicate your categories/articles in Joomla.

Regards,


Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.

Also helping the HikaShop support team when having some time or couldn't sleep.
By the way, do not send me private message, use the "contact us" form instead.

Please Log in or Create an account to join the conversation.

  • Posts: 253
  • Thank you received: 17
  • Hikaserial Subscription Hikashop Business
1 month 3 weeks ago #288755

Hi Jerome,

Jerome wrote: ...I wrote many times in that forum my opinion about the Joomla multilingual system...


Please, Which forum?
I want read your opinion / explications beforeto going on.

Thanks for support

Please Log in or Create an account to join the conversation.

  • Posts: 61826
  • Thank you received: 8793
  • MODERATOR
1 month 3 weeks ago #288777

Hi,

I'm not sure about Jerome.
Here is a thread where I talked about it a while back:
www.hikashop.com/forum/3-bug-report/3765...edition-in-j2-5.html

Please Log in or Create an account to join the conversation.

  • Posts: 253
  • Thank you received: 17
  • Hikaserial Subscription Hikashop Business
1 month 3 weeks ago #288824

Hi Nicolas,
thanks for link, I red it.

As far as I understand, the only "bad" thing on managing multilanguage with Joomla should be the need to "moltiplicate products", one product id per language, and this would be bad for statistics etc. because HikaShop do not have an integrated way to make associations (like joomla) and say that all the products languages are the same product. Hope also Jerome can confirm this.

Now, I think that this issue, and also others like joomla article integration / Seblod cck integration, can be solved with a similar "j2store Seblod" plugin approach , where:
- Build a plugin for joomla article (each joomla article will ask if is a product). Buld a plugin for Seblod (when integrated es explained each Seblod article will ask if is a product)
- Add a pre-question "Do you want to pick a product yet exist in your HikaShop?" (In this way all the old HikaShop products will can be moved into a Joomla article / Seblod article)
- The "Joomla article product" will be able to use the new Joomla Custom Fields. The "Seblod article product" will be able to use all the CCK features
- The user will be able to choose to use the Multilanguage with falang when using HikaShop directly, or switch to Joomla Multilanguage when using the Joomla Article / Seblod Article - No needed anymoreto develop an internal HikaShop Multilanguage
- And in my opinion would be better to leave the Custom Fields development to Joomla / Seblod etc... to concentrate HikaShop team efforts on features more importants like payments/invoices/statistics etc. and new app like a booking system...

If you are agree, I'd have some questions:

1 - When you can choose to treat article as product, you have to choose also the "product type".
J2store divide into: Simple / Variable / Configurable / Downlodable
I think HikaShop have only one product type, because all the product configurations are under the same product setting page (Included the HikaSerial, HikaSubscritpion, HikaMarket variables). Am I right ?

2 - I need help, your opinion, on Which HikaShop Product page sections leave and which have to be removed (because have to be setted into the article, like the description... I add a j2store Configurable Product Type example

File Attachment:

File Name: Edit-Article.pdf
File Size:97 KB


3 - Am I forgetting anything? All suggestions are too glad !

And always thanks for support...

Attachments:
Last Edit: 1 month 3 weeks ago by joomleb.

Please Log in or Create an account to join the conversation.

  • Posts: 61826
  • Thank you received: 8793
  • MODERATOR
1 month 3 weeks ago #288828

Hi,

1. Well, HikaShop has a product_type field for products. However, it's mostly used for behind the scene things.
For example, variants are stored as products but their product_type is "variant" instead of "main". I don't think that you would have to allow the selection of the variant type in articles though.
Another one is the "template" type, that HikaMarket uses to generate products when vendors create new products on the frontend. But again, these are not useful for articles in such integration.
So I indeed don't think that the selection of a type should be necessary for HikaShop if you were doing such an integration.

2. I think you would want most of the options. The options you wouldn't want I think are:
- product name since you would use the article title
- categories (but it would be useful for discounts, limits, custom hikashop fields, etc) so it might be interesting to keep them
- tags since you would use the article tags
- published since you would use the article published status instead
- the description, obviously
- the page title, meta description, keywords and alias fields would be irrelevant as the article handle these
- the canonical URL wouldn't be necessary as the URL would be the article's URL
- the available from/to fields could potentially be removed since there are already a publish/unpublish date for the articles
- the access level could be ommited to use instead the access level of the article
- for the page layout, I'm not sure. You might still want layouts but only for the bit added to the article by the integration plugin
- the custom fields could be ommited.

3. The idea is quite good indeed. That would allow for a great multilingual native integration without the need to rewrite a lot of the MySQL queries of HikaShop to handle it and would also avoid the pitfalls of duplicating the products, one per language.
That could even be made as a third party plugin since it wouldn't touch to the core of HikaShop, only add products to it.
One thing you could do first would be to have a product selector instead of a whole product settings interface in the articles. That way, you would have the same result but without all the work to integrate all the options of the product page to the articles. The only downside, would be to precreate the products, but you could have a add button with a popup to do that next to the product selector on the joomla article.

Please Log in or Create an account to join the conversation.

  • Posts: 253
  • Thank you received: 17
  • Hikaserial Subscription Hikashop Business
1 month 2 weeks ago #289070

Hi Nicolas,
really many thanks. I'm already working on it preparing a working plan to show you (as always, you know: I'm a collaborative spirit).
I'm including in the plan the Joomla Article (not only Seblod) and the "import" for all the HikaShops that want move:

...One thing you could do first would be to have a product selector instead of a whole product settings interface in the articles. That way, you would have the same result but without all the work to integrate all the options of the product page to the articles. The only downside, would be to precreate the products, but you could have a add button with a popup to do that next to the product selector on the joomla article.

- "a product selector": "Yes", to permit to all the the old HikaShop an integration, with a "prefilled importing view" and making available only products that are not yet associated with an Article (to avoid unwanted duplicated, two articles for the same product).
- "precreate the products": "No", because thinking on the user Frontend product creation experience, all should be in a most simple as possible "one page" layout.

Hoping HikaShop can evolve soon to a new big step, this topic "remain open" to receive all ideas /suggestions / opinions as possible...

The following user(s) said Thank You: nicolas

Please Log in or Create an account to join the conversation.

Time to create page: 0.110 seconds
Powered by Kunena Forum