fitwarrior

Nah, that’s not it… no attributes appeared to choose from… until this…

“Apparently now there are 2 methods to add attributes. The old way, a pipe | separated list at product level does not allow the plugin to detect the attribute.

You have to use the new way – add attributes first under “Attributes” in the main “Products” menu, THEN assign them at product page level.”

I got it to work. Great plugin! I opted for the paid version.

ps. your website screenshots could be updated — eg. location of where to turn on ajax

I got it. Apparently now there are 2 methods to add attributes. The old way, a pipe | separated list at product level does not allow the plugin to detect the attribute.

You have to use the new way – add attributes first under “Attributes” in the main “Products” menu, THEN assign them at product page level.

Update (or lack thereof) … I’m bac to getting goofy meta text like “_reduced_stock: 1” under each product line on pdf invoices.

Looks like another Booster update blew away my code hack to fix this.

Hey Booster, some help here?

Ok, might have it solved…

This seems to work:

@ini_set( 'log_errors', 'On' );
@ini_set( 'display_errors', 'Off' );
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

This allows me to allows me to log errors (in debug.log) without showing them on screen
AND allows pdf invoices to print ??

That is,

You’re suggesting to show errors only in log file:
define('WP_DEBUG_LOG', true);

instead of show errors on screen:
define('WP_DEBUG_DISPLAY', true);

But both of these require:
define('WP_DEBUG', true);

… and it’s this last line, when active in wp-config.php, that throws an error when trying to print pdf.

The problem is the pdf won’t print when ANY type of debugging is in place, even just error logging to /wp-content/debug.log

Booster team,

Would you please fix this permanently when you have a moment? That is, allow the pdf to print even with debugging on (with a “define(‘WP_DEBUG, true);” statement in wp-config.php).

Most of us prefer to keep error logging turned on, for obvious reasons, but then we can’t print invoices ??

N/m solved it…

My issue is the site is under construction so I have debugging on in wp-config.php:

//define('WP_DEBUG', true);
define('WP_DEBUG_DISPLAY', true);
define('WP_DEBUG_LOG', true);

Commenting out the first line, as shown above. allows PDF invoices to print.

While under construction, WP_DEBUG is showing a handful of minor errors/warnings about certain deprecated functions from other code in the site but nothing major so I’m guessing just any old warning or error is mucking up the output and the pdf creation process and making the pdf unable to render correctly.

Booster team… please close my support ticket on your site… there’s no way it seems for me to do it.

Also, your plugin rocks. Rebuilding our website I’ve been able to elimiate countless other (mostly poor quality) plugins for your very organized and functional code! Love you guys! Best money I’ve ever spent!

Same here.

Latest paid version. Latest WP and Woo.

Chrome error: “Error: failed to load pdf document”. Other browsers show slightly different wording but same error.

I need to launch this ecom site in a few days… anything you can do it appreciated.

Nevermind, looks like it updated… just needed to wait 30 hours. Please investigate.

Also, your Submit Ticket form is not working on your trackship website… returns a Wordfence error.

The functionality you provide with AST plugin and your Trackship service is good… customers like it ok. It’s just good enough for the price of $60/mo. But no more than that, and it seems I’m sending you one problem or another on a frequent basis.

Please devote more attention to this.

https://photos.app.goo.gl/2QWxmdh4UPD1Fp787

Besides, you’re the same company.

How are you certain it’s a TrackShip issue and not an issue with your plugin?

Good. It appears fixed.

New issue in today’s error logs:

[CRITICAL] : Uncaught Error: Cannot use object of type WP_Error as array in /home/##########/public_html/wp-content/plugins/woo-advanced-shipment-tracking/includes/class-wc-advanced-shipment-tracking-front.php:213
Stack trace:
#0 /home/##########/public_html/wp-includes/shortcodes.php(325): WC_Advanced_Shipment_Tracking_Front->woo_track_order_function('', '', 'wcast-track-ord...')
#1 [internal function]: do_shortcode_tag(Array)
#2 /home/##########/public_html/wp-includes/shortcodes.php(199): preg_replace_callback('/\\[(\\[?)(wcast\\...', 'do_shortcode_ta...', '[wcast-track-or...')
#3 /home/##########/public_html/wp-includes/class-wp-hook.php(288): do_shortcode('[wcast-track-or...')
#4 /home/sarmtech/public_html/wp-includes/plugin.php(206): WP_Hook->apply_filters('[wcast-track-or...', Array)
#5 /home/##########/public_html/wp-includes/post-template.php(253): apply_filters('the_content', '[wcast-track-or...')
#6 /home/##########/public_html/wp-content/themes/shopstudio/template-parts/content-page.php(19): the_content()

I don’t know how or if this is creating a functionality issue but it’s worrisome any time there’s a ‘crititcal’ error.

The latest version. My plugins always update automatically.

Is the issue fixed for new orders going forward, or can customers with multi-part shipments from, say, a month ago see a correct view in My Account > Orders?

I installed the update and looked at one of our multi-part shipment orders:

https://photos.app.goo.gl/cfevKW4DYFvtfviz9

The issue remains.