Handlee font appears in Page Edit but not Customize or Published

[Richard L]

Hi Weavers ~

I’m making a very simple site with just one page of text. I’ve hidden the header, footer, sidebar, etc to achieve that. For the font I’ve chosen Handlee, but I can only see it in the Page Edit screen. When I click on Customize for the page (where I selected Handlee in every place I could find a font choice), I get a generic sans serif font. Same thing in the preview page and the published page.

The site is http://www.ineedanewpledge.com. (I assume the content will remain confidential with you.)

I have jpegs of the Page Edit and Published screens to show what I mean but don’t see a way to attach or paste them in here.

I’m using WordPress 6.7.1 and Weaver Xtreme 6.7, with WX Plus 6.2, which I downloaded today so I assume it’s up to date.

I have a Lenovo Legion 5 with Windows 10 Home edition (installed 3/2024 and up to date).

I’m having the same issue in both Chrome and Firefox browsers.

Any suggestions? I know it might be something simple that I’m missing but I have no idea what.

Thanks, Richard

P.S. – I got the WX Plus plug-in hoping that I could install an additional font (Segoe Print) that I was using to set up the page in Word, but it doesn’t look like you can do that (or if you can, it won’t work on all devices). If I’m wrong and there is a way to install that font, please let me know as well.

[User]

@Richard L

At the risk of being redundant here, can you please confirm that you’ve gone through the hoops on the  Guide Page on this: https://guide.weavertheme.com/add-new-fonts-google-fonts-and-more/

Regards!

[Richard L]

This reply has been marked as private.

[User]

@Weaver will need to comment.

[scrambler]

While the theme wrapper, container and content are set to handlee, there is a css rule changing that to Manrope in the actual content

body.pagelayer-body p {
font-family: Manrope;
font-size: 18px;
font-weight: 500;
line-height: 1.6;
color: #0000008c
}

Given the selector pagelayer-body that I do not recognize, I suspect you may be using a plugin for content that is doing that. So if you are using a plugin, then check its settings

[Weaver]

You are apparently using the Pagelayer page builder plugin. Apparently it adds HTML wrappers that override anything else – such as Weaver’s settings.

I don’t think all the page builder plugins override the CSS rules that Weaver generates, but I don’t think Pagelayer and Weaver are compatible at all.

[Richard L]

Thank you, Keymaster – that totally worked.

I noticed “pagelayer” in the previous note from scrambler, which for some reason is a plugin though I don’t recall ever using it. I’d been looking through it’s css, then decided to just deactivate it, which solved the problem.

Many gratefuls!

🙂

Richard

[Richard L]

Oh wait, something else strange has happened.

Now the Customize and published pages show the Handlee font, but in Page Edit (for the only page), the text is gone. There had been just two “classic” blocks of text, and now there are two white error boxes that each say: “This block has encountered an error and cannot be previewed.”

My purpose for the site was to add text at the bottom of the block when I receive it from others. But now the blocks seem to be uneditable, even though the text is displayed in the published page.

Do you have any idea why, and how I can get the text blocks to reappear?

Addendum: just tried making a New Page to recreate the Front Page, and it also won’t display Classic blocks. Um.

Sorry bout this, and thanks!

Richard

[scrambler]

I suspect the content was created with the plugin. If so, deactivating the plugin may have removed the content.

Reactivating the plugin may bring it back, then you can save it, remove the plugin again, and recreate the content using WordPress blocks

[Richard L]

Thank you, scrambler, but I’m afraid it didn’t work. I reactivated the Pagelayer plug-ins with no change on that Edit page. It did cause the Customize and published pages to revert to that sans serif font, so I deactivated them again.

I did just discover though that the content is still there, but it can only be seen and edited with the code editor; the visual editor still shows those white blocks with the error message where each of the Classic blocks is located.

I tried recreating the page, which is as I say text only, on a New Page with Paragraph blocks, but some of the text is poetry with indented lines, which (as far as I know) only the Classic block can produce. You can’t indent lines in a Paragraph block (or even an entire block). So I can’t format the text as it’s intended without the Classic blocks.

As well the Classic block has an easy icon for changing text color, and provides colors that I want to use. The Paragraph block will allow you to change the font color but there are only a few choices. You can customize the colors, but it’s basically a lot more steps (besides being unable to indent some lines).

Before this happened, I did manage to input the content that I wanted in there today, but I’m planning to add to that frequently (just by adding text to the bottom of the page). I’ll still be able to do that in the Code Editor, but I’m not adept at html and I’ll have to format the new text by trial and error, then check it against the Customize page. All in all a lot more work than just editing in the Classic block.

I’m trying to give as much info as I can, per your requests above. Hope it’s not too much.

Any more ideas on eliminating that error with the Classic blocks in the Visual Page Editor?

Thanks again,

Richard

 

[Weaver]

That particular error message often comes when you switch back and forth from the block editor to the classic editor.

The general solution for me has been to use the classic editor to delete the “broken” block section. I often switch to the “code” view of the page to see the actual text and HTML directives used on a given page.

And it is also possible the page builder added some stray stuff when creating / editing the page. But I usually end up in the raw or code view of a page, and hand edit out the broken block content.

[Richard L]

Hi Keymaster ~

Never did figure this out – I couldn’t find any content in the Code Editor that wasn’t just part of the original text (which is all the page is, except two links). If I delete the error message blocks in the Visual Editor, it deletes the corresponding code and text on the page. But if I put a new Classic block in, on that or any other page, I get the same error.

I’ve just been editing the page in the Code Editor, and since it pretty simple text I’m not having any difficulty doing that. It doesn’t solve the Mystery of the Block Errors, but it’s functional.

Just letting you know though I don’t assume there’s an easy answer. Interesting though that I’ve got two older sites that use Weaver and also use a lot of Classic blocks, and I’ve never seen this error before.

Feel free to reach out if you think of something. Mostly I’m leaving this note in case you come across this error elsewhere and want to compare details.

Best,
Richard

[Author]

Posts