Jump to content

Search the Community

Showing results for tags 'multistore'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Help and Support
    • PrestaShop Download
    • PrestaShop Addons
  • News and Announcements
    • PrestaShop news and releases
    • PrestaShop Beta
    • PrestaShop Blogs
    • PrestaShop Meetups
  • International community (English)
    • General topics
    • PrestaShop Merchants
    • PrestaShop Developers
    • Taxes, Translations & Laws
    • Community Modules and Themes
  • Forum francophone
    • Discussion générale
    • Aide et support communautaire
    • PrestaShop pour les marchands
    • PrestaShop pour les développeurs
    • Adaptation aux lois Québécoises
    • Modules et thèmes gratuits
    • Modules et thèmes payants
  • Foro en Español
    • Discusión general
    • Soporte de la comunidad y ayuda
    • Comerciantes PrestaShop
    • Desarrolladores PrestaShop
    • Módulos y plantillas gratuitas
  • Forum italiano
    • Forum generale
    • Aiuto e supporto della Community
    • Commercianti PrestaShop
    • Sviluppatori PrestaShop
    • Aspetti legali sull'eCommerce
    • Moduli e template gratuiti
  • Deutsches Forum
    • Generelle Fragen
    • Support und Hilfe aus der Community
    • e-Commerce/Versand-Handel mit Prestashop
    • Prestashop-Entwickler
    • Anpassung an deutsches Recht
    • Kostenlose Module und Templates
    • Generelle Fragen Copy
  • Nederlandstalig forum
    • Algemeen
    • Hulp en ondersteuning, van en voor de community
    • PrestaShop-winkeliers
    • PrestaShop-ontwikkelaars
    • Het aanpassen van PrestaShop
    • Gratis modules en templates
  • Fórum em Português
    • Fórum Geral
    • Ajuda e Suporte da Comunidade
    • Lojistas que utilizam o PrestaShop
    • Desenvolvedores PrestaShop
    • Legislação específica
    • Módulos e temas gratuitos
  • Polskie forum
    • Forum ogólne
    • Wsparcie i pomoc użytkowników
    • Oferty twórców PrestaShop
    • Deweloperzy PrestaShop
    • Darmowe Moduły i Szablony
  • Dansk forum
    • Generelt forum
    • Hjælp og support fra fællesskabet
    • PrestaShop for købmænd
    • PrestaShop for udviklere
    • Love og regler
    • Gratis moduler og temaer
  • České fórum
    • Instalasi, Konfigurasi dan upgrade
    • Obecná diskuze
    • Bezplatné moduly a šablony
    • PrestaShop vývojáři
    • PrestaShop obchodníci
  • Bahasa Indonesia
    • Diskusi Umum
    • Podpora a pomoc komunity
    • Laporan Bug
    • Jasa, Promosi & Lowongan Kerja
  • Svenskt forum
    • Allmän diskussion
    • Installation, konfigurering och uppdatering
  • Forumul românesc
    • Discuţii generale
    • Instalare, configurare şi upgrade
  • Pусский язык
    • Обсуждение скрипта
    • Установка, Настройка, Обновление
    • Прием багов
  • Slovenské fórum
    • Všeobecná diskusia
    • Podpora a pomoc komunity
    • PrestaShop obchodníci
    • PrestaShop vývojári
    • Bezplatné moduly a šablóny
  • Türkçe Topluluğu
    • Genel Konular
    • Topluluk desteği ve yardım
    • PrestaShop Tüccarları
    • Prestashop Geliştiricileri
    • Ücretsiz Modül ve Temalar
  • Diễn đàn tiếng Việt
    • Thảo luận chung
    • Hỗ trợ từ cộng đồng
    • Dành cho chủ doanh nghiệp / cửa hàng
    • Dành cho lập trình viên
  • PrestaShop Communities
    • اللغه العربيه [Arabic]
    • Ελληνικά [Greek]
    • עִבְרִית [Hebrew]
    • 中文
    • Magyar [Hungarian]
    • 日本語 [Japanese]
    • Lietuviškai [Lithuanian]
    • انجمن فارسی [Persian]
    • ไทย [Thai]
    • Malaysia [Malaysian]
    • Eesti [Estonian]
    • Slovenščina [Slovenian]
    • Српски [Serbian]
  • IP. Board Forum
    • IP. Board Forum Questions and Issues
  • Archive
    • Zapłać Moduły i Szablony [ARCHIVE]
    • Moduly, upravy a dizajn [ARCHIVE]
    • Phát triển và các mô-đun [ARCHIVE]
    • Yazılım, Modül ve Tema [ARCHIVE]
    • Модули, Шаблоны [ARCHIVE]
    • Module şi teme [ARCHIVE]
    • Pengembangan dan Modul [ARCHIVE]
    • Moduler och teman [ARCHIVE]
    • Ecommerce x PrestaShop [ARCHIVE BOARD]
    • Vývoj a moduly [ARCHIVE]
    • Kostenpflichtige Module, Templates [ARCHIVE]
    • Módulos y temas pagos [ARCHIVE]
    • Módulos e temas pagos [ARCHIVE]
    • Servizi commerciali [ARCHIVE]
    • Forum - Feedback Contributor
    • PrestaShop Cloud

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


  1. Personal Salesmen This module lets you assign a customer or customer group to an employee. The employee will only see his/her assigned customers, and no other customers. So if you have customers that often return to your shop, but should only be managed by one of your employee's and it's private, this is your module! If you are logged in as the SuperAdmin you can see all the customers and employee's. Features: Easily manage customer orders Less hectic order overview for your employee's Private sales restricted for employees Less work for SuperAdmin to assign chores Linked employee receives email upon new order Link employees to customer groups Fully functional for Multistores Installation: After the installation and enabling the module, any employee that is not a Superadmin will only see his/her assigned customers and orders. If you don't make any links, the other employees wont be able to see any customers or orders. So if you have not configured the module any other employees will not see anything at al! We recommend making a special employee profile for your Personal Salesmen (Advanced parameters > Team > Profiles). In order to have the module work, every employee should have the permission: View & Configure to the Personal Salesmen module. If the permission is not set the profile of your employees the filters won’t work. If you are using the Prestashop Multistore function, please make sure upon installing the module that you have all the stores selected. (in de right upper corner) If you have not, the module will not function properly. How to use: As show in the image below, you can add and remove links. Once you have created a link this employee will be able to everything to the selected customer as set in the employee profile permissions. By clicking on the red trashcan you can delete a link between any employee and his/her group or customer. (Before PS 1.7.7 you can only delete all the links of employees) You can also link employees to a customer group. This makes it really easy to assign employees to multiple users at once. As shown in the image below you can link the employee to a customer group. This means in the future if you set a customer to a group, this will automatically be visible to the linked employee. This is a really great function for B2B to, for company's that have a responsible employee per department. Other languages: If you are not using English as main language for your shop, you should manually copy the folder mails/en and replace the en for the language you are using in the backoffice. For example there is a folder mails/nl for the nl language. Prestashop 1.7 personalsalesmen.zip Comments, tips or updates? Check GIT.
  2. Hi, Do you have nay idea how to create different registration form for each multistore shop? What happend... ? I have a Prestashop with multistore feature active. Both shops are different and I need custom registration for each of them. Each registration page will contain different form fields, so simple HTML/CSS would not work here, as the POST data need to be stored somewhere... I tried to override /classes/form/CustomerFormatter.php but it change registration content in all shops. I also try to create custom module which override above file but only for specific multistore ID and it do not help. Same results as above.
  3. Hi, I have a Prestashop with multistore feature active. Both shops are different and I need custom registration for each of them. Each registration page will contain different form fields, so simple HTML/CSS would not work here, as the POST data need to be stored somewhere via controller... I tried to override /classes/form/CustomerFormatter.php but it change registration content in all shops. I also try to create custom module which override above file but only for specific multistore ID and it do not help. Same results as above. Do you have nay idea how to create different registration form for each multistore shop?
  4. Hello, I've a question about the category management in a multistore enviroment. I have several categories (about 500) with a very big and complex treeview. I have several store, every one can select wich categories should use and eventually modify his treeview. But every times a store edits a category (status visibile/not visibile or parent category) the change is reflected in every store of the environment. A store can only edit Title and description without having impact on other stores. In the db in fact there is only one - simple - table called "category" without any reference to shop id. Is there a way to avoid this? I hope to have been clear
  5. I was wondering if its possible for different stores in a Multistore Set Up can each have different Categories or do they need to be the same categories added to the main setup? If so, do I need to add all the categories in the main setup first before setting up another store? Thanks!
  6. Hey. I have two multistore domains, siteone.com and sitetwo. (Strictly speaking, subdomains; a1.b.c.com and a2.b.c.com.) Getting a blank error 500 page at the second one. Debugger says: (1/1) ContextErrorException Notice: Trying to get property 'precision' of non-object in Context.php line 498 at ContextCore->getComputingPrecision()in Cart.php line 2174 at CartCore->getOrderTotal(false, 1)in CartPresenter.php line 334 at CartPresenter->present(object(Cart))in FrontController.php line 524 [...] So perhaps something about some configuration being missing that the second store expects? Any pointers? Cleared cache, disabled nonoriginal modules etc. Install is fairly fresh as well, haven't edited any files directly. A thread I found here on the forums says (and gives as a solution) that multistores ought each to belong to a different store group, but that makes no sense, does it? It would be impossible to unify stocks in such case, wouldn't it. Thanks.
  7. Hej Jeg ville gerne have sat multistore op i min Prestashop 1.7.8.8 men jeg synes ikke man kan finde nogle steder hvad der er af muligheder, her tænker jeg på, hvad deler de evt 2 shops ? Hvis man har betalings modul, forsendelses, tema osv i shop 1 virker de så også i shop 2 ? Det jeg drømmer om er to shops med forskellige navne og lidt anderledes index page ellers skal de være ens, er det muligt? Hilsen Dennis
  8. ▶️ Product price history Your promotions and discounts will comply with the requirements of the EU Omnibus directive. Module informs the customer about the lowest price in the past statutory time. Sales prices Promotion prices Specific prices Combination prices The module monitor and record prices changes in an highly optimized and efficient way and informs the customers of your PrestaShop store in a UX-Friendly way about product price changes on product page. 🏁 Translations: English, Polish, Italian, Spanish, French and German. 🌎 Multistore support. Setup module independently in each store. 🔗 Read more about module: https://prestashow.com/en/prestashop-modules/85-product-price-history-prestashop-omnibus.html ▶️ Detection of price changes and promotions The module will automatically detect changes in sale prices, specific prices, promotional prices and combination prices from all sources from which these changes can come: Product editing in Back-Office Importing and updating prices, such as from XML or CSV Price changes made by the PrestaShop API Changes coming from external integrations, e.g. from ERP ▶️ Price storage time In the module configuration you can specify the number of days for which the module will archive price changes. The default value is set to 30 days. ▶️ Presentation of price history The module will automatically detect where the product price is displayed in your template and display the relevant information next to the price. You can rely on full automation of the message placement or paste {hook} yourself anywhere on the product page, in the product.tpl file. Module informs customers in a non-intrusive and customer-intuitive way (UX-Friendly) about recent changes in the product price. ✅ Interactive icon - next to the product price. After tapping or hovering over the icon, the user will receive an interactive message about the lowest price of the product in the last X days or about no price changes. ✅ Interactive message - complete information about the lowest price, displayed below the product price. 🔥 Viewing and editing the price history in the back-office - access to the price history is possible in the product edition, in the PrestaShop admin panel. You can edit the prices archived by the module, which will prove useful if you make a mistake while creating a promotion or editing prices. 🔥 Multistore support - he module works with PrestaShop Multistore. You can configure the module globally for all stores or independently for each Multistore store. 🔥 Modify message content - you can modify messages in all the languages enabled in your store using PrestaShop's built-in translation system. Messages in the module are translated in English, Polish, Italian, Spanish, French and German. 🔥 Modify appearance of icons and messages - you can customize the appearance to your store by editing the module's clear and lightweight .tpl and .css files. 🔗 Read more about module: https://prestashow.com/en/prestashop-modules/85-product-price-history-prestashop-omnibus.html
  9. I'm tasked with taking a local site to a few other countries, so we will need separate sites so we can have different currencies, payment gateways, couriers, etc. (The usual stuff - nothing out of the ordinary here). My concern is based around volumes of transactions per hour. Let's assume we have 200 transactions per hour from 5 countries totaling 1000 transactions per hour. Is it better to have a totally separate installations of Prestashop, each with their own database, per country where each site manages 200 transactions per hour, or... Is it better to have a single installation with multistore active with a single shared database that processes all 1000 transactions? The multistore feature is really quite pleasant to use, but I'm worried that in a year's time, I'm going to wish I'd created separate sites with their own databases due to limited processing capacity. I guess the heart of my question is "how many transactions per hour can Prestashop reliably process before it struggles? (assuming the hosting is not a bottle neck. That it is top notch, well cached, part of the Cloudflare network with lots of RAM. Perhaps even a dedicated server.). I've seen tests that have tested the number of products that show the catalogue can reach 1 million products, but nothing about its processing efficiency. (Magento boasts about how many it can process as a reason why it's the most capable of them all, and I've experienced first hand where a WooCommerce site was struggling with just 25 logged in shoppers on shared hosting. As a result, this is a big concern in my life and don't want to get it wrong at this early stage.) I appreciate your feedback, experiences and opinions. Thanks.
  10. Hello, I am testing the multi-store with groups configured to share customers, but registered customers are not shared. When I go to another store in the group I get the login form on the customer account page. Indeed session_status() returns 1 on all front pages.
  11. Good morning everyone. I have configured Prestashop in multi-store mode. I have a problem when I have to manage product attributes. When I log in as a non-administrator user of a single store, I can easily create the attributes with their values. When I want to associate them with a product, through the "Combinations" tab, however, they are not visible. So, I tried to log in as SuperAdmin and again they weren't visible within the product. In order to make them visible, always as SuperAdmin, I had to necessarily associate the attribute also with the main store (the one created during the installation phase). I can't understand if this is a native Prestashop feature, because if so, every attribute created by a store other than the main one, in order to be used, must necessarily be enabled by me, SuperAdmin. How can I make store users autonomous without SuperAdmin intervention? Best regards. ---- Cristian
  12. Hello. Immediately I apologize for my poor English. I found an article on how to change the language change to change the multi store. my prestashop 1.7.7.1 But I have errors, who can help? or where to look? article: https://www.prestashop.com/forums/topic/382956-multi-language-store-with-unique-domains-multistore-way/ i don't have override override\modules\ps_languageselector\ps_languageselector.php so i put everything in /modules/ps_languageselector/ps_languageselector.php this is how it looks <?php use PrestaShop\PrestaShop\Core\Module\WidgetInterface; if (!defined('_PS_VERSION_')) exit; class Ps_LanguageselectorOverride extends Ps_Languageselector implements WidgetInterface { public function install() { if (!parent::install() || !$this->registerHook('displayNav2')) return false; return true; } public function getWidgetVariables($hookName = null, array $configuration = []) { $id_shop = (int)$this->context->shop->id; $id_group = (int)$this->context->shop->id_shop_group; $shop = new Shop($id_shop); $shopsList = $shop::getShops(false, $id_group); foreach ($shopsList as $index => $currShop) { $shopsList[$index]['lang'] = Language::getLanguages(true, $currShop['id_shop'])[0]; } return array( 'shopsGroup' => $shopsList, 'currentShop' => $id_shop ); } public function hookDisplaydisplayNav2($params) { $shopsList = $this->getWidgetVariables(); if (1 < count($shopsList['shopsGroup'])) { $this->smarty->assign($shopsList); return $this->fetch('module:ps_languageselector/ps_languageselector.tpl'); } return false; } } themes\classic\modules\ps_languageselector\ps_languageselector.tpl <div id="mod-ps-languageselector"> <h4>{l s='Language:' d='Shop.Theme.Global'}</h4> {if isset($shopsGroup)} {foreach from=$shopsGroup item=shop} <a href="http://{$shop.domain}" class="{if $shop.id_shop == $currentShop}active{/if}"> {if isset($shop.lang.id_lang)} <img src="/img/l/{$shop.lang.id_lang}.jpg" alt="{$shop.lang.language_code}" title="{$shop.lang.name}" /> {else} <img src="/img/l/none.jpg" alt="Flag no found"> {/if} </a> {/foreach} {/if} </div> as in the article. My mistake on the site. (1/1) ClassNotFoundException Attempted to load class "Ps_Languageselector" from the global namespace. Did you forget a "use" statement? in ps_languageselector.php line 32 at include_once() in Module.php line 1149 at ModuleCore::coreLoadModule('ps_languageselector') in Module.php line 1141 at ModuleCore::getInstanceByName('ps_languageselector') in Hook.php line 904 at HookCore::exec('displayNav2', array('smarty' => object(SmartyDevTemplate), 'cookie' => object(Cookie), 'cart' => object(Cart)), null) in smarty.config.inc.php line 167 at smartyHook(array('h' => 'displayNav2'), object(SmartyDevTemplate)) in SmartyLazyRegister.php line 83 at SmartyLazyRegister->__call('smartyHook', array(array('h' => 'displayNav2'), object(SmartyDevTemplate))) in 6e578e133ed58d47a69ee7062b6bb5122428d6e7_2.file.header.tpl.php line 81 at Block_3343910586101ad15b33e87_53697865->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_3343910586101ad15b33e87_53697865), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_3343910586101ad15b33e87_53697865)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_3343910586101ad15b33e87_53697865', 'header_nav') in 6e578e133ed58d47a69ee7062b6bb5122428d6e7_2.file.header.tpl.php line 31 at content_6101ad15b3f561_84992769(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('file:_partials/header.tpl', null, 'classiclayouts/layout-full-width.tpl', 0, 31536000, array(), 0, false) in e82d89c22dc120d03bf6a7f5543e8ff56fbae356_2.file.layout-both-columns.tpl.php line 188 at Block_12778859336101ad15ab2483_59246451->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_12778859336101ad15ab2483_59246451), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_12778859336101ad15ab2483_59246451)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_12778859336101ad15ab2483_59246451', 'header') in e82d89c22dc120d03bf6a7f5543e8ff56fbae356_2.file.layout-both-columns.tpl.php line 62 at content_6101ad15ace019_67500863(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('layouts/layout-both-columns.tpl', null, 'classiclayouts/layout-full-width.tpl', 0, 31536000, array(), 2, false, null, null) in smarty_internal_runtime_inheritance.php line 116 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyDevTemplate), 'layouts/layout-both-columns.tpl') in d67279c1e8169c42112671b957277c41b71cf45f_2.file.layout-full-width.tpl.php line 42 at content_6101ad15a99ce2_15076725(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('layouts/layout-full-width.tpl', null, 'classiclayouts/layout-full-width.tpl', 0, 31536000, array(), 2, false, null, null) in smarty_internal_runtime_inheritance.php line 116 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyDevTemplate), 'layouts/layout-full-width.tpl') in 10ad1afad3da53f0c9d3801b0f1ca9b3acdb797c_2.file.page.tpl.php line 33 at content_6101ad15a87000_96927155(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('page.tpl', null, 'classiclayouts/layout-full-width.tpl', 0, 31536000, array(), 2, false, null, null) in smarty_internal_runtime_inheritance.php line 116 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyDevTemplate), 'page.tpl') in 8b9e5a7b8263849536862e2cbe12fc8157224ed3_2.file.index.tpl.php line 33 at content_6101ad15a2fa48_41477484(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render(false, 0) in smarty_internal_templatebase.php line 232 at Smarty_Internal_TemplateBase->_execute(object(SmartyDevTemplate), null, 'classiclayouts/layout-full-width.tpl', null, 0) in smarty_internal_templatebase.php line 116 at Smarty_Internal_TemplateBase->fetch('index.tpl', null, 'classiclayouts/layout-full-width.tpl', null, false, true, false) in SmartyDev.php line 40 at SmartyDev->fetch('index.tpl', null, 'classiclayouts/layout-full-width.tpl') in FrontController.php line 704 at FrontControllerCore->smartyOutputContent('index.tpl') in FrontController.php line 686 at FrontControllerCore->display() in Controller.php line 326 at ControllerCore->run() in Dispatcher.php line 518 at DispatcherCore->dispatch() in index.php line 28 error in admin Symfony\Component\Debug\Exception\ ClassNotFoundException in modules/ps_languageselector/ps_languageselector.php (line 32) use PrestaShop\PrestaShop\Core\Module\WidgetInterface;if (!defined('_PS_VERSION_')) exit;class Ps_LanguageselectorOverride extends Ps_Languageselector implements WidgetInterface{ public function install() { if (!parent::install() || !$this->registerHook('displayNav2')) require_once() in src/Adapter/Module/ModuleDataProvider.php (line 248) ModuleDataProvider->PrestaShop\PrestaShop\Adapter\Module\{closure}('ps_languageselector') in src/Adapter/Module/ModuleDataProvider.php (line 266) ModuleDataProvider->isModuleMainClassValid('ps_languageselector') in src/Core/Addon/Module/ModuleRepository.php (line 478) ModuleRepository->getModule('ps_languageselector', false) in src/Core/Addon/Module/ModuleRepository.php (line 570) ModuleRepository->getModulesOnDisk(false) in src/Core/Addon/Module/ModuleRepository.php (line 213) ModuleRepository->getFilteredList(object(AddonListFilter)) in src/Core/Addon/Module/ModuleRepository.php (line 611) ModuleRepository->getInstalledModules() in src/Core/Addon/Module/ModuleRepository.php (line 621) ModuleRepository->getInstalledModulesCollection() in var/cache/dev/ContainerUqcy2y0/getPrestashop_Core_Form_ChoiceProvider_ModuleByNameService.php (line 8) require('/var/www/www-root/data/www/xx.com/var/cache/dev/ContainerUqcy2y0/getPrestashop_Core_Form_ChoiceProvider_ModuleByNameService.php') in var/cache/dev/ContainerUqcy2y0/appDevDebugProjectContainer.php (line 2600) appDevDebugProjectContainer->load('getPrestashop_Core_Form_ChoiceProvider_ModuleByNameService.php') in var/cache/dev/ContainerUqcy2y0/getForm_Type_Translations_ModifyService.php (line 8) require('/var/www/www-root/data/www/xx.com/var/cache/dev/ContainerUqcy2y0/getForm_Type_Translations_ModifyService.php') in var/cache/dev/ContainerUqcy2y0/appDevDebugProjectContainer.php (line 2600) appDevDebugProjectContainer->load('getForm_Type_Translations_ModifyService.php') in var/cache/dev/ContainerUqcy2y0/getForm_RegistryService.php (line 117) appDevDebugProjectContainer->{closure}() in vendor/symfony/symfony/src/Symfony/Component/DependencyInjection/ServiceLocator.php (line 64) ServiceLocator->get('PrestaShopBundle\\Form\\Admin\\Improve\\International\\Translations\\ModifyTranslationsType') in vendor/symfony/symfony/src/Symfony/Component/Form/Extension/DependencyInjection/DependencyInjectionExtension.php (line 64) DependencyInjectionExtension->getType('PrestaShopBundle\\Form\\Admin\\Improve\\International\\Translations\\ModifyTranslationsType') in vendor/symfony/symfony/src/Symfony/Component/Form/FormRegistry.php (line 78) FormRegistry->getType('PrestaShopBundle\\Form\\Admin\\Improve\\International\\Translations\\ModifyTranslationsType') in vendor/symfony/symfony/src/Symfony/Component/Form/FormFactory.php (line 74) FormFactory->createNamedBuilder('form', 'PrestaShopBundle\\Form\\Admin\\Improve\\International\\Translations\\ModifyTranslationsType') in src/PrestaShopBundle/Form/Admin/Improve/International/Translations/TranslationsSettingsFormHandler.php (line 78) TranslationsSettingsFormHandler->getForm() in src/PrestaShopBundle/Controller/Admin/TranslationsController.php (line 104) TranslationsController->showSettingsAction(object(Request)) in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php (line 151) HttpKernel->handleRaw(object(Request), 1) in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/HttpKernel.php (line 68) HttpKernel->handle(object(Request), 1, false) in vendor/symfony/symfony/src/Symfony/Component/HttpKernel/Kernel.php (line 200) Kernel->handle(object(Request), 1, false) in admin673fujfr6/index.php (line 82) Thank you for your help.
  13. As you can see, it says no image available (this is because product is from another store, the stores share shopping carts). Also the page it redirects to when clicking on ourProduct is not the actual product page on the other store but on the same page as I am currently (i am on myshop.com, product is originally from myshop.com/store2 and when clicking on it it redirects to myshop.com/ourProduct not myshop.com/store2/ourProduct. Have searched for solutions but have not found any working ones. Prestashop version is 1.7.7
  14. Hello, We're facing a problem on a multistore prestashop 1.7.6.5 . We can't set permission for an employee only for one store. The option was in prestashop 1.7.5.2 . It's a big issue for us and we don't find any existing solution. Could anyone help us to know why Prestashop removed this option and how to fix it ? Thank you
  15. This prestashop addon helps the administrator to translate websites using the google Translate widget based on visitors' geolocation. Facilitates international sales, and helps international clients to understand the store in their language The simple act of translating your website will increase your traffic significantly. It allows you to start making inroads into 70% of the global population that doesn’t speak English. A multilingual store increases accessibility to potential clients. Not only does it increase your chances of attracting more clients, but it allows you to attract more diverse clients. Offering information and services in multiple languages builds credibility and makes your site look more professional. It also makes your site friendlier to these potential clients, because people naturally prefer doing business in their own language. The benefit of translating your website is an improved image and better branding. Features - Make your website instantly available in 100+ languages. - Visitors geolocation details using ip address and show translation automatically based on visitors language. - This module expands your global reach quickly and easily. - It helps in SEO rankings. - Easy to use and configure. - It can be the hook in the left, right block, header, and footer positions. - Good translation from Google. - Support multiple browsers and operating systems. - Lightweight and fast loading on the web page. - SEO friendly. - Support all browsers: Firefox, Chrome, IE, Safari, etc. - Lightweight. (Smaller file size which loads faster.) - Increase sales, conversion rates, and product promotions. - Maintain existing customers & Attract new customers. - Lower marketing expenses, exposure to potential customers, and reach targeted audiences. - Compatible with PrestaShop 1.5.x,1.6.x and 1.7.x. - Multiple browsers compatibility(IE, Firefox, Opera, Safari, Chrome, and Edge). - Mobile, Tablet, and all devices compatible. - Multi-language and Multi Store compatible. - 24*7 Support. Benefits to Customers - Customers can have your entire website in their language. - Customers will find it very easy to read and understand your store in their language. - Customers trust your products & services. - Maintain existing customers & Attract new customers. - Increase in sales and store traffic. - Exposure to potential customers, reach targeted audiences. Installation Step 1: Upload the module zip file from the back-office Module & Services menu tab. Module Manager area using the upload button. After the successful installation module menu, the link will appear in the left menu or top menu in the back-office more area. Step 2: Install the module using the install button. Step 3: Visit the module management page from the back-office "More" area (section) in the left menu in the back-office. Step 4: The module installation process is very easy, how module configuration works can be seen in the demo instance. Step 5: Please visit our demo instance for module configuration and usage demo. - Module works without making any change in the existing PrestaShop file so that existing customization and theme change do not affect. - We provide free technical and feature support in installation, and configuration, as well as access to updates available for this product. - Free support on installation, configuration, and customization as per store requirements, for example, new hook addition to your store. Recommendation : Please visit the developer's modules page for other interesting modules https://addons.prestashop.com/en/2_community-developer?contributor=301729 Other : Please leave your valuable feedback and rating after purchasing and using the module. This will help to increase self-confidence, improve service, and enhancements the module as per requirements to make it better for different online stores. For a demo on version 1.7.x visit the below links Front-office Demo URL => https://www.hrms-systems.com/presta-addons/en/ Back-office Demo URL => https://www.hrms-systems.com/presta-addons/admin619j6kpbb/index.php For a demo on version 1.6.x visit below links Front-office Demo URL => https://www.hrms-systems.com/presta-apps/en/ Back-office Demo URL => https://www.hrms-systems.com/presta-apps/admin539fyipwq/index.php OUR PRESTASHOP ADDONS MARKETPLACE URL PrestaShop Marketplace URL => https://addons.prestashop.com/en/2_community-developer?contributor=301729 Alternate download URL => https://www.presta-addons-modules.com/en/prestashop-automatic-google-translation-geoip.html
  16. [SOLVED] What do I have? A website: domain.com Prestashop installed in: prestashop.domain.com Multistore is enabled What do I want? Multiple shops in subdomains like: someshop.domain.com anothershop.domain.com What did I do before asking? Check and followed: Prestashop Docs for PS17: Setting a shop's URL Created multiple shop in prestashop.domain.com like: someshop.domain.com anothershop.domain.com This is the setting for someshop.domain.com : What is the problem? someshop.domain.com does not show anything and it does not work ------------------------------ UPDATE: SOLVED Special thanks to @Prestachamps ❤️ What is the technical issue? Web server does not know that where is someshop.domain.com and you need to tell your web server to point to specific route How to solve this generally? You should find out how to set up subdomains in your web server. Then create a subdomain for each shop that belongs to multi stores list like: someshop.domain.com Point the subdomain to Prestashop instance route. This means: someshop.domain.com will always load prestashop.domain.com But it does NOT redirect to prestashop.domain.com (This is key point) This pointing is meant to work like rewriting, NOT redirecting. Otherwise it does not work. How to solve this in cPanel? Create a subdomain of someshop set Document Root to prestashop.domain.com
  17. Hej Jeg arbejder på at oprette en multistore hvor, ShopA er min nuværende og ShopB bliver den nye, ShopB skal dog være med et andet logo, et helt nyt visuelt udtryk, og reelt en helt anden shop hvor man ikke kan se de kommer fra samme adresse. Og samme adresse er netop problemet! Kan ShopA og ShopB begge have samme varekartotek, og samme lager, samt ordrerne lander samme sted, så det kan klares fra samme backend? i så fald hvordan?
  18. Hi, I have multistore enabled, and I wish to have a page before accessing the website that let an user chose a store (according to his location). So the idea is that when an user access store1.website.com or store2.website.com, he lands on a store selector page "store_selector.html" And then, the user clicks on a link "store1.website.com/index" or "store2.website.com/index" that leads to the default index. I tried to modify the .htaccess that way : RewriteEngine on RewriteRule ^index$ /index.php [L] DirectoryIndex store_selector.html But that was before discovering that every page is redirected to index.php, and then the "Dispatcher" is used to redirect to the right page. I also tired to go in Shop Parameter / select store1 / select "index" page and add "index" in the "Rewritten URL" field. But that does not seems to change anything. In Advance parameter / multi store, I could set a "Virtual URL" to "index", but that means that it change every link on my store, which is already online (not good for SEO). I hope that I don't have to play with the Dispatcher in PHP and that there is a simpler solution. Any help would be welcomed.
  19. Hi, I have a multistore with 2 stores: Store 1 : theme use is "at_auros Version 2.2.0 Leotheme Team" Store 2 : theme use is "leo_nom Version 1.0.1 Leotheme Team" When i am on store 1, the user icon and cart icon are display: But when i go to the store 2 and return on store 1 after, icons disappears: I have to clear cache for solve the problem. My compilation smarty parameters are : "Recompile templates if the files have been updated" When i turn this to : "Force compilation" everything work, but its not good for production What can i do please ? Thanks
  20. In multistore mode, different shops have same template, but slightly different settings like colors, logos, etc. This is easily accomplished by adding shop-specific classes to the templates. Like when adding a shop id to the class-names in layout-both-columns.tpl. However only the shop-name, shop-addresses and other details that can all change regularly are available through the getTemplateVarShop() in the FrontController. Why is the $this->context->shop->id not in there, so it can easily be used in smarty as {$shop.id} Also the smarty-var {$shop.name} is not the name of the shop, but the name of the shop-group! So all names of my shops in same group are same. So, how do I get the shop-id in the layout-both-columns.tpl template?
  21. ✔️ PrestaShop Invoices Extender Pro module Handle invoicing yourself. Generate all types of invoices directly from your store: for store orders and sales from other channels: phone, or email. Generate any type of invoice, send it to your customers and finally integrate generated invoices with your accounting software. 📑 Read more about module: https://prestashow.pl/en/prestashop-modules/39-prestashop-invoices-extender-b2c-b2b.html ✔️ Complete invoice management for PrestaShop 1.6 & PrestaShop 1.7. 🏁 EN and PL translations. You could translate module and PDF using PrestaShop Translations. 🌎 PrestaShop Multistore support. Setup module independently in each store. Invoicing automation. Assign the type of generated invoice to the order status. The module will automatically generate a given type of invoice, if the order in the store gets the appropriate status. Editing of data on the invoice. If there are changes in the order, for example in items, quantities or amounts - you can generate a correction invoice. The correction invoice show changes <before and after>. Manually generated invoices can be edited at any time and without any restrictions. International sales support. Invoices Extender support all currencies available in your store. Generated by the module invoices are in the currency of the order and have a summary of the currency conversion, e.g. EUR to PLN with the exchange rate. If you sell products with different VAT rates, information about the rates along with a summary of all tax rates appearing in the order will be placed on the invoice. Manual invoicing. This module help you handle sales coming from other sales channels (telephone, e-mail, etc.). When issuing invoices manually, you can choose recipients and products from your store (autocomplete) or provide any data by completing the fields yourself. Multistore and multi-language support. Your invoices can be generated independently for all stores in Multistore. You can set up an independent invoice issuer for each store. You can translate all phrases on generated invoices to languages enabled in your store. By default, the module is fully translated into Polish and English. Export to CSV and PDF. This module allows you to export sales statements and invoices. Filtering (Invoice type,Currency, Date from-to), Export: CSV, PDF format (ZIP package with invoices). File with 5,000 invoices generate in 10 sec. Support all type of invoice: Proforma, VAT Invoice, Invoice without VAT, Correction, Return and Duplicate Custom invoice number - fully customizable with number reset per month/year Optional "Bill or Invoice" select in order process Fully automate invoicing: generation of invoices by order status International sales support: multiple tax rates, tax table, currencies conversion, languages and more... Sending invoices by e-mail "Invoices" section in back-office order details - generate, preview and change. "Invoices" section in customer's My Account You can completely disable access to invoices for customers Export to PDF and CSV - automate flow of transfer invoices to accounting software 📑 Read more about module: https://prestashow.pl/en/prestashop-modules/39-prestashop-invoices-extender-b2c-b2b.html 🧪 Check module at demo store: https://presta.show/generate/PShowInvoiceExtender
  22. Hi, I have a Prestashop installation on the example.com domain and I need to create a second dedicated ecommerce for b2b. I want to use the Prestashop Multistore function, which in some tests I managed to configure correctly on virtual URL. However as I will have to modify some files such as the index to force access to view the site, I need a physical url for ftp. What I am wondering is how does the configuration with physical url work? Once a physical URL of a folder created in the directory has been associated, does the physical installation of prestashop not take place automatically? Or in that folder, do I have to install prestashop myself? Thanks in advance for the reply.
  23. Salve, avrei bisogno di capire una cosa che non riesco a comprendere Vorrei utilizzare la funzione multinegozio, ma non riesco a capire una cosa dopo diversi tentativi Faccio esempio per spiegarmi meglio devo realizzare questi siti facenti parte tutti dello stesso dominio.. ogni sito è quindi con sottodomini 1.miosito.com 2.miosito.com 3.miosito.com etc. E' necessario dover installare prestashop su ogni sottominio? o mi basta una installazione singola (per esempio su 1.miosito.com)? Se devo installare prestashop su tutti i sottodomini devo utilizzare uno stesso nome utente e password? Ci sono altri accorgimenti da attuare? Grazie
  24. Hej, mam taką sytuację: 3 sklepy na multistore i 1 blog na WordPress. Blog jest w tej chwili w subdomenie dla jednego sklepu Y (blog.y.pl), chciałbym, żeby był w folderze y.pl/blog/. Niestety domyślnie cały multistore jest zainstalowany w folderze domeny X, a blog należy do sklepu Y i jeśli wrzuce teraz blog do folderu, to prawdopodobnie będzie się wyświetlał w domenach X, Y i Z. Czy dobrze rozumiem problem? Da się to jakoś ogarnąć tak, żebym dla każdego sklepu z multistore mógł zrobić osobnego bloga w folderze /blog/?
  25. Hola a todos, Estoy configurando un nuevo dominio con la opción de multistore, funciona todo aparentemente, capturar productos y categorías individualmente, los url redireccionan correctamente usando un url virtual. Las configuraciones de url quedan como sigue: Estamos en la parte de hacer compras de prueba, todo funciona al 100% en la tienda principal, pero en la tienda secundaria al querer agregar un producto al carrito de compras la url resultante marca un error 404 Not Found: ¿Alguien ha tenido este problema? ¡Gracias de antemano por la ayuda!
×
×
  • Create New...