Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • March 24, 2019 at 1:19 pm #1082231
    cg

    After updating to 4.5.5 a protocoll-relative font url from a child-CSS “style.css” is modified wrong:

    this:

    //example.de/wp-content/themes/enfold-example-child/fonts/example-font.eot

    becomes this … with a duplicated domain in the path:

    https://example.de/example.de/wp-content/themes/enfold-example-child/fonts/example-font.eot

    Result: fonts not found and not loaded.

    Unfortunately i don’t have a running stage with this behaviour at the moment, because i had to fix it in the live environment where it occoured after this latest update. Additional info: the theme import for fonts isn’t used, just an own font-folder and URLs in CSS of a child-theme.

    —–
    Edit:
    Related to: https://kriesi.at/support/topic/4-5-5-fails-to-show-any-custom-background-image-at-the-top-of-my-home-page/

    Edit:
    Maybe related to “improved: file merging with relative urls should work better now” or “improved: added several filter for font managment and template builder data” from the 4.5.5 changelog

    March 25, 2019 at 3:49 pm #1082718
    Günter

    Hey Christian,

    Quick Reminder About File Paths

    With 4.5.5 we added support for the first line “/” for root.

    So you do not need to enter domain any more.

    Also check this thread: https://kriesi.at/support/topic/again-one-problem-with-merged-css/

    Hope this helps solving your issue.

    Best regards,
    Günter

    March 26, 2019 at 12:05 pm #1083072
    cg

    Hi Günter, thx for your answer.

    I will try the fixed version of the ‘asset-manager.class.php’ from the repository you linked in that thread.

    Thanks for your work on this.

    Update:
    That fixed file does work. Although it seems that it just changes the protocol relative path to an absolute path including the protocol on its own in the merging/compression process.
    I am not sure, if this is what it should do, because those urls would work without this modification … but maybe it’s safer in the long run to convert all urls to absolute urls … the pro/contra considerations about absolute vs. relative urls have a nice long history since the early years of webdevelopment … hehe … :-)

    Thanks, all good, case solved.

    • This reply was modified 5 years, 8 months ago by cg. Reason: update
    March 26, 2019 at 3:54 pm #1083141
    Günter

    Hi,

    Thank you for the feedback and that we could solve the problem.

    Enjoy the theme and feel free to come back if you need further assistance.

    Best regards,
    Günter

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • The topic ‘Merged CSS modifies protocoll-relative URLs so font-files aren't loaded/found’ is closed to new replies.