stewarthowell

@mane4 Ooh that’s interesting. Thanks for the tip, I’ll give it a try.

@mane4 Nope never did solve it. Had to walk away from Qubely leaving behind a year’s worth of page updates. Gutted.

Trying to do most things in Kadence now. https://en-au.www.ads-software.com/plugins/kadence-blocks/

It’s not as comprehensive as Qubely so also using Ultimate https://en-au.www.ads-software.com/plugins/ultimate-addons-for-gutenberg/ and Advanced https://en-au.www.ads-software.com/plugins/advanced-gutenberg/

Please let me know if you solve it as I still have dozens of pages with Qubely blocks which still render ok as long I don’t need to publish an update.

No worries Ross.
Thanks for getting back to me.
-Stew

@bondie Jack in terms of looking for commonalities… what is your hosting environment? I’m on AWS Amazon Linux 2. VPC in Sydney. MariaDB. Hmmm maybe drop me an email and I can share more details with you directly. [email protected]

-Stew

Have you had any luck Jack @bondie ?
I’m getting nowhere fast with Qubely support.

– – –
4/9 Support: Please provide your wordpress login url, admin user and password
4/9 Me: I create a ‘Support’ admin account on dev environment and provide it.
5/9 Support: almost showing the same interface in the front end loading the css too but has some issues in some certain parts. Can you please show me a page where its not rendered at all?
10/9 Me: I create a new page with only 3 qubeley blocks on it, demonstrating the problem. Process was recorded and video link provided. Same as initial post.
10/9 Support: Can we have admin credentials
11/9 Me: Here they are again, they haven’t changed.
12/9 Support: i require your permission to have the authority to deactivate existing activated plugin
15/9 Me: Yes I grant you permission to do anything you like. It is a dev environment and you have full admin permissions.
16/9 Support: Your php is 7.2.33 please upgrade to 7.4 or more.
17/9 Me: Done. php is now 7.4.9. All plugins deleted. My child theme deactivated.
Active theme changed from TwentyThirteen to TwentyTwenty. The problem is still happening.
18/9 Support: Increase your php config values to these.
memory_limit = 256M
upload_max_filesize = 100M
post_max_size = 38M
max_execution_time = 900
max_input_time = 900
24/9 Me: Done. The problem is still happening.

• This reply was modified 4 years, 2 months ago by stewarthowell.
• This reply was modified 4 years, 2 months ago by stewarthowell.

I haven’t been able to get past first-level support at Themeum, so no answers from them yet Jack.

First they ask for admin credentials, which I provide. Then they say “the page edited with Qubely is almost showing the same interface in the front end loading the css too but has some issues in some certain parts. Can you please show me a page where its not rendered at all?”. So I create a new page with only Qubely blocks https://dev.gleneirafc.com.au/test7 and send the video. Now they ask for admin credentials again. Meh.

I wonder what our sites have in common that might be to blame? Are you on a theme called TwentyThirteen maybe? I doubt it’s caused by a plugin conflict because on my dev environment I deactivated, then deleted, every other plugin except Qubely and the fault still presents itself.

Thanks for having a look Sekandar. As suggested, I
a) Changed the save location of the Qubely CSS
b) Deactivated other plugins.
Still no good. I’ll email support.

Session video: https://www.awesomescreenshot.com/video/819491?key=77ec894c30e6899677113bb586307877

-Stew

• This reply was modified 4 years, 2 months ago by stewarthowell.

Sorry please ignore. I was looking at the European version of plugin.

The plugin version for the rest of the world is:
https://www.ads-software.com/support/plugin/afterpay-gateway-for-woocommerce/

It would be less confusing if they names weren’t almost identical.

Thanks for looking into this Pablo. My WooCommerce version is Version 3.8.0

I updated to Booster Plus for WooCommerce to 4.6.1 and the error came back. Then I manually added your 3 new lines as described (under the line starting with $total=) and the error stops happening.

-Stew

PS Sorry I don’t know why the init_template_class() function isn’t being invoked earlier

Problem still exists in 4.6.0

I fixed it by adding the following line into a file in the plugin.
require_once( 'shipping/class-wc-shipping-wcj-custom.php' );

The file to edit is…
wp-content/plugins/booster-plus-for-woocommerce/includes/class-wcj-shipping.php

And the place to add it in is just after line 63. In other words, just above the line starting with…
$total_number =

• This reply was modified 5 years ago by stewarthowell.

This issue still exists in 4.5.1

Not sure about the plugin you mention agusbagus, but this works with my Booster-for-Woocommerce plug-in

Booster settings > email and miscs > export
Export Module Options > Enable
Export Orders Options >
Field #1 > Enabled
title > Player Name
type > Order Shortcode
value > [wcj_order_checkout_field field_id=”order_wcj_checkout_field_1″]