Database Table Errors and Bedrock Compatibility

  • Resolved marketingflotte

    (@marketingflotte)


    5 years, 1 month ago

    Hello,

    we’ve wanted to test the plugin as an alternative to the selfhost-google-fonts plugin which seems to be abandoned.
    But after we auto-detected the fonts, downloaded them and generated the stylesheet it throws the following errors after hitting the save button:

    WordPress database error: [Duplicate column name ‘local’]
    ALTER TABLE Dr6klF_omgf_fonts ADD COLUMN local varchar(128) AFTER font_style;

    WordPress database error: [Table ‘wordpress.Dr6klF_caos_webfonts’ doesn’t exist]
    ALTER TABLE Dr6klF_caos_webfonts RENAME TO Dr6klF_omgf_fonts

    WordPress database error: [Table ‘wordpress.Dr6klF_caos_webfonts_subsets’ doesn’t exist]
    ALTER TABLE Dr6klF_caos_webfonts_subsets RENAME TO Dr6klF_omgf_fonts_subsets

    WordPress database error: [Duplicate column name ‘preload’]
    ALTER TABLE Dr6klF_omgf_fonts ADD COLUMN preload tinyint(1) DEFAULT 0 AFTER local;

    Additionally it seems the plugin is not compatible with the bedrock wordpress boilerplate by roots.io.
    In this setup WordPress is installed in a “wp” subfolder and wp-content is called “app”.
    See here: https://roots.io/bedrock/

    The plugin downloads the fonts and created the fonts.css file in the app/cache/omgf-webfonts folder.
    At the frontend the fonts.css file can’t be found cause the path to the font.css file gets prepended with “wp”.
    So intead of https://example.dev/app/cache/omgf-webfonts/fonts.css the path is:
    https://example.dev/wp/app/cache/omgf-webfonts/fonts.css

    Any idea how we can fix this issues?

    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    But after we auto-detected the fonts, downloaded them and generated the stylesheet it throws […] errors after hitting the save button.

    It appears it didn’t add the omgf_db_version line to your wp_options table, because it keeps trying to trigger the install scripts. This only happens after you click ‘save changes’?

    The plugin downloads the fonts and created the fonts.css file in the app/cache/omgf-webfonts folder.

    I’m happy it adds the fonts.css file in the correct folder ??

    So instead of https://example.dev/app/cache/omgf-webfonts/fonts.css the path is: https://example.dev/wp/app/cache/omgf-webfonts/fonts.css

    I think OMGF takes the Base URL of your WordPress install and appends the path to it. I’d have to see how I can change this.

    gh0stshell

    (@gh0stshell)

    I just download the plugin last night 3/8/2020 and see the same errors in my log.

    caos_webfonts’ doesn’t exist for query ALTER TABLE sfd_caos_webfonts RENAME TO wbs_omgf_fonts

    • This reply was modified 5 years ago by gh0stshell.
    Plugin Author DaanvandenBergh

    (@daanvandenbergh)

    Hi guys,

    This bug should be fixed in version 3.0.0 since the usage of custom tables has been replaced with the usage of WordPress’ own wp_options table.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Database Table Errors and Bedrock Compatibility’ is closed to new replies.