Timeline for Custom font for a Pardot landing page
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2022 at 7:06 | answer | added | Emad Al-Dean | timeline score: 0 | |
| Apr 14, 2021 at 2:44 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 14, 2020 at 5:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 11, 2020 at 6:06 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 12, 2020 at 11:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 10, 2019 at 9:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 31, 2019 at 10:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 22, 2019 at 18:54 | answer | added | Lucas Costa | timeline score: 1 | |
| Dec 24, 2018 at 10:14 | answer | added | kt10208 | timeline score: 0 | |
| Dec 18, 2018 at 9:42 | comment | added | Selim Sevim | I think that is not allowed to store your font files in Pardot and use them like that but I am not 100% sure. | |
| Dec 18, 2018 at 8:12 | comment | added | kt10208 | @SelimSevim My landing page is still on pardot (not being displayed in any other domain via any iframe or something) and the font file is also uploaded to pardot. So basically there's no .htaccess file to update. | |
| Dec 17, 2018 at 16:06 | comment | added | kt10208 | SelimSevim Errors that I get are: CSS3115: 'At sign here'font-face failed cross-origin request. No Access-Control-Allow-Origin header. CSS3119: No fonts available for @font-face rule | |
| Dec 17, 2018 at 16:05 | comment | added | kt10208 | @Aidan I have updated the url to be without the 'http:' part. Thanks. | |
| Dec 17, 2018 at 16:04 | history | edited | kt10208 | CC BY-SA 4.0 |
added 195 characters in body
|
| Dec 17, 2018 at 13:51 | comment | added | Selim Sevim | I think you are getting this error. "No 'Access-Control-Allow-Origin' header is present on the requested resource." You might need to update .htaccess based on this documentation: help.salesforce.com/… | |
| Dec 17, 2018 at 13:15 | comment | added | Aidan | Does anything show in the browser developer console when you load the page? One thing that jumps out is that you're trying to load the font over http. If the page is on https, the browser will block loading the font over http. It's better to write the url as url('//go.pardot...'), then the protocol used for the font will match the page itself | |
| Dec 17, 2018 at 11:54 | history | asked | kt10208 | CC BY-SA 4.0 |