Jump to content

musicmaster

Members
  • Posts

    5,553
  • Joined

  • Last visited

  • Days Won

    55

musicmaster last won the day on August 1

musicmaster had the most liked content!

Contact Methods

Profile Information

  • Location
    Netherlands

Recent Profile Visitors

30,624,230 profile views

musicmaster's Achievements

  1. This is what I am talking about. I clicked the Link button on a product page with a price of 72.95. And now it ask me to pay 7295.- Sorry for the language. But I assume that it looks the same in other languages.
  2. To enable debug mode: - download /config/defines.inc.php - open it in a text eeditor - set _PS_MODE_DEV_ to true (It should look so: define('_PS_MODE_DEV_', true);) - save the file and upload it again.
  3. I have the Stripe_official module installed under PS 8.2.3. When I click the ">Link" button it shows the login page with at the bottom the price times 100. So 23,95 becomes 2395,00. What could cause this behavior? When I look at the page source in the browser I see the javascript variables stripe_amount and stripe_express_amount both having the value as 2395.
  4. It is online again. I found that the problem was a bit wider. The new version - 1.36m - should solve it.
  5. There is some rather serious bug in the Prestools Integrity-repair code in version 1.36k that was available last week. If you have that version please update to version 1.36l.
  6. I uploaded a version that fixed that. The code checked for a field that is only present in Prestashop 1.6.1 and newer.
  7. "Warning: mysqli_connect(): Headers and client library minor version mismatch. Headers:30308 Library:30407 in /home/.../DC_Prestools_Suite/login1.php on line 381" That is a server problem. Not a Prestools problem. You should ask your hosting provider about that. They may have made an error while upgrading some php module. Quite probably your Prestashop installation suffers similar problems. The difference is that Prestools is built to bring out any problem immediately in the open so that it can be solved while Prestashop gives priority to giving the user a smooth experience while hiding problems - hoping that they are not serious. BTW: when you report errors in Prestools please do that for the latest version. That way your line numbers will match with what I see.
  8. I have started to study the ps_checkout log files under the /var/logs directory. I see lots of entries like [2025-10-29 19:21:04] ps_checkout.ERROR: Webhook Dispatcher error: Header validation failed: Shop-Id can't be empty [] {"process_id":3177005} These errors mostly (not always) happen in the minutes after some Paypal error. Different types of Paypal errors can be the initiator. Sometimes there is a follow up error: ps_checkout.ERROR: ADD API call failed for order 1234: Unprocessable Entity [] {"process_id":2690942} Does anyone know what this is about?
  9. I don't understand your question very well. If you would put in the new shop Transformer too it will be a version fit for the new Prestashop version. If those versions use the same variables you could use Copy_shopdata_confhub to copy the configuration or the table copying options to copy module specific tables. But it is up to you to decide whether that applies.
  10. In my Cpanel server log I see the following error appearing many times: Trying to get property 'id' of non-object in /classes/module/Module.php on line 2137 When I look at that line in the code (Prestashop 8.2.3) I see: if (Db::getInstance()->getValue('SELECT `id_module` FROM `' . _DB_PREFIX_ . 'module_shop` WHERE `id_module` = ' . (int) $id_module . ' AND `id_shop` = ' . (int) Context::getContext()->shop->id)) { $active = true; There is only one "id" here: Context::getContext()->shop->id I don't see the error in the localhost copy of the shop. Does anyone have an id what could be happening here?
  11. If you don't have gdpr, newsletter (emailsubscription) or wishlist related data or data connected to specific modules than this looks rather complete. But don't forget to test first.
  12. I moved a new version of a shop from a working directory to the root to make it the active shop. And then things went wrong: - Suddenly there was a javascript error with as a result that the TinyMCE editor no longer worked. The search field on the modules page didn't work either. The javascript error is in main.bundle.js - On the modules page there appeared at the top of the page the warning: 10 of your modules are no longer covered by Business Care - At the top right of the backoffice the buttons were pushed right and became clustered. I tried to disable ps_mbo but that crashed my backoffice. The only way to get it running again was to declare the module active in the ps_module table. In its new state the business care warning and the presence in the left side menu had disappeared but the javascript error remained. Later I also added the module again to the ps_module_shop table to fix a Stripe error that falsely claimed that the ps_eventbus and ps_accounts modules were no longer active. Does anyone have an idea how to solve this situation? PS version 8.2.3. ps_mbo version 4.14.0. Update: a day later the problem suddenly disappeared
×
×
  • Create New...