• Resolved Ann

    (@akg-free)


    Hi Daan,
    we’re OMGF with a Divi theme, latest versions.

    In the Divi settings Google font loading and subsets are active. In OMGFs Advanced tab, Divi and Elementor compatibility is auto checked.

    OMGF says the fonts we’re loaded sucessfully locally in backend and disables the external font loading via Divi, but writes an empty css file with just the leading comment and writes no fonts.

    With activated automatic subset configuration under “Advanced” in OMGF, saving on the main OMGF tab leads to an uncaught error:

    Uncaught Error: ucfirst(): Argument #1 ($string) must be of type string, array given
    in .../wp-content/plugins/host-webfonts-local/src/Optimize/Run.php on line 251

    Call stack:

    ucfirst()
    wp-content/plugins/host-webfonts-local/src/Optimize/Run.php:251
    OMGF\Optimize\Run::fluent_implode()
    wp-content/plugins/host-webfonts-local/src/Optimize/Run.php:206
    OMGF\Optimize\Run::optimization_succeeded()
    wp-content/plugins/host-webfonts-local/src/Optimize/Run.php:47
    OMGF\Optimize\Run::run()
    wp-content/plugins/host-webfonts-local/src/Optimize/Run.php:31
    OMGF\Optimize\Run::__construct()
    wp-content/plugins/host-webfonts-local/src/Admin/Optimize.php:72
    OMGF\Admin\Optimize::run()
    wp-content/plugins/host-webfonts-local/src/Admin/Optimize.php:63
    OMGF\Admin\Optimize::init()
    wp-content/plugins/host-webfonts-local/src/Admin/Optimize.php:40
    OMGF\Admin\Optimize::__construct()
    wp-content/plugins/host-webfonts-local/src/Admin/Actions.php:54
    OMGF\Admin\Actions::do_optimize()
    wp-includes/class-wp-hook.php:324
    WP_Hook::apply_filters()
    wp-includes/class-wp-hook.php:348
    WP_Hook::do_action()
    wp-includes/plugin.php:517
    do_action()
    wp-admin/admin.php:176
    require_once('/homepages/29/d51171...0/wp-admin/admin.php')
    wp-admin/options-general.php:10

    This still persists when all plugins but OMGF Free and Query Monitor are deactivated, after a deleted and reinstalled 6.0.3 and even with rollbacks to OMGF 6.02, 6.0.0 and 5.9.3, with and without active OMGF Pro.

    The writing access works, else the unfilled et-builder-googlefonts.css wouldn’t exist and even be recreated after deleting the cache in backend or manually via FTP.

    I won’t try it out on other OMGF / Divi combo projects because this is our only project which isn’t online currently. 😉

    What happens here? o_O

    Regards from Germany
    Ann

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    Hi Ann!

    I can tell you what’s wrong here: we’re both working. On a Friday night!

    All jokes aside; could you check under Advanced Settings if at least one subset is selected under the Used Subsets option? Latin should be selected in your case, and others in case you’re running a multilingual website.

    Hit Save when you made sure one is selected, then head back to the Local Fonts tab.

    Let me know the result! Because if this fixed it then I know how to prevent the error in the future.

    Thread Starter Ann

    (@akg-free)

    Hi Daan,
    thank you for your as usual quick and relaxed response, especially on a friday night! 😉
    Sorry that I get back to you so late, it’s the first time since my post back on this project.
    Yep, good news, selecting a subset fixes the problem! 🙂

    Plugin Author Daan van den Bergh

    (@daanvandenbergh)

    Excellent. Thanks for getting back to me, Ann.

    The next version will include a fix to make sure that these errors won’t occur again.

    Thank you for your patience!

    Thread Starter Ann

    (@akg-free)

    Thank you for your always friendly and helpful manner! 🙂

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Error on run.php, no fonts and empty css in omgf folder …’ is closed to new replies.