Jump to content

Aris S.

Members
  • Posts

    12
  • Joined

  • Last visited

Contact Methods

Profile Information

  • First Name
    Aris
  • Last Name
    Schlingmann

Aris S.'s Achievements

Newbie

Newbie (1/14)

  • One Month Later Rare
  • One Year In Rare
  • Week One Done Rare

Recent Badges

3

Reputation

  1. We had the same issue on PrestaShop 1.7.5.2 : when "Set default country from browser language" is enabled and your browser language is e.g. "English (United States)" the prices are shown VAT excluded, but only on first page load. After refreshing the page, the prices are shown including VAT... "Fixed" it by setting "Set default country from browser language" to NO.
  2. Hi Guy, It's now possible when editing a product and clicking the 'Add feature' button to choose a previously assigned feature and add it with another value. So yes, if you have a feature 'Color' you can assign it once with value A and once with value B.
  3. Thanks @Zitty, didn't notice the issue on the PrestaShop Forge before.
  4. I have investigated the issue further by comparing the latest PS 1.6 and latest PS 1.7 releases and found the following in classes/Link.php, getAdminLink(): In 1.6 the link is created as follows: return Dispatcher::getInstance()->createUrl($controller, $id_lang, $params, false); In 1.7 the link is created as follows, if the link is not handled by Symfony: return $this->getBaseLink().basename(_PS_ADMIN_DIR_).'/'.Dispatcher::getInstance()->createUrl($controller, $idLang, $params, false); So, in 1.7 a full URL is created, where in 1.6 a relative URL is created. In multistore, this is not want. It creates a full URL to shop B when you are logged in using the URL of store A. Now I'm wondering if I am the only one experiencing this issue?
  5. I am using "alias b to a" , via DirectAdmin. But also on a local environment using MAMP and virtual hosts the issue persist. You can reproduce it as follows with PS 1.7.3.0: - Perform clean installation of PS 1.7.3.0. - In backoffice, enable multistore feature - Add second store and fill in second store URL - Login into store A (on the URL of store A), and switch in PrestaShop to shop B. - Now the URL to e.g. the Dashboard page is the URL to store B. - Clicking on the Dasboard URL takes you to the login page of the backoffice on the URL of store B. That had to be the URL of store A! Only the context needs to be changed to store B, not the URL! Hope you can help us out!
  6. We have a problem using the 1.7 multistore feature. We have 2 stores defined, store A and store B. Store A is the default shop. When logging in to Store A there is no problem. When logging in to Store B, the URLs of store A is used, for example in the AJAX calls to refresh the dashboard data. This result in errors like: - Failed to load <URL>: Response for preflight is invalid (redirect) - Request has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin <URL> is therefore not allowed access. In fact Store B should use it's own URL and not the URL of store A. Anyone experience with the same issue? Found this topic: https://stackoverflow.com/questions/43910748/xml-http-request-error-on-prestashop-multiistore but there is no response...
  7. Thanks, also what I was looking for. To adjust it the 'clean' way you can override the Mail class: class Mail extends MailCore { public static function Send($id_lang, $template, $subject, $template_vars, $to, $to_name = null, $from = null, $from_name = null, $file_attachment = null, $mode_smtp = null, $template_path = _PS_MAIL_DIR_, $die = false, $id_shop = null, $bcc = null, $reply_to = null) { // Don't send an email a credit slip is created (not configurable in backoffice) if ($template == 'credit_slip') { return true; } return parent::Send($id_lang, $template, $subject, $template_vars, $to, $to_name, $from, $from_name, $file_attachment, $mode_smtp, $template_path, $die, $id_shop, $bcc, $reply_to); } }
  8. We have the same problem. Any solution yet? See also http://forge.prestashop.com/browse/PSCSX-6787
  9. We have the same problem. Any solution yet? I think this is a PrestaShop bug, see http://forge.prestashop.com/browse/PSCSX-6787
  10. Thanks, I can use the hook ActionObjectCombinationAddAfter (mind the *AddAfter instead of *AfterAdd). Issue closed.
  11. I would like to take some custom actions after adding a new product combination (generate an EAN13) but I can't find the correct hook for it. I've found a hook ActionProductAdd, but there is no hook ActionProductAttributeAdd?! Can anyone help please?
  12. We have a problem updating the stock quantities using advanced stock management. When updating the stock quantity for a new product the stock quantity in the table ps_stock_available is not updated. Is anyone familiar with this issue? Update: Problem was caused by using an external module to add new products quickly. Some data was not updated correctly (ps_stock.advanced_stock_management was not set to 1, ps_product_shop.advanced_stock_management was not set to 1, ps_stock_available.depends_on_stock was not set to 1). Problem solved.
×
×
  • Create New...