Ubet95 free 190 philippines.Claim Your Free 999 Pesos Bonus Today

Cyberchicken
(@cyberchicken)

3 years, 7 months ago

I just migrated a site that uses Kirki plugin.
The url hasn’t changed, just the hosting provider.
Everything works fine except a couple of fonts.
The browser request to the fonts bears this path
https://www.example.com/home/h6kj08g4/public_html/myWordpressInstallationFolder/wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff

Note that
home/h6kj08g4/public_html/
was the absolute file system path on the OLD hosting provider.

Therefore I searched the whlose database and found many such paths in the wp_option table:
option_name kirki_downloaded_font_files
option_value https://fonts.gstatic.com/s/questrial/v9/QdVUSTchPBm7nuUeVf70viFjuW44JQ.woff “/home/h6kj08g4/public_html/wp-content/fonts/questrial/QdVUSTchPBm7nuUeVf70viFjuW44JQ.woff”

I tried to go into the Typography section of the customizer, change something and save, but the paths and the problem remained.

I searched and replaced (with the proper tool) the old path for the new path but it didn’t work: the urls came out like
“https://www.example.com/home/var/www/vhosts/example.com/httpdocs/wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff”
which was not ok.
I then stripped all the root part of the path, leaving just
“wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff”
and it worked.

I went checking to the old installation of the site and found another quirk:
some paths were just like
https://www.example.com/home/h6kj08g4/public_html/myWordpressInstallationFolder/wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff
and some like
https://www.example.com/home/h6kj08g4/public_html/wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff
which is more correct I think since
“myWordpressInstallationFolder”
should be invisible to any browser since it has been taken care of by .htaccess rewrite rules.

Can you explain what happened?
The physical path to the wp-content shouldn’t be saved in the db I think.
Still the old site _was_ working.

Thank you.

Viewing 1 replies (of 1 total)

Thread Starter Cyberchicken
(@cyberchicken)

3 years, 7 months ago

Update:

I then stripped all the root part of the path, leaving just
“wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff”
and it worked.

I was wrong: it worked just for the root fo the site; for anything with a non-blank slug the fonts that were tried to be loaded from a path like
https://www.example.com/home/h6kj08g4/public_html/myWonderfulPageSlug/wp-content/fonts/mulish/1Ptyg83HX_SGhgqO0yLcmjzUAuWexZNR8aevHZ47LTd9ww.woff

So I decided to uninstall Kirki plugin, delete the correponding option from the db, reinstall the plugin, and now everything works as it should.

Note: the option kirki_downloaded_font_files is much leaner, (I believe there were many duplicates before).
All the local paths are like
“/var/www/vhosts/example.com/httpdocs/myWordpressInstallationFolder/wp-content/fonts/questrial/QdVUSTchPBm7nuUeVf70sSFjuW44JUcz.woff”
which I think is wrong, because the document root could change, and should be calculated, not hardcoded in the db; the cache should take care of any performance hit.

Please make me you considerations.

Thank you

Viewing 1 replies (of 1 total)

The topic ‘old path in migrated site’ is closed to new replies.