I am using a rockettheme template (gantry 4) that lets me select from a list of google fonts for the template font. That list is found in the file: libraries/gantry/admin/widgets/fonts/js/google-fonts.json
RIght after selecting a google font the client wanted, I installed admin tools and created the htaccess file. I THINK then I did not happen to open the template settings section until today. When I did, the google fonts wouldn't 'load' and the error in the inspector console was:
"Failed to load resource: the server responded with a status of 404 (Not Found)" for public_html/libraries/gantry/admin/widgets/fonts/js/google-fonts.json
...and the font displayed on the front end was no longer that google font.
The file was there, right here: libraries/gantry/admin/widgets/fonts/js/google-fonts.json
So, the file was not really missing.
I remembered a list of file type extensions allowed in the htaccess file set up ... so I went back to check and json was not in that list. Just as a guess, I added that file extension. Then, the google fonts list loaded properly again in the templates setting, the error is gone, and the site is displayed in the desired google font again.
I submit this ticket in case someone else runs into this issue, with the suggestion that maybe json should be added to the list of file type extensions allowed by default and to ask if there is any security reason not to have json on that list.
Sincerely, Vicky
RIght after selecting a google font the client wanted, I installed admin tools and created the htaccess file. I THINK then I did not happen to open the template settings section until today. When I did, the google fonts wouldn't 'load' and the error in the inspector console was:
"Failed to load resource: the server responded with a status of 404 (Not Found)" for public_html/libraries/gantry/admin/widgets/fonts/js/google-fonts.json
...and the font displayed on the front end was no longer that google font.
The file was there, right here: libraries/gantry/admin/widgets/fonts/js/google-fonts.json
So, the file was not really missing.
I remembered a list of file type extensions allowed in the htaccess file set up ... so I went back to check and json was not in that list. Just as a guess, I added that file extension. Then, the google fonts list loaded properly again in the templates setting, the error is gone, and the site is displayed in the desired google font again.
I submit this ticket in case someone else runs into this issue, with the suggestion that maybe json should be added to the list of file type extensions allowed by default and to ask if there is any security reason not to have json on that list.
Sincerely, Vicky
Vicky Thomas
