musicmaster

One tip on reducing database size: besides the usual suspects like ps_connections*, ps_guest, ps_page , ps_pagenotfound and ps_sekeyword you can also choose to truncate ps_search_index and ps_search_word. You just will need to regenerate them later on. ps_pagenotfound registers when people try to access a non-existing page on your site. ps_sekeyword registers with which keywords people found your site via the search engines.

What is the problem with Winmerge? I regularly use it. Export the structure or the whole database from two databases and comparing the resulting sql files usually works. Occasionally I need to put the sql file in a database to change all the prefixes when they aren't the same. Jumping between places with differences I usually find those differences that are relevant for my problem rather quick.

As you may well aware Prestashop reduced that functionality in its 1.7 version. They provided two motives. One was that their stock management software had quite a few bugs. The other was that the stock management needs of companies are so diverse that it is better to focus on having good interfaces/modules for specialized stock management software packages.

Thank you for the link. That shows indeed room for improvement. However, I doubt that this explains my problem. Amsterdam is working. And there is the very strange phenomena that I am working in the backoffice or Prestools and it works. And then I click there a link to the webshop and I get this DNS_PROBE_FINISHED_NXDOMAIN page.

I almost daily see the error "DNS_PROBE_FINISHED_NXDOMAIN" on my TB 1.1 website. Refreshing the page or just waiting solves the problem. But of course first impressions count. The problem may also be restricted to Chrome - I am not sure about that The puzzling thing is that it only happens in the shop. When I run the backoffice or Prestools it works. That suggests that this may be a problem of the shopping software and not the hosting. Does anyone know what causes this and how it can be fixed?

I have some trouble with the hosting. The website is still there but sometimes it initially says that it is down. When you refresh the page you will see that it is still there.

is this due to the "disable non-Thirty Bees modules" flag?

I did some experiments on your site and placed a test order. I saw quite a lot of warnings. On the first page I got the notice: Undefined offset: 2 in classes/tax/TaxCalculator.php at line 155 On later pages I got many times two notices from php-debug.js at line 53, 38 and 57: Notice: Trying to get property 'value' of non-object in themes/panda/./header.tpl Notice: Undefined index: sttheme in themes/panda/./header.tpl Another error that I got was this: When after the order I clicked on the logo to go to the homepage I only got the logo and for the rest a white page. This page has the familiar php-debug.js notice duo many times repeated. So I tried some other things. First I went into my user account. That worked. Then I tried a random "page": just the url followed by some random characters. That triggered an error page that allowed me to search on the site. So I searched for "caja". Now I got a real debug mode error page: I am not sure what this all means. Maybe Datakick recognizes what happens here.

The type of attribute is not a property of the product but a property of the attribute.

Is this discussion also relevant for Thirty Bees? https://www.prestashop.com/forums/topic/1045112-is-prestashop-able-to-cope-with-new-european-tax-laws/ Implementation would mean that you can set the price incl VAT while the price for each EU would be different depending on its VAT rate.

One other wish concerns the payment modules. I noticed that neither with Paypal not Stripe payments I there is any information on which order the payment was for.

I looked in my archive and I found some links. No idea whether they still are available and cost the same. http://addons.prestashop.com/en/front-office-features-prestashop-modules/2942-multi-dimensional-products.html 299 euro http://addons.prestashop.com/en/front-office-features-prestashop-modules/5628-product-properties-extension-sell-by-weight-lengthetc.html 199 euro http://addons.prestashop.com/en/front-office-features-prestashop-modules/18794-linear-meter-sell.html 129,99 http://psandmore.com/ 199 euro PS&More extension for PrestaShop https://www.prestashop.com/forums/topic/93968-change-order-quantity-to-a-decimal-value/page-3 A do-it-yourself method explained on the forum.

There are several modules for this. However, this is tricky functionality. I remember seeing how it was implemented in one of those modules. It added a new entry to the database (if I remember well a product) for every visitor - even if he didn't buy the product but just visited the page. After some time this resulted in a very bloated database. Of course a more mature implementation would work a bit like Attribute Wizard Pro: each order would have its own entry in the ps_product_attribute table, those entries would have the right price and the only attribute they would refer to was an empty string. If you added the product to the cart the length or weight would be stored in some extra field in the ps_cart_product table. When the order was completed the length/weight would be part of the product name so that the ps_order_detail wouldn't have to be changed.

