CK MacLeod

On the site I haven’t rolled back yet:

1. Most of admin other than for the processes noted works fine.

2. wp-admin files for update-core.php, customize.php, and theme-install.php are all present and accounted for.

3. Not sure which log file you’re referring to.

Thanks for your interest.

Note that I haven’t worked on or updated this plugin in several years. I also don’t recall ever looking at Jetpack’s related posts plugin, and I don’t know what you’re using for the sidebar.

I might be able to take a quick look at these issues next week/month, but would need WordPress credentials and possibly other permissions. If it requires more than a simple adjustment to the plugin catering to your site specifically, then we might have to discuss it as a development job, if you’re interested.

• This reply was modified 2 years, 11 months ago by CK MacLeod.

Seems a very odd choice for Twenty Twenty Two not to include easier access to the good old Customizer – since 1), at least as far as I could discover, there’s no simple way to override certain theme defaults, and 2) it seems a major step backward in terms of usability to have to go back to editing a text file, whether style.css or theme.json.

In my case, I simply wanted to get rid of the default padding that affects the entire site via .wp-site-blocks, and trying to zero it out via Global Styles had no effect.

I’m guessing there are already plugins available, or soon-to-be-available, for getting the customizer back for block themes – like the Classic Editor plugins were, and by many people still are, preferred when Gutenberg was rolled out. Maybe in the short term can just add/restore the customize.php link to the admin bar.

Checking the code a little more, the js script for producing num_of_random_chars is producing “0” as in Form Data (in developer console):

action: coupon_bulker_ajax_endpoint
fn: bulk_coupon_generate
coupon_id: 188854
code_prefix: bulker
num_of_coupons: 1
num_of_random_chars: 0

An alternative to the hack described above could be in coupon-bulker-admin.js at line 39 or line 48.

The alternative I’m currently using (since we just want 8 characters regardless), is in class-coupon-bulker-admin.php, lines 254-5:

    //$num_of_random_chars = intval( $_POST['num_of_random_chars']);
    $num_of_random_chars = 8 ; 

Not sure what happened here, it seems to be some new issue – maybe with WooCommerce update? – that has reduced the number of random characters to 1.

Downloads are also broken, incidentally: Attempts to download new coupons still show the last downloaded/exported group.

(wondering what happened to prior comments on this thread…)

@looknear That’s nice you’ve added that functionality to your new plugin, and nice that you can delete by prefix, too. Good work, even if the interface, understandably, has some rough edges at this stage.

I won’t discuss your plugin further here, since this is a review thread for someone else’s plugin, but I’ll note one additional limitation for both of you authors: Neither plugin currently looks for and copies coupon meta data supplied by custom functions or other plugins (ACF, Coupon Categories and Tags…). There are workarounds, and I wouldn’t call it a major limitation, but a slicker, maybe pro-level version would 1) expand custom-prefixing and possible other customization at code creation, 2) copy and expose custom meta data to whatever extent is practical, and 3) absorb and improve upon Coupon Categories and Tags or supply alternative organization features.

• This reply was modified 4 years, 1 month ago by CK MacLeod.

The message used as the title of this thread, upon an attempt to load the generated PDF, in Chrome. As a side note, these occasional but repeatable failures occur across different browsers, although some browsers produce different failures than others: On Chrome, nothing loads at all, for example, other than the Acrobat background and the above-referenced message. Firefox manages to load some of the document header, and also offers some other options (that don’t do any good). Meanwhile, as noted, many similar or even nearly identical documents (or documents based on near-identical inputs) load as desired.

Just to give you some background:

I have two different documents, originally consisting of an HTML table or set of tables, with a few headings and a paragraph or two, with dynamic content derived from user and WooCommerce order and product data.

I don’t know how much more detail would be useful for you. I’ll just say here that the document HTML is returned via ob_get_clean() in a shortcode function. Originally, I ran some logic after the original ob_start(). As errors popped up, I found that it helped to move all calculations, no matter how simple – many were of the general type echo $response ? $response : $no_response – outside of the object declaration.

In other words, I am now deploying no PHP more complicated than echo $variable between ob_start() and ob_get_clean(). I still got another load failure this week. This time, I was able to clear the error by simplifying the document even further, converting two tables to just one.

I wonder if there isn’t some memory- or capacity-related bottleneck interfering with PDF generation, though I’ve also tried increasing PHP memory limits without effect. However, I don’t understand that part of the process very well.

