Cross-posted from HP support forum.

HP’s LaserJet Pro P1102w printer drivers (download) fail to install on macOS 12.0.1 or later. Attempting to install them displays the error:

This update requires macOS 12.0 or earlier.

Timeline

• macOS 12.0.1 was released on October 25, 2021.
• HP’s drivers (5.1) were were released on October 27, 2021.
• Previous thread (“Hp printer driver for Macos Monterey 12.0.1 not available“) October 11, 2021. Support agent @Kumar0307 failed to escalate this to engineering and falsely suggested the driver would work with 12.0.1; it does not.
• macOS 12.1 was released on December 13, 2021.
• As of December 29, 2021, HP has not released a fix.

The problem is due to the Distribution script in the installer. It looks like this:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<installer-gui-script minSpecVersion="1">
<options hostArchitectures="x86_64"/>
<title>SU_TITLE</title>
<script/>
<installation-check script="InstallationCheck()"/>
<license file="License.rtf"/>
<choices-outline>
<line choice="manual"/>
</choices-outline>
<choice id="manual" title="SU_TITLE">
<pkg-ref id="HewlettPackardPrinterDrivers" auth="Root" packageIdentifier="com.apple.pkg.HewlettPackardPrinterDrivers">#HewlettPackardPrinterDrivers.pkg</pkg-ref>
</choice>
<script>
function InstallationCheck(prefix) {
if (system.compareVersions(system.version.ProductVersion, '12.0') &gt; 0) {
my.result.message = system.localizedStringWithFormat('ERROR_25CBFE41C7', '12.0');
my.result.type = 'Fatal';
return false;
}
return true;
}
</script>
<pkg-ref id="HewlettPackardPrinterDrivers" installKBytes="933742" version="10.6.0.1.1.1602826228"/>
</installer-gui-script>

The script is checking for 12.0 instead of 13.0.

The workaround is described in a macrumors thread: run these commands in Terminal:

curl -o ~/Downloads/hpdrivers.dmg&nbsp;<a href="https://updates.cdn-apple.com/2020/macos/001-41745-20201210-DBC9B46B-88B2-4032-87D9-449AF1D20804/HewlettPackardPrinterDrivers.dmg" target="_blank" rel="noreferrer noopener">https://updates.cdn-apple.com/2020/macos/001-41745-20201210-DBC9B46B-88B2-4032-87D9-449AF1D20804/Hew...</a>
hdiutil attach ~/Downloads/hpdrivers.dmg
pkgutil --expand /Volumes/HP_PrinterSupportManual/HewlettPackardPrinterDrivers.pkg ~/Downloads/hp-expand
hdiutil eject /Volumes/HP_PrinterSupportManual
sed -i '' 's/12.0/13.0/' ~/Downloads/hp-expand/Distribution
pkgutil --flatten ~/Downloads/hp-expand ~/Downloads/HP_Drivers_12.pkg
rm -R ~/Downloads/hp-expand

Then open the newly-created HP_Drivers_12.pkg and install it.

If you rename a WordPress theme, you will lose customizations (theme mods). They’re stored in wp_options based on the theme’s slug.

WP CLI makes it easy to quickly copy the theme options over:

wp> $new_slug = "my-new-theme-slug";
wp> $theme_slug = get_option( 'stylesheet' )
wp> $mods       = get_option( "theme_mods_$theme_slug" );
wp> update_option( "theme_mods_$new_slug", $mods );

Having recently spent some time with OpenStates data, I noticed the state government websites varied … a lot. Wanting to quantify this variation, I used the SSL Labs scanner, Lighthouse, and some Ruby scripts to compare the 50 states, DC and Puerto Rico’s legislature’s websites.

The table below covers usability (is the hostname flexible), security (does it allow or require HTTPS), server configuration (SSL Labs) and performance (Google Lighthouse).

							Lighthouse
