sprucelydesigned

PHP Fatal error: Uncaught Error: Failed opening required '/srv/htdocs/wp-content/plugins/miniorange-oauth-20-server//admin\helper\constants\class-miniorange-oauth-20-server-oauth-constants.php' (include_path='/:.') in /srv/htdocs/wp-content/plugins/miniorange-oauth-20-server/admin/helper/class-miniorange-oauth-20-server-customer.php:15 Stack trace: #0 /srv/htdocs/wp-content/plugins/miniorange-oauth-20-server/admin/class-miniorange-oauth-20-server-save-settings.php(27): require_once() #1 /srv/htdocs/wp-content/plugins/miniorange-oauth-20-server/admin/class-miniorange-oauth-20-server-admin.php(195): Miniorange_Oauth_20_Server_Save_Settings->__construct() #2 /wordpress/core/6.4.3/wp-includes/class-wp-hook.php(324): Miniorange_Oauth_20_Server_Admin->mo_oauth_server_admin_init_save_settings('') #3 /wordpress/core/6.4.3/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #4 /wordpress/core/6.4.3/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #5 /wordpress/core/6.4.3/wp-admin/admin.php(175): do_action('admin_init') #6 /wordpress/core/6.4.3/wp-admin/plugins.php(10): require_once('/wordpress/core...') #7 {main} thrown in /srv/htdocs/wp-content/plugins/miniorange-oauth-20-server/admin/helper/class-miniorange-oauth-20-server-customer.php on line 15

Fixed the first error by replacing the back slashes with forward slashes. Then the error above also showed the same issue. Replacing slashes fixes the error.

Thank you for the quick update @softound

I’ve temporarily patched my copy of your plugin with the following fix to address this (updated after my previous post).

In the file /wp-content/plugins/woo-stripe-payment/includes/admin/meta-boxes/views/html-order-pay.php
I updated the <p> html at the top of the file to this:

<p class="form-field form-field-wide">
	<?php
		$order_post_status = get_post_status( $order->get_id() );
		$disabled_attr     = '';
		$tooltip           = __( 'Admins can process customer orders over the phone using this functionality.', 'woo-stripe-payment' );

	if ( 'auto-draft' === $order_post_status ) {
		$disabled_attr = 'disabled="disabled"';
		$tooltip       = __( 'Please create the order before processing payment.', 'woo-stripe-payment' );
	}
	?>
	<button class="button button-secondary wc-stripe-pay-order" <?php echo $disabled_attr; ?>>
		<?php esc_html_e( 'Pay for Order', 'woo-stripe-payment' ); ?>
	</button>
	<?php echo wc_help_tip( $tooltip ); ?>
</p>

That effectively accomplishes what I think is the best solution of disabling the button and providing a tool tip text to explain why:

Maybe you all can add this bug-fix/feature in a future release?

I think that’s an excellent solution! My preference would be for the button to be visible but disabled and the tool-tip to explain to create the order first to enable the Pay for order button.

• This reply was modified 10 months, 2 weeks ago by sprucelydesigned. Reason: Removed proposed solution that didn't properly work

I understand that. But I fail to see how this notice complies with #11 of the plugin guidelines: https://developer.www.ads-software.com/plugins/wordpress-org/detailed-plugin-guidelines/#11-plugins-should-not-hijack-the-admin-dashboard

There are plenty of free plugins that I’ve happily given a donation because it’s such a well maintained plugin. But those earned those based on the quality of the plugin itself. Maybe you should try to monetize this plugin on its own merits rather than using it to shill another product.

@bhshravankumar I’m happy to provide a test site if you need. I’ll open a support ticket on the cartflows website and provide details there (I have a Cartflows Pro license). Ticket ID 236979.

I’m not sure I follow. The browser isn’t the issue. The PDF that is generated is the issue. Happens when printing outside the browser.

The specific add-on that causes the conflict is “WP Sheet Editor – Taxonomy Terms Pro” Version 1.6.0

I also tested this on a completely different Mac and it even displays improperly in Preview and prints improperly as well.

Same issue is occurring with WooCommerce Shipping plugin, so it’s something that’s in a shared library between these two plugins.

Just to note, there’s another support thread for the same issue already: https://www.ads-software.com/support/topic/logo-not-scaling/

1. Printing via Preview gives the erroneous layout.
2. If we open the PDF with Illustrator and print, it works ok.

Opened my own thread. You can remove these if you like, @tobifjellner

I have this same issue. Example printed invoice: https://ibb.co/47tWgvJ

Settings: https://ibb.co/NYrjm6m

This only happens when printing from a Mac. PC prints just fine. Also, other PDFs print fine from the same Mac, it’s just PDFs from WooCommerce. Same issue occurring with the WooCommerce Shipping plugin labels. So it’s something shared in those libraries.

• This reply was modified 2 years, 3 months ago by sprucelydesigned. Reason: added detail on machine in use

Same issue here on a few sites. Here’s the PHP error:

"PHP message: PHP Fatal error: Uncaught Exception: You cannot add that amount of "Lady Dye Yarns Winterpalooza Box"; to the cart because there is not enough stock (0 remaining). in /public/wp-content/plugins/woocommerce-square/includes/Gateway/Digital_Wallet.php:284
Stack trace:
#0 /public/wp-content/plugins/woocommerce-square/includes/Gateway/Digital_Wallet.php(233): WooCommerce\Square\Gateway\Digital_Wallet->get_product_payment_request(11136)
#1 /public/wp-content/plugins/woocommerce-square/includes/Gateway/Digital_Wallet.php(202): WooCommerce\Square\Gateway\Digital_Wallet->get_payment_request_for_context('product')
#2 /public/wp-includes/class-wp-hook.php(287): WooCommerce\Square\Gateway\Digital_Wallet->enqueue_scripts('')
#3 /public/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
#4 /public/wp-includes/plugin.php(484): WP_Hook->do_action(Array)
#" while reading response header from upstream, client: ---, server: ---, request: "GET /product/lady-dye-yarns-winterpalooza-box/ HTTP/1.0", host: "ladydyeyarns.com", referrer: "https://ladydyeyarns.com/product-category/limited-products/"

I chatted in with WooCommerce Support who opened a bug report here: https://github.com/woocommerce/woocommerce-gateway-paypal-express-checkout/issues/527

I’ve found disabling Smart Payment Buttons? will restore the ability for customers to checkout.

@jeffmatson done. Appreciate the update and your time. Hope you find a good method for monetization. As for environments, I saw the issue on all my sites on Siteground using their standard stack of caching: page, dynamic, memcached. WP 4.9.8, php 7.2, on either Flatsome or Divi themes.