If you want to look into this further, I can give you access and show you the PHP I’m using. I don’t really expect you to do that, though – I was really just hoping for some clues on where to look next.

I periodically encounter this error: The application works well most of the time, then fails on a certain instance type.

I have previously cured the error by simplifying the code used to produce the content of the eventual document. I’m kind of at the end of that process now, and still getting the error. I can provide more details/access if you are interested in investigating and helping out further.

The only information in error logs that hint at an mpdf problem are on the level of a “notice” referencing a deprecated “each” function:

[27-Jan-2021 21:03:17 UTC] PHP Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/duffym5/public_html/pianorentals.com/wp-content/plugins/wp-mpdf/mpdf/mpdf.php on line 10894

I tried switching to an earlier version of PHP (from 7.3 to 7.0), and the deprecation warning went away, but the failure to load error didn’t.

@rynald0s

If you scan WooCommerce Support threads for the past few days, you will see that this is a very bad bug encountered by multiple users, that currently is being crowdsourced for hacks. Y’all really should escalate and fix pronto, as it critically compromises site operations.

https://www.ads-software.com/support/topic/cannot-update-products-since-last-update/
https://www.ads-software.com/support/topic/product-save-times-out-to-502-error/
https://www.ads-software.com/support/topic/issues-adding-product-critical-error/

at Github https://github.com/woocommerce/woocommerce-admin/issues/6168

@gabrielfuentes

If you scan the threads for the past few days, you will see that this is a very bad bug encountered by multiple users, that currently is being crowdsourced for hacks. Y’all really should escalate and fix pronto, as it critically compromises site operations.

https://www.ads-software.com/support/topic/cannot-update-products-since-last-update/
https://www.ads-software.com/support/topic/product-save-times-out-to-502-error/
https://www.ads-software.com/support/topic/issues-adding-product-critical-error/

at Github https://github.com/woocommerce/woocommerce-admin/issues/6168

Thanks @geoffreycrm It could be that my hack was necessary only due to peculiarities of the installations I was working on, possibly including previous attempts to solve by direct db editing (somewhat as was suggested earlier on this thread).

I’m not sure I’ll ever learn the answer, as frankly I can’t spend much more time on this crisis right now. Either way, one might hope that action soon by Automattic devs will obviate the necessity of adding anything to the site, and let us remove emergency additions of all types. Maybe things’ll be clear when they solve it.

@tracyandersonmd I see you got it fixed. I’ll emphasize that in normal circumstances I’d never hack WooCommerce core files, but in this case I strongly suspect a WooCommerce patch will be forthcoming soon, and it’ll be better just to have the hack overwritten. If the issue is handled without overwriting RemoteInboxNotificationsEngine.php, then the hack should be removed.

If someone else wants to write a plugin that combines the filter and the hack in the form of “remove_action” actions, that would be better than what I’ve done, but I honestly expect this all to be taken care of literally any moment, considering the gravity of the bug, though maybe I’m too trusting…

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

@geoffreycrm

Did the filter solve the plugin updating for you, too? I had to address that issue separately (with a hack pending action on this bug from WooCommerce).

see https://www.ads-software.com/support/topic/product-save-times-out-to-502-error/#post-13947711

Thought I should amend while awaiting action from WooCommerce/Automattic:

At a vanilla site, the simpler code + hack solved both identified issues. At a much more complex site, I needed to use a version of the more complicated filter. So the “complete” interim fix, looked like this:

//TEMPORARY BUGFIX FOR WOOCOMMERCE "PHONING HOME" - REMOVE AFTER WOOC FIXES
add_filter('woocommerce_admin_features', 'pk_woocommerce_admin_features');
function pk_woocommerce_admin_features($features) {

	if(($key = array_search('remote-inbox-notifications', $features)) !== false) {
		unset($features[$key]);
	}
        // return other features if any (?)
	return $features; 
}

To restore normal plugin-related update/activation actions, comment out lines 69 and 70 of woocommerce/packages/src/RemoteInboxNotifications/RemoteInboxNotificationsEngine.php

Like so:

//HACK Interrupt "phoning home" until WooCommerce is patched
		//add_action( 'activated_plugin', array( __CLASS__, 'run' ) );
		//add_action( 'deactivated_plugin', array( __CLASS__, 'run_on_deactivated_plugin' ), 10, 1 );