30knees

I got this reply: It only shows when debugging is enabled (which it shouldn't be when the website is fully live). It's just a bug in Prestashops HelperForm class which may or may not get fixed due to it having no negative effect other than showing a notice (notices generally pose no issue). I like the "may or may not get fixed". :)

OK, thanks. So to make sure I understood: Having values under different attributes (=attribute categories) means the system wants to make these into combinations. If I do not want that, they need to be values under the same attribute. Then I will change my implementation.

Sounded odd to me, too, but I don't have any arguments to give him :) It also only shows up with his module.

When I visit a certain third party module's configuration page I get the following error: Notice on line 988 in file /cache/smarty/compile/e8/17/8f/e8178f4c9387e84f401348d28910fcfff4f23a17.file.form.tpl.php [8] Undefined index: name The developer said it is unrelated to their module and is caused by debugging being enabled in the "defines.php" file. I don't know whether this is a ps/tb incompatibility issue or something else, but I'm posting it here in case it's relevant for someone or something.

I have two attribute categories, one "Pieces" and one "Weight". For a certain product that is available both as poweder and as capsules, I would like to have one attribute with "100 capsules" and one with "100g". This means each attribute would be from a different attribute category. The customer can select whether they'd like to buy the product as capsules or as powder. 100 capsules is the default attribute. This means it's automatically pre-selected. If a customer clicks on 100g, both 100 capsules and 100g are selected and I get the message: "This combination does not exist for this product. Please select another combination." But these two shouldn't be combination attributes, they should be individually selectable. Am I doing something wrong or is this just how tb works? If so, does that mean I would need to have the two attributes in one category and not spread across two categories?

@wakabayashi OK, then I misunderstood you. I thought you meant editing by writing in a payment method. Yes, I'll look into editing that, too.

@wakabayashi Couldn't one define such payment methods so they are "real" methods and then one could edit the payment method by selecting from those are are enabled?

@30knees said in How to edit the carrier of an existing order?: How can I edit the carrier of an existing order? I don't see how/where I can, but I find it hard to imagine that this isn't possible. We might be able to get this into the core. What would we need to edit beyond Carrier and Carrier fee? Please keep it simple, nothing fancy as of now.

Your code worked nicely, too.

The rating is weird: Only 5 votes and supposedly over 90% of customers would recommend the product. No idea how to interpret that and whether the rating is reliable. But I'll take it into consideration. Thanks for pointing out!

Hi, I'm looking at http://www.joethemes.com/prestashop-affiliate-program-module/ Does anyone have experience with it?

@mdekker How do I execute the query you mention? I get a bunch of the following error messages when I visit its configure page: /vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(157) : eval()'d code [8] Undefined index: id_aeuc_email I updated to 3.1.1 and it shows 3.1.1.

Hi, I updated AEUC to v 3.1.0. When I click on "Configure", I get the following error: Fatal error: Class 'AdvancedEUComplianceModule\AeucCMSRoleEmailEntity' not found in /modules/advancedeucompliance/advancedeucompliance.php on line 1851 [PrestaShop] Fatal error in module file :/modules/advancedeucompliance/advancedeucompliance.php: Class 'AdvancedEUComplianceModule\AeucCMSRoleEmailEntity' not found

It looks like it works now after the module update. Super job!

I'm not sure if this is what you mean. I get the following: product.js:177 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. jquery-1.11.0.min.js:4 [Deprecation] Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/. [Violation] Added synchronous DOM mutation listener to a 'DOMNodeInserted' event. Consider using MutationObserver to make the page more responsive.

This might be the same as https://forum.thirtybees.com/topic/520/loyalty-points-available-in-one-language-but-not-the-other/

@vzex Were you able to fix it for Panda, by the way? If so, how did you fix it? :)

Communities and projects like this live and die because of their culture. I don't know what's been going on in the background and who started what, but @Traumflug's reply to @Occam in the thread was hostile and without any value at all. I hope these two important members of our community are able to make up and work together again to improve tb.

@pedalman It's the Panda theme for me. I'll give your solution a try, thanks!

Edited: Post didn't belong in this thread.

I have to agree with RaptorX's main point: ``` You guys keep presenting me with workarounds and tools that while being great is not the same as being done in the main software as it should be. If TB doesnt have to rely on modules to do things that should be done natively this types of problms would be less common and quicker to resolve. ``` A shop should be as easy as possible. Maybe currently we'd break compatibility with PS 1.6, but eventually that is going to happen and then there is no real reason anymore why tb shouldn't adopt the best solutions other shops have developed.

@lesley I'll work on features and post here. I don't know that much about bugs.

@Occam is the one who knows what all the bugs are. There are eg: https://forum.thirtybees.com/topic/585/enabling-advanced-checkout-page-in-advanced-eu-compliance-hides-some-payment-methods and https://forum.thirtybees.com/topic/846/aeuc-error-thrown-on-index-php-controller-order and https://forum.thirtybees.com/topic/584/bug-in-eu-advanced-compliance-with-shipping-taxes

How about a crowdfunding of AEUC? I would support it. Any idea how much we would need?

@mockob You could try eg something like this https://www.leipzig.ihk.de/mediathek/Aufbau%20eines%20rechtssicheren%20Online-Shops.pdf with Google Translate.