My wishes: - An option to start an attribute combination with “select a” instead of a default value. I know this is a template job... - Option to automatically hide categories without products or subcategories with products. You have now modules that do such a thing. But the problem is that while they disable you have to re-enable yourself. - Option to disable combinations. - Auto-save for customizations - Option to include attachments in messages to customers - And finally the big fish: a solution for the combination problems. There are several situations where the Prestashop combination structure gives problems: - with too many combinations everything becomes slow - some attributes don't influence stock - some attributes have their own stock The solution that seems the most feasible to me at the moment is the following: - you need an additional table. Let's call it product-addons. - a product-addon can be either a product or an attribute. If you need stock keeping you use a product. A product can be set to be used in this function only. - the attribute table is expanded with a weight and a price field - an addon product can have attribute combinations. If there is more than one attribute the combinations will be merged into a single select menu ("carpet size:large; color:red"). If an addon product has product-addons itself they will be ignored. - addon products without combinations and single value attribute groups will be displayed as checkboxes. - I hope there is some possibility to insert those extra fields with hooks in templates that don't support them. - the category_product table will need an extra field for the product-addons. In the order_detail table the information can be part of the name field.

Thanks. I see that you allow settings per feature and you have also added a flag for custom values. Nice to see extra options compared to Prestashop. But I am I am not yet sure how easy it will be to implement for me.

Is there some flag in the database that indicates that multifeature? I would like to support it in Prestools like I do it for PS 1.7.3+. I assume other people building for Thirty Bees will face the same question.

I had a look at it. I created an account; logged out and tried to login again. I couldn't login again but I always got the same error - no matter whether the password was right or not. My gut feeling is that it could have something to do with groups.

What kind of errors do you have? Many errors are related to errors in the database when due to timeout there are some inconsistencies. They can easily be solved.

I tested Prestools in an upgraded TB 1.2 shop but I didn't see any error messages. I just uploaded a new version of Prestools. But I doubt that it will solve your problems as I don't understand them very well. Both line numbers that you mention are VAT related. My guess would be that there is something wrong with one of the tax tables. But it is hard to find out what without more information. If you want you can pm me.

It is in the paid functions of Prestools.

Did you: - empty the cache - regenerate .htaccess ???

When someone wants to build a module from Prestools product-edit I would be happy to cooperate. The most popular mass edit module on Prestashop Addons (https://addons.prestashop.com/en/fast-mass-updates/19965-bulk-mass-editing-products.html) looks like it took quite a lot of inspiration from Prestools. If such a module was made both for Thirty Bees and Prestashop it could pay for itself. As I see it mass edit and cronjobs are areas that have a broad appeal and could help TB too. One of the latest additions to Prestools was image edit that allows you to add images by drag and drop. You need to generate thumbnails afterwards as otherwise it would take too much time. However, for Prestashop 1.7 that is not necessary as it generates its thumbnails on the fly. It might be a good things to have such a thing in Thirty Bees too. Also for mass import by csv. Many of the latest additions to Prestools concern maintainability: integrity checks and cleanup procedures. My main inspiration was that I had to deal with some old shops with quite a lot of decay. As I see it, such old shops should play some role in the discussion about stability.

I am glad there is a solution for the business side of Thirty Bees. Good to see that people want to help. As for the future I would like to give the participants the following considerations/ideas: - start with the easy stuff that can make TB more popular. Migration modules from Prestashop 1.7 and WooCommerce are easy targets - as is support for PHP 8. Note that the next major version of Prestashop will be 1.8/8.0 and if they handle it as badly as the upgrade to 1.7 Thirty Bees could once again become a desirable alternative. Functionally PS 1.7 is hardly different from 1.6 and TB. - starting with the easy stuff will give you time to work out ideas for further development. - I would love to see TB once again starting to use version numbers. - As Prestashop told it, one of the reasons they didn't go forward with ASM was that every webshop company they talked to wanted something different. There may be no easy solutions here.

Those backoffice images are stored under the /img/tmp directory. And they are generated independently from the image formats in Preferences. So maybe there is some issue with the rights for this directory.

Settings->Products