state	URL	www	.gov	HTTPS Support	HTTP Upgrade	SSL Labs	Perf	AX	Best Practices	SEO
AK	akleg.gov		✔️		❌	C	56	74	73	69
AL	legislature.state.al.us	🚫 root	❌	❌	❌	—	15	76	60	75
AR	arkleg.state.ar.us	🚫 root	❌		✔️	B	65	94	87	84
AZ	azleg.gov		✔️		✔️	A	43	90	73	82
CA	assembly.ca.gov		✔️		✔️	B	31	92	60	80
CA	senate.ca.gov		✔️		✔️	B	30	68	80	91
CO	leg.colorado.gov		✔️		❌	A	29	93	80	90
CT	cga.ct.gov		✔️		✔️	B	22	89	67	92
DC	dccouncil.us		❌		✔️	A	64	81	73	77
DE	legis.delaware.gov		✔️		✔️	B	14	85	67	76
FL	flsenate.gov		✔️		✔️	B	44	88	87	91
FL	myfloridahouse.gov		✔️		✔️	B	69	82	73	91
GA	legis.ga.gov	🚫 root	✔️		✔️	A	23	100	80	92
HI	capitol.hawaii.gov		✔️		✔️	B	85	56	73	50
IA	legis.iowa.gov	🚫 root	✔️		✔️	A+	94	71	80	78
ID	legislature.idaho.gov		✔️		✔️	B	27	87	73	69
IL	ilga.gov		✔️		✔️	C	87	61	53	50
IN	iga.in.gov		✔️		❌	B	96	77	67	75
KS	kslegislature.org		❌	❌	❌	—	72	78	60	67
KY	legislature.ky.gov	🚫 www	✔️		✔️	B	38	89	80	68
LA	house.louisiana.gov		✔️		✔️	B	48	73	80	74
LA	senate.la.gov		✔️		✔️	B	41	85	80	91
MA	malegislature.gov		✔️		✔️	F	30	100	73	71
MD	mgaleg.maryland.gov		✔️		❌	B	60	92	60	88
MD	msa.maryland.gov		✔️		✔️	F	41	82	73	77
ME	legislature.maine.gov		✔️		❌	A	76	85	73	89
MI	house.mi.gov		✔️		✔️	B	98	94	67	62
MI	senate.michigan.gov		✔️		✔️	C	86	97	87	91
MN	house.leg.state.mn.us	🚫 root	❌		✔️	B	32	98	80	90
MN	senate.mn		❌		✔️	A+	9	100	87	79
MO	house.mo.gov		✔️		✔️	B	94	61	93	54
MO	senate.mo.gov		✔️		✔️	B	10	93	73	84
MS	legislature.ms.gov		✔️		❌❌	B	34	65	80	82
MT	leg.mt.gov		✔️		✔️	B	37	91	67	77
NC	ncleg.gov		✔️		✔️	B	40	93	67	88
ND	legis.nd.gov		✔️		✔️	B	65	100	73	64
NE	nebraskalegislature.gov		✔️		✔️	B	80	99	80	97
NH	gencourt.state.nh.us		❌		❌	F	0	84	60	75
NJ	njleg.state.nj.us		❌		✔️	A+	89	67	47	75
NM	nmlegis.gov		✔️		✔️	B	87	80	73	83
NV	leg.state.nv.us		❌		✔️	B	58	100	67	91
NY	nyassembly.gov		✔️		✔️	B	57	98	87	99
NY	nysenate.gov		✔️		✔️	A	39	80	67	85
OH	ohiohouse.gov		✔️		✔️	B	27	98	73	69
OH	ohiosenate.gov		✔️		✔️	B	34	61	60	75
OK	oksenate.gov		✔️		✔️	A	7	76	73	83
OK	okhouse.gov		✔️		✔️	B	43	90	73	88
OR	oregonlegislature.gov		✔️		✔️	B	29	97	73	74
PA	legis.state.pa.us		❌		✔️	B	82	63	80	74
PR	tucamarapr.org		❌	❌	❌	—	14	84	60	67
PR	senado.pr.gov		✔️		✔️	B	12	73	67	69
RI	rilegislature.gov		✔️		❌	F	58	69	47	42
SC	scstatehouse.gov		✔️		✔️	B	89	82	73	79
SD	sdlegislature.gov		✔️		✔️	A	6	98	93	100
TN	capitol.tn.gov		✔️		✔️	B	64	100	67	82
TX	house.texas.gov		✔️		✔️	B	68	97	67	69
TX	senate.texas.gov		✔️		✔️	B	52	80	73	77
UT	le.utah.gov		✔️		✔️	A	71	98	80	85
VA	virginiageneralassembly.gov	🚫 www	✔️		✔️	B	46	87	67	69
VT	legislature.vermont.gov	🚫 www	✔️		✔️	B	90	94	73	87
WA	leg.wa.gov		✔️		✔️	B	34	89	73	80
WI	legis.wisconsin.gov		✔️		✔️	B	80	95	87	70
WV	wvlegislature.gov		✔️		❌	B	86	84	73	90
WY	wyoleg.gov		✔️		✔️	B	4	92	80	83

