boyington

It works !

I disabled the “Also aggregate inline JS” and the ”
Optimize CSS Code” options and the cache size stopped increasing.

Thanks for your help !

Regards

Got a fatal error after upgrading to the 7.1.1 version ??

PHP Fatal error: require(): Failed opening required ‘/home/httpd/wordpress/public_html/wp-content/themes/enigma/customizer-pro/class-customize.php’ (include_path=’.:/usr/local/lib/php’) in /home/httpd/wordpress/public_html/wp-content/themes/enigma/functions.php on line 25

it seams the problem comes frome some case issue that can be solved by renaming the file:

wp-content/themes/enigma/js/carouFredSel-6.2.1/jquery.carouFredSel-6.2.1.js

in

wp-content/themes/enigma/js/carouFredSel-6.2.1/jquery.caroufredsel-6.2.1.js

Hi @boneyboy ,

there is no ‘[‘ in my-custom-css/my-custom-css.php on line 69 for the version 3.2 (but yes there is one in the 3.3 version)

So it seems you did not downgrade.

exactly the same for me with the 3.3 version:

PHP Parse error: syntax error, unexpected ‘private’ (T_PRIVATE) in /home/httpd/wordpress/public_html/wp-content/plugins/my-custom-css/pages/myphp/Edit.php on line 257

downgarding to 3.2 solved the problem.

thanks @tommcgee

Hi,

are you sure this problem is connected to the woobytes plugin ?

Regards

Hi,

Did you set the woocommerce order status to ‘completed’ ?

Hi,

I see where the trouble come from.

Let’s look at the cashback api doc:

currency: (string) currency of the purchase. Supported values: USD, EUR, RUR, GBYTE, BTC. If the purchase was paid in any other currency, you should convert its amount to any of the supported currencies except GBYTE.

That means that the api is waiting for a converted value of your GPB price.

I think we can add this needed automated conversion feature on the next release of the plugin…

Meanwhile, I am afraid you will have to use one of the supported currencies (USD, EUR, RUR, GBYTE, BTC), or you won’t benefit yet from the cashback program.

Regards

This seems to be a problem on cashback api server side.

Try again (setting order status to ‘pending’ and then back to ‘completed’) and if you still have this error, you can directly ask the cashback api main dev Tonych on slack.

Hi,

Did you try to just remove the default cipher list ?

You can do that on the settings page (‘SSL cipher list’ field).

Then you can check if it’s working by then resending the cashback api reques.
For that, just :

select your completed order
change its status from ‘completed’ to ‘pending’
change its status from ‘pending’ to ‘completed’

This will automatically send a new cashback api request and you will see the result on the order notes.

Hope this help !

Regards

• This reply was modified 6 years, 7 months ago by boyington.

Hi,

curl –ciphers ecdhe_ecdsa_aes_256_sha https://byte.money/new_purchase

There’s no universal cipher it depends on the SSL backend of both client and server.

You can check which are yours by doing from a shell prompt

curl https://www.howsmyssl.com/a/check

then test one of them against the cashback api

curl --ciphers TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA https://byte.money/new_purchase

…until it works.

Regards

Hi,

1) did you see that since the 1.1.0 version, you can choose Byteball Bytes, KBytes, MBytes or GBytes as possible main currency for your e-shop (in Woocommerce / Settings / Currency options) ?

2) The plugin will automatically send the payment request to the cashback api as soon as an order status is set to ‘completed’
If it did not work for you, can you tell the error message that was returned by the casback api ? (the error message should be added in the order notes)

Regards

Hi hodgigre,

The new 1.1.0 version of WooBytes plugin now automatically sends a notification email (with order details AND payment link) to customer as soon as the order is created (can be switched off on plugin settings page).

Regards

Hi hodgigre,

be advised that the new 1.1.0 version of WooBytes plugin now adds the possibility to set Byteball Bytes, KBytes, MBytes or GBytes as main currency of your e-shop.

Regards

Hi hodgigre,

In fact, no, the byteball payment address was never displayed on checkout page.

Thinking of your proposition, I a m not sure of the result. It will for sure add information to the checkout page and so make the page more complicated and for what use ?

Regards