ferdinand.bardamu
Forum Replies Created
-
To answer my own question, YES applying CSS in the form builder worked for the confirmation/failed pages I produced with the related shortcodes. So this facility appears to be MORE GLOBAL than using Settings > Advanced > Donation Forms for custom CSS.
Hi Ginger, thanks for the response. I would, however, like to use the redirect and have it enabled. If I move my CSS from Settings > Advanced > Donation Forms to that area, it is supposed to also work for the iframes produced by the confirmation/failed shortcodes? Should I understand the Settings > Advanced > Donation Forms custom CSS area to be a legacy feature?
Just following up to confirm I am able to load these fonts now that I have the site on the public internet. We definitely need to be loading these in our GiveWP CSS and I also found the easiest thing to do was skip the specificity and use selectors like body, h1, h2, h3, etc.
To be clear, I created a shortcode to just pull the content of the iframe src but what was displayed was not the form but default 404 content from the live site. So if the font src lookups are also hitting the live site instead of the dev site then they of course cannot take effect.
It appears the plugin is using public DNS for its own lookups? (Or that there are public lookups occurring at some point.) That would definitely cause this problem. In which case I guess I will just see this as moot for now and proceed under the assumption it will resolve once the site is public.
If I grab the content of the iframe and paste it into an Avada code block, the fonts display properly. I will see if I can do this cleanly and just use the shortcode to generate the forms. Seems like this could break easily but we shall see.
Here is the pertinent section of CSS I have at Settings > Advanced > Donation Forms
@font-face { font-family: 'BENTONSANS-COMP-BLACK'; src: url('//hannahandfriends.org/wp-content/uploads/2025/09/bentonsans_comp_black-webfont-1.woff2') format('woff2'), url('//hannahandfriends.org/wp-content/uploads/2025/09/bentonsans_comp_black-webfont.woff') format('woff'); font-weight: normal; font-style: normal; font-display: swap; } @font-face { font-family: 'Nanami-Light'; src: url('//hannahandfriends.org/wp-content/uploads/2025/09/Nanami-Light.woff2') format('woff2'), url('//hannahandfriends.org/wp-content/uploads/2025/09/Nanami-Light.woff') format('woff'); font-weight: normal; font-style: normal; font-display: swap; } @import url('https://fonts.googleapis.com/css2?family=Arvo&display=swap'); } /* Fonts Test */ @import url('https://fonts.googleapis.com/css2?family=Protest+Guerrilla&display=swap'); .give-form, .give-form * { font-family: 'Roboto', sans-serif; } .givewp-layouts.givewp-layouts-headerTitle h2{ font-family: 'Protest Guerrilla'; } .givewp-layouts.givewp-layouts-headerTitle h3{ font-family: 'Protest Guerrilla'; } /* End Fonts Test */I have cleared GiveWP cache and performed a hard reload of the page in question (I have updated my hosts file to work on the site with the correct domain but you can access it by proxy here: https://hannahandfriendsorg.skipdns.link/give/) before recording the screencast below. As you can see, the fonts shown are still the defaults. When I inspect in dev tools and go to change the font-family property, the fonts I added via @font-face are available to be selected but doing so does not change them to those fonts, just to system defaults. (Presumably, the page is aware of them but they cannot be called for iframe content.) The fonts added via @import are not available to be selected and entering them manually likewise does not result in those fonts being displayed. When I look at the Network > Fonts section of the dev console, I can see that the two custom fonts that Avada loads via @font-face are present in some Avada CSS. There are not separate entries for these fonts in any GiveWP CSS.
Screencast (expires in 2 days): https://streamable.com/k4c07o
Screenshot (expires in 3 days): https://temp.sh/sYMtQ/Screenshot_from_2025-10-22_13-50-13.png
Hi, Ginger. I appreciate the prompt response. However, I am afraid you are misunderstanding the problem so I will restate. When I said “even using the built-in custom CSS styles section” that was referring to the “global space” you pointed me to. And yes that does work fine for styling the form inside the iframe. I can even change the font-family property inside the iframe. What I cannot do is effectively change the font-family property to my custom fonts. (Changing them to a supported system font works fine.) By “custom fonts” I am referring to fonts I have directly loaded in my parent document’s CSS as these are unavailable to the iframe. I have included @font-face declarations in the provided GiveWP custom CSS section and these seem to pass sanitization and are saved but they do not actually load the custom fonts. Perhaps they are silently dropped? I have also tried @import for the Roboto Google font and it likewise is saved but the font is not actually imported and available to the iframe. This is a big problem for anyone using non system fonts.
To confirm: You would like us to delete/purge the plugin, install version 2.4.5, and reconfigure our SendGrid settings?
Including a session transcript from an example failed message. (Side note: We can’t include text only visible to plugin authors anymore?)
smtps:plain://smtp.sendgrid.net:465 220 SG ESMTP service ready at geopod-ismtpd-11 EHLO mydomain.com 250-smtp.sendgrid.net 250-8BITMIME 250-PIPELINING 250-SIZE 31457280 250-AUTH PLAIN LOGIN 250 AUTH=PLAIN LOGIN AUTH PLAIN 334 MyAPIKeyIHaveRemovedForPostingToTheSupportForum 235 Authentication successful MAIL FROM:<[email protected]> 250 Sender address accepted RCPT TO:<[email protected]> 250 Recipient address accepted DATA 354 Continue X-Mailer: Postman SMTP 2.4.4 for WordPress (https://ww.wp.xz.cn/plugins/post-smtp/) X-WPCF7-Content-Type: text/plain Content-Type: text/plain; charset=UTF-8 From: My User <[email protected]> To: [email protected] Message-Id: <[email protected]> Subject: Our Subject Date: Fri, 10 Mar 2023 18:05:04 +0000 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline MIME-Version: 1.0 Customer [email protected] . 550 The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved. Visit https://sendgrid.com/docs/for-developers/sending-email/sender-identity/ to see the Sender Identity requirementsI can’t provide any additional information right now but I am confirming this. Version 2.4.4 fails to send with Sendgrid because of “sender verification” error. Rolling back to 2.4.3. resolved for me. Can try to provide more information later.
Thanks for the message. Sounds like I was on the right track. I will go ahead and make my own template.
Yes, I read the documentation and successfully styled all of my forms except for the green spinner and its parent div (want to drop the shadow), which is the topic of this post, as I have not been able to locate the correct CSS selectors. I was curious if anyone else had been able to style those specific elements and, if so, the selectors or approach used.
Edit: Please unmark this as “resolved” as your “answer” did not even address my question. If you do not have an answer, perhaps others in the community will.
- This reply was modified 5 years ago by ferdinand.bardamu. Reason: Noticed this was marked resolved
Agreed! I had missed out on it until now because I was just using Slimstat and did not know what I was missing. (I would have liked to have used Piwik but couldn’t justify the standalone installation for my clients.) It was only Slimstat becoming unmaintained that led me to search again and find what is now Matomo and this great plugin.
Yes, I can confirm that modifying line 70 from
require_once 'vendor/autoload.php';to
require_once __DIR__ . '/vendor/autoload.php';resolved the issue. (Well, the error ceased. Still have to see if data begins accumulating again, but that seems likely.)
Hustle staff, please take note of this syntax modification. I will see if I can find this in the WPMUDev Github repo as well.
Thanks much.