You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In real life on an e-commerce or other site, it often happens that you have to create a FAQ / Knowledgebase based on the affiliation of the translation you use ... for example, they will not be the same payment instructions for an e-commerce for users from Germany or Ireland .... so the suggestion would be to hide the folders / categories / articles based on the translation you use: https://help.abc.com/public/en/folder/1/articles
where if you use /es/ instead of /en/ for example or another translation you can also change the visibility of the stored articles ... in my opinion it is not a complicated thing ...
perhaps you should create/insert a flag box in the code to check in the info to the folders / categories / articles.
This would be an extraordinary thing for a multilingual helpdesk that is almost unavailable on the market!
Thank you so much for your attention!
The text was updated successfully, but these errors were encountered:
In real life on an e-commerce or other site, it often happens that you have to create a FAQ / Knowledgebase based on the affiliation of the translation you use ... for example, they will not be the same payment instructions for an e-commerce for users from Germany or Ireland .... so the suggestion would be to hide the folders / categories / articles based on the translation you use:
https://help.abc.com/public/en/folder/1/articles
where if you use /es/ instead of /en/ for example or another translation you can also change the visibility of the stored articles ... in my opinion it is not a complicated thing ...
perhaps you should create/insert a flag box in the code to check in the info to the folders / categories / articles.
This would be an extraordinary thing for a multilingual helpdesk that is almost unavailable on the market!
Thank you so much for your attention!
The text was updated successfully, but these errors were encountered: