datakick

It's sad that Mollie does not support thirtybees natively. But I'm also pretty sure they do not intentionally block thirtybees. In fact, there is nothing in the api request that would provide information about used platform. Mollie is an api-based solution, and anybody can integrate with them. It doesn't matter if it's open-source, or custom made proprietary solution. They don't really care. This whole flame is based on a fact that some part of the official mollie module does not work on thirtybees. This can, of course, happen. You all know that there are some modules that need some modification, attention, and love. I guess the problem here is in webhook implementation. It either fails with some 500 error page, or maybe short-circuit the processing due to some condition. Because webhooks are triggered by Mollie automated service, nobody notices these errors. We observe them only indirectly by the fact that the order status does not change automatically. But that does not mean that Mollie is blocking thirtybees, now does it? Let's calm down and work together to troubleshoot this problem.

Have you cleared caches? (server, browser, cloudflare,...)? It's a change in js file and it can be cached anywhere... But it's definitely there

Sorry, that is not a best solution. It is just a cover-up of a bigger problem: there is something in your system that is trying to set Blowfish object inside your Cookie. There used to be a _cipherTool property inside Cookie class. This protected property used to hold cookie encryptor instance. I bet you have some Cookie override that tries to set this (now not existing) property, which in turn causes the fatal error. You can try this: revert your fix edit class Cookie.php at the very beginning, add this line: protected $_cipherTool; That should fix your problem. Anyway, this is a core compatibility issue, and it should be handled in the core.

this is error messages encrypted using your server's private key. So only you can decrypt this message. Go to Advanced Parameters > Logs, you will find decryption tool there.

Unfortunately it wasn't fixed properly. Although beesblog implements hook GSitemapAppendUrls, it does not register it inside its install method. I'll fix this for the next version of this module. Meanwhile, if you are in hurry, you can edit beesblog.php file, find method getContent, and add this line inside it: $this->registerHook('GSitemapAppendUrls'); Then save, and open beesblog configuration page. That will register the hook. Now you can delete the line again -- module has been successfully paired with sitemap

Oh, you are right. This commit is not in release 1.0.22. It will be in the next version. Sorry for the confusion. I have some work in progress, so I don't want to release it yet. But you can use this pre-release revision: revws-1_0_23-pre.zip

You need to switch Display review average in to Custom placement, and then edit your product.tpl template and add hook to appropriate place

btw, this option to adjust placement of review average was added to the module as well (both free and premium). I must say it looks much better when placed under the product name. See this example on beautiful niara theme

Thanks for confirmation. This is a good workaround until this is fixed properly in core

Hi everyone, I've released a new premium version of revws module. Upgrade 2.0.4 brings one of the feature everyone asked me about - Store Reviews. You can check this new functionality on my demo account - front office / back office. If you don't need this feature, free version is still there and fully supported.

That statement is true every theme... because it's a problem of smarty engine, not theme itself. Thirtybees will eventually migrate to newer version of smarty that does not generate warnings / notices. But since that is very dangerous step, we are in no hurry to do that, and we want to have contingency plans in case new smarty version does not work as expected. That means some way to switch to older smarty version. In 1.0.9 error reporting was revamped, and the display_errors php settings in dev mode was disabled. That means that the theme will work just fine on php7.2 (you will still see the warnings / notices in error log, but not in the page itself).

@Brian It looks there are either some remnants of ps16 (or older) php files in your core, or that you have some module that's not compatible with thirtybees. Use gitupdater module, and try to compare agains 1.0.8 version. It should tell you that everything is up to date, and no changes are necessary (because you are now on 1.0.8 version). But if there are some extra files from previous prestashop versions, or if some files were not installed/migrated correctly, the module will tell you. And allow you to fix this. Then run tbupdater module to update your modules. If it still does not work, then let us know.

@Brian the problem with missing theme configuration page was solved a week ago, it will be part of the next release. If you need it right now, you can use traumflug's new gitupdater module and migrate your 1.0.8 to bleeding edge branch. That will pull this change to your server. Then you can reinstall the theme Or you can simply apply this commit: https://github.com/thirtybees/thirtybees/commit/e6e5b9f3a5b8a59078fc9e5184e2f24d3c5a2bce

Nevertheless, when you upgrade to newer version, you will loose this modification.

Are you changing core files? Please don't do that... you'll get stuck with outdated version of thirtybees. These changes should be handled by custom module. Such module can either provide overrides, or hook to appropriate hooks if exists. In this case, there is a hook named actionEmailSendBefore that can be targeted. This hook can be used to adjust email parameters, for example to add your email address to bcc for all emails, change subjects on the fly, etc... And you can use it to block some emails from being sent, by returning false value from the hook. This is clean and reusable way to customize your shop.

as the reply states, gmail rejected the email because it did not pass SPF check You need to add SPF records to your dns, so email servers can verify that your server can send emails on your domain’s behalf

You can either install the apcu extension, or modify configuration of your prestashop you are migrating from and change the caching system in /config/settins.inc.php to something else

@cprats pm me your ftp access, I'll check this for you

There is some code that's trying to communicate with some external service. You need to figure out where that code is, and what url it tries to access. Since you wrote that it happens roughly at the same time, I would start by looking at the module with some cron support.

@Smile what you are trying to do is to maintain your own fork of thirtybees platform, with all the benefits and drawbacks. This also means that you can't use update module to update your site, because this module works against thirtybees codebase. To keep updated, you will need to manually merge thirtybees git repository to your bitbucket fork, resolve all potential conflicts, and then manually update your site. This can get pretty ugly. I would recommend you 1) not change core code. Implement your own custom module instread, and hooks / overrides to extend the core functionality 2) if you plan to change community theme, then clone this theme to your own, change it's name, and carry on from there. You can, of course, try to merge changes to community theme to your theme, if it makes sense. But even if you don't, you should be ok. Your *old* theme should still be compatible even in future version of thirtybees

Works very nice and fast. Congrats on this release! I tested it a bit, and here are my notes: 1. my locally modified files are correctly listed in Files to get changed, but are not marked as M (this worked when I updated from 1.0.8 to 1.0.x, but when not when downgrading back to 1.0.8) 2. I could not find if my modified files are saved anywhere before they get overwritten by updater module 3. I strongly recommend to not touch community theme at all, as everyone makes changes to it. Unfortunately we don't have ps17 template inheritance functionality yet

If you are not willing to wait for 1.0.9, then you can try to apply the fix from this commit (or simply copy the newest version of Configuration.php file to your tb classed directory). That should fix this problem.

I don't think this is tb related. That's probably problem with your server configuration (firewall, connection timeout limit, etc...) or with the server your server is trying to communicate with.

Disable module Block Featured Products

You might be right. I've submitted a fix for this issue today. You can download the latest version of classes/Configuration.php file from github, upload it to your server, and test if it helps. If you do so, don't forget to let us know the result