Typekit now 'web projects' -- old sites working, but cannot set up new

Is there a need for a/this module anyway in case of Adobe Fonts?

You can just copy the code

<link rel="stylesheet" href="https://use.typekit.net/tfg6xoz.css">

and paste it in your head-section in html.html.twig and add your fonts in your CSS file. Its fast, its simple and theres no need to blow up drupal code with an module not serving any extra benefit for this task.

I kinda love the new approach of Adobe fonts, cause everyone can implement fonts easily with just ONE line of extra code. So just uninstall font-your-face and enjoy. ;-)

By the way, this is also an 8.x issue.

I have run into this issue, new font imports are failing because its still attempting to match against a domain (that is no longer present from the api)

Here is a patch to fix the problem

Patch from #7 does not apply. Here is re-rolled one, also have minor improve handle it better when variant not found at Typekit.

Previous patch Improved to

• show better message when font family not found.
• remove existing fonts when importing fonts afresh.

Sorry, just understood that removing already imported fonts is not good idea!
Here is the updated patch.

Same as #10 but for 8.x-3.x

Corrected minor mistake in #11, it was creating blank font items when not receiving variant info. Enhanced, so font entry will get created only if a valid variant info is received.

I'm getting the error "Typekit kit did not match current domain, ourglass8:8888" when I try to import fonts. I have other sites were the same typekit fonts were previously imported and they work OK.

Patch 12 wouldn't apply, terminal log says:

git apply -v typekit.patch
Checking patch modules/typekit_api/typekit_api.module...
error: while searching for:
$kits = typekit_api_get_kits($config->get('token'));
foreach ($kits as $kit_data) {
$kit = typekit_api_get_kit($kit_data->id, $config->get('token'));
if (typekit_api_kit_matches_domain($kit, $_SERVER['HTTP_HOST'])) {
foreach ($kit->families as $family) {
foreach ($family->variations as $variant_id) {
$variant = typekit_api_get_variant($family->id, $variant_id, $config->get('token'));
$metadata = [
'typekit_id' => $variant->id,
'variant' => $variant->font_variant,
'kit' => $kit->id,
];
$font_data = new stdClass();
$font_data->name = $variant->name;
$font_data->url = 'https://typekit.com/fonts/' . $family->slug . '#' . $variant_id;
$font_data->provider = 'typekit_api';
$font_data->css_family = "'" . implode("', '", $family->css_names) . "'";
$font_data->css_style = $variant->font_style;
$font_data->css_weight = $variant->font_weight;
$font_data->foundry_url = 'https://typekit.com/foundries/' . $variant->foundry->slug;
$font_data->metadata = $metadata;
$font = fontyourface_save_font($font_data);
$font->activate();
}
}
}
else {
Drupal::messenger()->addMessage(t('Typekit kit did not match current domain, @domain', ['@domain' => $_SERVER['HTTP_HOST']]));
}
}
Drupal::messenger()->addMessage(t('Imported Typekit kits: @kits', ['@kits' => print_r($kits, TRUE)]));
return $font_context;

error: patch failed: modules/typekit_api/typekit_api.module:106
error: modules/typekit_api/typekit_api.module: patch does not apply

I was in the fontyourface directory

Any thoughts?

@Peter patch is for dev branch. You might be using current release 8.x-3.2 of the module. Please try current dev release then you can apply the patch.

This works on the latest dev at 8.x-3.x-dev from 29 Mar 2023.

Re-rolled for the latest release 4.0.0