Jump to content
thirty bees forum

Recommended Posts

Posted
  On 7/19/2021 at 7:12 PM, Smile said:

We expect in 2-4 weeks from now. Sorry it sounds wired but I could not find the php issue for the 1.3 sprint in Jira 😉 But if I am correct 1.3.0 will support 7.4.... Don't nail me down if I am wrong 😉

Expand  

Regarding PHP compatibility: 1.3.0 will still be supported on PHP5.6 ... PHP7.4

There is an ongoing effort to make it work on PHP8. This is not a small feat because PHP8 introduced standard class 'Attribute' that clashes with thirty bees core class. To fix it we need to rename our class, respective move it to different namespace (in core and all native modules). While this is quite simple to do, it of course introduces compatibility issues with any third party modules. To overcome this issue, thirty bees will contain mechanism that will parse and 'patch' third party modules PHP files. When you install new module, it's php files will be processed anda all references to Attribute class will be adjusted. For this we will use third party library. Unfortunately that lib does not support PHP5.6, which is one of the reasons why we are deprecating PHP5.6 and will not support it in the future.

At this moment there is still no need to actually remove support for PHP5.6, but once we integrate the support for PHP8 to mainline, we will be forced to do it. 

  • Like 7
  • Thanks 1
  • 4 weeks later...
  • 3 weeks later...
Posted
  On 8/12/2021 at 1:22 PM, Smile said:

Quick update. We expect version 1.3 in the first or second week of september.

Expand  

Great to know that, let's keep the good work flow !

For infos, I still use TB everyday mostly on b2b websites 🙂, some are still on 1.1.0 version and works perfectly.

  • Like 1
  • 3 weeks later...
Posted

Almost there but we had a little bit programing hours this week then expected. So stay tuned! Its always dangerous to mention a date 😉

  • Like 4
Posted
  On 9/18/2021 at 10:58 AM, Smile said:

Almost there but we had a little bit programing hours this week then expected. So stay tuned! Its always dangerous to mention a date 😉

Expand  

I don't think it's a problem for you to mention a date if you just remember to inform any delays or changes. It's the silence that makes people suspicious and wondering.

We are looking forward to the next release. Thanks for the info.

  • Like 2
  • 5 months later...
Posted

For me it works very nice, prejudiced a little ðŸ˜‰ 

No strange things really, just some nice new things I was waiting quite some time for.

  • Thanks 1
Posted
  On 2/21/2022 at 1:36 PM, wakabayashi said:

Who of you is already using the 1.3 version? How does it work out for you? 🙂

Expand  

I use it. I haven't noticed newly introduced bugs at all. A few are still lingering from previous versions. I've submitted to github. It works pretty well.

  • Thanks 1
Posted (edited)
  On 2/21/2022 at 1:36 PM, wakabayashi said:

Who of you is already using the 1.3 version? How does it work out for you? 🙂

Expand  

I was on 1.3, no issues.  I updated to bleeding edge (1.4), a week ago or so, and have had no issue that I'm aware of.

Edited by SLiCK_303
  • Thanks 1
Posted

check if you have any database upgrades you need to apply.

also try to do hard refresh (ctrl+f5), maybe some javascript file has been updated.

Screenshot from 2022-02-26 09-50-28.png

Posted

Its directly related to the new option  - Edit specific prices.

If you have a product with specific price and you change the value of discount in specific price, than saving works, otherwise it does not work.

I tested it in my shop just now on various products with and without specific price.

I'm sure this will be fixed very soon.

  • Thanks 1
Posted (edited)

Its related with line 3122-3123 in AdminProductsController.php

if (($price == -1) && ($reduction == 0)) {
 $this->errors[] = Tools::displayError('No reduction value has been submitted');

If reduction is not newly set or changed within current product editing/saving the error comes up.
Until fix you can outcomment line 3123 so you will be able to at least save the products.

Edited by toplakd
  • Like 1
  • Thanks 1
Posted
  On 2/26/2022 at 8:20 AM, toplakd said:

Its related with line 3122-3123 in AdminProductsController.php

if (($price == -1) && ($reduction == 0)) {
 $this->errors[] = Tools::displayError('No reduction value has been submitted');

If reduction is not newly set or changed within current product editing/saving the error comes up.
Until fix you can outcomment line 3123 so you will be able to at least save the products.

Expand  

Appreciate the clarification

Posted
  On 2/26/2022 at 8:20 AM, toplakd said:

Its related with line 3122-3123 in AdminProductsController.php

if (($price == -1) && ($reduction == 0)) {
 $this->errors[] = Tools::displayError('No reduction value has been submitted');

If reduction is not newly set or changed within current product editing/saving the error comes up.
Until fix you can outcomment line 3123 so you will be able to at least save the products.

Expand  

This is fixed now, please update to the latest bleeding edge

  • Like 1
  • Thanks 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...