Notes

• Three sites don’t support HTTPS: Alabama, Kansas and Puerto Rico’s lower house. Mississippi downgrades HTTPS request to HTTP.
• Of the sites supporting HTTPS, Massachusetts, Maryland, New Hampshire and Rhode Island get an “F” grade. (Get it together, northeast!)
• New York’s old state assembly site (assembly.state.ny.us) still works and doesn’t redirect you to nyassembly.gov.
• The Michigan House uses house.mi.gov; house.michigan.gov redirects there (but doesn’t have a valid certificate).
• The Michigan Senate uses the opposite: senate.michigan.gov. Going to senate.mi.gov redirects you there (and also lacks a valid certificate).
• Alabama, Arkansas, Georgia, Iowa and Minnesota require you add a www prefix.
• Kentucky, Virginia and Vermont don’t permit www prefixes.
• The Minnesota state senate uses an .mn domain, which belongs to the country of Mongolia. Seems like a security risk.

After upgrading from Mojave to Catalina and Big Sur, Adobe Creative Suite 6 Design Standard no longer worked (despite Illustrator and Photoshop being 64-bit apps).

Not wanting to spend $60/month for occasional use, running these under Mojave in a VM was my next-best option. After repeatedly running into an error using a VirtualBox setup script, I downloaded VMware Fusion 12 Player and tried to install it. The installer got stuck at the macOS Utilities screen, regardless of whether I dragged the Mohave installer app to Fusion or built an ISO.

Eventually I installed Mojave on an external hard drive and used Fusion’s “Install macOS from the Recovery partition” feature to create a working VM.

Once Mojave was up and running, installing Creative Suite from the DVD worked as expected.

After installation, I ran Adobe Application Manager to check for updates. The apps themselves (InDesign, Photoshop, Illustrator) updated successfully. However, several pieces of support software failed to update:

• Adobe Bridge 5.0.2
• Photoshop Camera Raw 9.1.1
• Adobe Extension Manager 6.0.8
• Adobe Digital Publishing Suite Tools 2015.5

The updater would get to the end of the process and error out.

Updating these four components manually was difficult.

• Adobe has a support page for Bridge 5.0.2, but the download link itself is 404.
• The Camera Raw download page only goes back to 10.5. The Internet Archive’s copy shows 9.1.1 but doesn’t download the zip file. The Adobe Forums almost came through here, offering up a working 9.1.1 installer download … but it still wasn’t the latest version.
• Adobe Extension Manager 6 has an information page and a working download link (alternate).
• The DPS Tools download page only goes back to CC 2014, and the Internet Archive’s copy has an info page, but no working download link. These folks have a directory listing of the Adobe FTP site, but the download itself is no longer present.

Adobe Support was anti-helpful. @AdobeCare sent me to chat support, who told me (rather ungramatically) that since CS6 was discontinued, support wasn’t available. I didn’t need support, I just wanted the updater to work and for their website to have working links. They sent me to the Bridge updater page (the one I had already found, with its broken link). After I told them (via email) the link was no good, they doubled down on the idea the link was working:

We would like to inform you that the direct download link is working fine at our end. You need to to follow the “Right Click” steps which was attached with the last email for downloading the file on your computer from the link below:

Thanks, folks. I know how to click things, and I know when something is 404:

~  $ curl -I http://download.adobe.com/pub/adobe/bridge/mac/5.x/AdobeBridge_5.0.2_mul_AdobeUpdate.dmg
HTTP/1.1 404 Not Found
Server: Apache
Content-Type: text/html; charset=iso-8859-1
Content-Length: 0
Date: Mon, 01 Feb 2021 15:56:23 GMT
Connection: keep-alive

Since updates took a while before failing, I figured it was actually executing something and used fs_usage -f filesys -w | grep -i adobe to check. Sure enough, it was downloading a file … but deleting it on error, before I could save the downloaded installer file.

My next step was to figure out what was being dowloaded and download those files manually. Using tcpdump -A port 80 | grep -A 5 GET, I was able to grab the swupdl.adobe.com URLs the updater uses, and manually download:

• Adobe Bridge 5.0.2
• Photoshop Camera Raw 9.1.88
• Adobe Digital Publishing Suite Tools 2015.5

Each dmg contained an installer that ran successfully.