codabiz
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Twenty Sixteen] version 2.9 upgrade issuesHi Kathryn,
Final explanation.
Long forgotten: many years ago, I added .htaccess protection to my wp-content directory as described here: https://www.elegantthemes.com/blog/tips-tricks/wordpress-htaccess-tips-and-tricks
What I have discovered is that WordPress updates, over many years, never overwrote this .htaccess file. After updating allowed types, all is well.
Many thanks.Forum: Themes and Templates
In reply to: [Twenty Sixteen] version 2.9 upgrade issuesCorrection:
My posting errors: Just to clarify, the file I amended was the .htaccess file in the wp-content directory. As per this forum article:https://generatepress.com/forums/topic/problem-with-icons-font-awesome/
Forum: Themes and Templates
In reply to: [Twenty Sixteen] version 2.9 upgrade issuesHi Kathryn,
Yes, mark as closed. Final thoughts: although the fix works, I shouldn’t really need to alter the default .htaccess file in wp-content directory (WP 6.2). After all, It was the addition of new WOFF & WOFF2 fonts in twentysixteen v2.9 that triggered the issue. The best solution may become apparent later on?- This reply was modified 1 year, 6 months ago by codabiz.
Forum: Themes and Templates
In reply to: [Twenty Sixteen] version 2.9 upgrade issuesSolved!
Well you pointed me in the right direction! From a search I found this relating to the .htaccess file in wp-config. I added( |woff|ttf|eot|woff2) to it.
So from this:
Order deny,allow
Deny from all
<Files ~ “.(xml|css|jpe?g|png|gif|js)$”>
Allow from all
</Files>To:
Order deny,allow
Deny from all
<Files ~ “.(xml|css|jpe?g|png|gif|js|woff|ttf|eot|woff2)$”>
Allow from all
</Files>See here: https://generatepress.com/forums/topic/problem-with-icons-font-awesome/
Seems WP 6.2 needs an update? Many thanks to all
Forum: Themes and Templates
In reply to: [Twenty Sixteen] version 2.9 upgrade issuesHi Kathryn,
Many thanks for your efforts and advice. The line-height change to 1.5rem is one I made. After further checks, with Chrome browser if you look at Inspect > Console: there are 12 x 403 errors relating toTwentysixteen “Fonts failed to load”. My logs are also show 404 errors relating to fonts, and over 2000 excess 403 errors. It would seem the problem is related to the fonts files added in v2.9? What do you think?Forum: Themes and Templates
In reply to: [Twenty Sixteen] version 2.9 upgrade issuesAfter clearing all cache I have installed v2.9, which is now live on my website. So something spurious happened with the first update. However, there are differences between v2.8 and 2.9. Though the body text is 1rem, it appears the root font-size 16px is overruled. In the comparison below. The heading has gone from 1 to 2 lines. Pic title is smaller , and the text below the pic has gone from 8 lines to 7 lines! It is as though the root font size is 14px. See comparison here:
Forum: Themes and Templates
In reply to: [Twenty Sixteen] version 2.9 upgrade issuesMany thanks Alvaro.
I had to revert to twenty sixteen v.2.8 live, as I currently have a lot of site traffic and the v.2.9 the small font made the website barely readable. Info: with v.2.9 the font sizes were correct in the page editor mode. I will try upgrading again to 2.9 and take a print screen for you.