kontur

Would it be possible for you to link to a sample page, or send me such a link at [email protected] so I can see what loads on the page and what the status of the frontend of the plugin is on page load?

If you open your browsers developer console, then refresh that page that should have the Fontsampler, do you see any warning or error console logs? A javascript error on the page (be it from Fontsampler or for some other reason) may prevent the rendering.

Do you have more context for this error?

Hello,

sorry for the late reply. Do you get any errors, either in the browser javascript console, or in the php error log?

Do you have a link where I could see this issue online?

Hey there,

good to see you managed a work around. Inside any .fontsampler-id-xxx element the .type-tester__content is what ultimately holds the text.

-J

Hey,

wow, that is a weird issue. I can’t seem to switch to the Polish version for comparison, but the English does “write” the wrong direction. Have you tried this with any kind of other woff file, just for testing?

Do you have the multiline option active or disabled?

Johannes

Hey Patric,

I have started on some work for Variable font in the development version of the plugin, but given the time constraints and fundamental changes to WP I’ve come to the conclusion that for major updates to the plugin I’d need to commit to a complete rewrite with Gutenberg blocks and VF/woff2 centric UIs — unfortunately I do not have the time for such a refactor, so for now, things are a bit in limbo.

Hope you can understand. Obviously I would love to make a more modern iteration of the plugin myself, too.

Johannes

Hey,

thanks for the test page. It looks like the font has no Opentype features at all, and I think somewhere in the code when updating the list of detected features there is an assumption that all fonts would have such features which causes a problem in the Javascript.

I’ll have to investigate this some more, but that you for the test case.

Hm,

the auto-populated name is just a “suggestion” — you can type a name there youself, no?

If you somehow managed to save it without a name that would result in problems when accessing the font later, yes.

Cheers,
Johannes

Why is WP such a tremendously shit platform to develop…

Thanks for sharing this “insight” from the WP team.

Great to hear! Thanks for reporting and testing.

The plugin ships with a compiled default settings css file, but this should get compiled from a “template” on settings save. For some reason the default file (but not the template) had the wrong color in there. Will fix this with the next release to avoid from happening at all.

-Johannes

Thanks, I think I’ve found why this happened to slip into the code. If you re-save your general settings, then re-save the specific fontsampler, are those still remaining red?

To be frank I don’t know how to handle this issue. To me it seems the likely cause is two different plugins using the same library and possibly different versions of it. The way the Fontsampler plugin code includes the Twig library should be specific to the plugin, yet it seems to conflict on some global level.

Have you filed a similar issue with Gantry? Assuming they are a framework they are more likely to have encountered this issue before with other plugins, I’d be curious to hear their approach to how this could get resolved.

Hey,

could you post a screenshot of the “Styling” sections of that Fontsampler ID 3 and the main Settings?

Best,
Johannes

Hey,

sorry for the late reply. I have just now updated the Twig library included in the plugin. If you have a chance, could you test with Fontsampler 0.4.10 and let me know if the issue is still persisting?

Best,
Johannes