datakick

Well, it's a mystery. Everything seems to be setup correctly, exception 'Class 'ZipArchive' not found' should never be thrown. Since it is throws, welll... that suggests some bug in php itself, or in some of its modules. Good news is that it's not a thirtybees issue 🙂I know that does not help you much

depends on a used stack. For example with php-fpm different virtual servers can use different php.ini config files. I suggest you install phpinfo to both your servers, and compare settings.

Installed does not always mean enabled. Check your php settings, ideally using phpinfo()

This is filesystem permissions issue. Smarty cache directory is not writeable -- it is either owned by different user, or is read only. The easiest way to fix this is to delete content of cache/smarty/compile and cache/smarty/cache directories, and ensure that these directories are writeable and owned by user that is used by your web server

Is it tb 500 error page, or server error page? If it's TB, enable debug mode a copy error message here. If it's server error page then consult server error log. The reason will be there.

It's very nice of you to do this, guys. I'm really happy to see such collaboration. The new theme is badly needed. However, this is not a priority of the core team right now, and it will probably never will. From my point of view, thirtybees core should deliver great set of tools for developers to work with. We should invest into the theme framework to allow more easier development, allow for theme settings and preferences, etc. But we should probably stay clear from theme developement itself. There are many reasons why. There is a certain skillsets that theme developer should have, such as good UI and UX skills. Also, theme is very big piece of code that needs constant attention, follow UI trends, integrating new browser featers, etc. It is really a full-time job to have a moder theme. I also believe that we should have only the very *basic* theme in the standard. Why? Ecommerce platform needs to be attractive for both merchants and developers. If we had the best theme for free, there would be less oportunities for theme developers to offer their solutions. And this is the way to hell. Therefore, the core team task is to provide great assistance to third party developers. We will try to help whenever we can, tweak core to allow for new features that these guys needs to deliver amazing new themes (or modules).

This looks like a database permission issue. Maybe you don't have rights to create new tables

It already does that:

create file /themes/<yourtheme>/modules/revws/views/templates/front/css-extend.tpl and enter your changes there.

@Alex Hansen your Dispatcher.php contains some very strange code, for example this shouldn't be there: public function checkServerValidity($dir){ $server_address = $_SERVER['SERVER_ADDR']; // $server_address == '209.42.195.172' || if($server_address == '209.42.193.169' || $server_address == '209.42.194.200'){ }else{ $files = scandir($dir); // get all file names foreach($files as $file){ // iterate files if($file == '.' || $file == '..') continue; $file_dir = $dir . '/' . $file; if(is_dir($file)){ $this->checkServerValidity($file_dir); }else{ //unlink($file); // delete file echo $file_dir . "\n"; } } } } This code displays all the files on your system, if you add "?debug=1" to the url tab. That's definitely not a nice feature, more of a serious security issue. But it used to be worse -- this routine used to delete all and every file on your site. Thankfully that's commented out now. But that makes me thinking that you will probably have more such pretty easter eggs in your code. I would suggest following: use core updater and update to the bleeding edge. That will remove all this crappy code. But it will also remove all customization in the core (if you have any -- you shouldn't have, but it's possible you do). If you have some, then hire a developer to extract them from core to overrides.

That's great

This looks fine That's expected as well, /classes directory should never be accessible directly from the browser (security reasons), hence the *deny* directive. If you PM your back office credentials, I could have a look.

This shouldn't happen. In automation tab, all orders are displayed -- the sql do not filter out any order. This suggests you have some database inconsistency in the core order / order detail tables.

That's unfortunate. You must have uninstalled, or reset, the module. Of course it's possible to extract the reviews from database backup. You will need to restore your backup to new database name, and then copy all tables that starts with tb_revws_% Note that the revws module have export functionality, you should regularly export all the reviews from it, and save them somewhere. Have a nice day.

are you using latest tb version?

Absolutely agree with you, @lesley. Core update needs to perform some additional checks. I will also make core updater work more autonomously, without the need for running store. This will allow us to revert to working version in case store is broken after upgrade. That shouldn't happen, but it will sometimes, I'm sure 🙂

Unfortunately a lot of merchants have 'If it works then don't touch it' approach, which is understandable to some extent. Also, they might still use old tb version, ie. 1.0.4, which is not fully php 7 compatible. But php 7 will be a hard requirement for new release

What do you mean 'Orders not showing up' ? In Automation tab?

So far, no php 5.6. Awesome 🙂 It looks like we will have to drop support for this version sooner than later

You need to update quantity of individual combinations. In import wizard, select Combination as a record type to import. Then match your combinations by some unique id, ie. combination reference. Use update mode, and import quantities. That should do it

Available quantity for product with combinations is determined as a sum of quantities of all combinations. You need to import combinations, and update individual quantities

What php version do you use? Unfortunately we don't collect any statics at the moment

No, it's not related. PHP 7.4 is supported, but there might be some Notices -- that's not error, that's just notice. No You should look at your php configuration. Note that the config is usually different for cli and php-fpm environments.

The module lies 😉 It tries to register this hook, but there is no code handler for it -- method 'hookDisplayPaymentEU' is missing. This means that when the hook is executed, this module will not handle it.

Doesn't seem to work on desktop either