this would have to be with "!important" statements, but it is an option nonetheless. One more thing, it could of course be that your theme overwrites some of the CSS declarations. When you say "still no display, just a blank space where the sampler should be" - do you mean that the text input field of the Fontsampler is missing, or the entire Fontsampler including the UI elements (like the sliders and dropdowns etc). So the screenshot, is that on safari or chrome, or do both look like this?ĭo you have a default text set for the Fontsampler (like in below screenshot), or is it just that the "textarea" is empty - if you hover over the empty textarea (above the UI elements of the Fontsampler), do you get the "text input" cursor? When you click, can you actually type there? It's hard to debug this remote, so forgive my naive questions. It's optional, but it might help me figure out why exactly the javascript breaks and fails to load the font. Since I can't reproduce this with any fonts available to me, would you be comfortable with emailing me ( one of the woff files that you experience this issue - with? Needless to say I will treat the file confidential, I will test it only locally on my computer, and delete the file when I am done testing. Are you experiencing this issue with all woff fonts? Could you try a single publicly available woff file in a single fontsampler, for example from the "Webfont Kit" tab at fontsquirrel, download the kit, extract the zip and use the included woff file to upload to your test site? Does that font work, or do you get the same error? Looking at that spot in the code it looks like something with how the font is loaded by the browser or what font metadata (which gets extracted from the font file) is passed in to the browser on the load call is not quite as I'd expect it to be. The console error you are now reporting, however, is something I can't reproduce. I will look into fixing this particular issue now that I can reproduce them better, however, those problems do not cause Fontsampler to break in my test, and the fonts render just fine despite the error logs from other plugins or conflicting javascript library definitions. I've installed all the plugins you have and get the similar error messages. I think there is two separate problems here. You can also email me at if you don't want to post this publicly. So, what I would ask you is if you could let me know all plugins you have currently installed on your development version? I'll try to install them in a local test version as well and see if I can reproduce the problem then. However, I've helped someone else debug this same issue once, and I would like to see if I could do something in my plugin to avoid this issue even if other plugins aren't playing nice - and to make sure this definitely isn't something I'm handling wrong in the Fontsampler plugin. It's quite likely that when you turn off other plugins (for example one-by-one and reload in between to determine which one is causing the problem) the Fontsampler will work again. A module loader I am using in my plugin has a potential for conflicts if other javascript pieces are loaded in a "non-conformant" way. It looks like there is a problem with Javascript, possibly from other plugins.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |