Visual forms won’t display unless logged into WordPress
-
We have a donation page at https://unitycommunitycenter.org/donate/ with a legacy form that has been working fine for a while. I recently created a new form using the newer visual builder, and it works fine, as long as you’re signed into WordPress. I’ve created another form and tested it, and it appears that all visual forms, whether classic or multi-step, are only displaying while signed into WP.
The page I need help with has three embedded forms on it, one classic and two visual, one before and one after the classic. Inspecting the form and watching the console as the page loads shows it failing to GET https://unitycommunitycenter.org/?givewp-route=donation-form-view&form-id=2901&locale=en_US (and the other form ID) and getting HTTP/2 500 error.
I’ve tried deactivating the security plugin we’re using, but that didn’t help. I also tried using a Twenty Something theme, instead of Avada, to see if that was the problem, but that also didn’t help. I don’t mind uninstalling and reinstalling the GiveWP plugin, but I don’t want to lose our forms, and I don’t see a way to export or preserve them.
The page I need help with: [log in to see the link]
-
Hi @dcsolida ,
Glad you reached out! Happy to help.
I can’t see where the Visual Forms are on this page — https://unitycommunitycenter.org/2025-tournament-reg/. Do those forms have the Published status? If they do, I would recommend switching them back to draft and then publishing them again.
If it caused a 500 error, there might also be some PHP error logs that can give us some more details on what happened.
What I’ll need from you are the PHP error logs. If you don’t know how to get error logs, you can use the Fatal Error Notify plugin, but after activating it you’ll have to trigger the error again to see it. Sporadically, that doesn’t work, so you can ask your host where to find the PHP error logs on the server, then copy/paste the relevant error in your reply.
Furthermore, please send along your System Info.
Navigate to Donations → Tools → System Info (tab) and click the button to “Get System Report” and copy/paste that in your reply here.
That will give me some more context to be able to help.
Looking forward to helping you get to the bottom of this!
Thanks, Robin,
Below is the system info you requested, before installing Fatal Error Notifier. The only red X’s are GiveWP emails, and it looks like we just have some of those disabled. The PHP version of 7.4.33 concerns me. I don’t have access to this organization’s cPanel or server back-end, but I can ask if we an get that updated. I’ll report back with whatever FEN can report…
David
WordPress Environment
Home URL: https://unitycommunitycenter.org
Site URL: https://unitycommunitycenter.org
WP Version: 6.7.2
WP Multisite: –
WP Memory Limit: 768 MB
WP Debug Mode: –
WP Cron: ✔
Language: en_US
Permalink Structure: /%category%/%postname%/
Show on Front: page
Page on Front: Home (#6)
Page for Posts: Unset
Table Prefix Length: omq_
Table Prefix Length: 4
Table Prefix Status: Acceptable
Admin AJAX: Accessible
Registered Post Statuses: publish, future, draft, pending, private, trash, auto-draft, inherit, request-pending, request-confirmed, request-failed, request-completed, refunded, failed, revoked, cancelled, abandoned, processing, preapproval, upgraded, tribe-ea-success, tribe-ea-failed, tribe-ea-schedule, tribe-ea-pending, tribe-ea-draft, tribe-ignored, give_subscription Server Environment
Hosting Provider: Siteground
TLS Connection: Connection uses TLS 1.3
TLS Connection: Probably Okay
Server Info: Apache
PHP Version: 7.4.33
PHP Post Max Size: 256 MB
PHP Time Limit: 120
PHP Max Input Vars: 3000
PHP Max Upload Size: 256 MB
cURL Version: 8.9.1, OpenSSL/3.2.4
SUHOSIN Installed: –
MySQL Version: 8.0.39
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
gzip: ✔
GD Graphics Library: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔ GiveWP Configuration
GiveWP Version: 3.22.1
GiveWP Cache: Enabled
Database Updates: All DB Updates Completed.
Database Updates: All Database Migrations Completed.
Database Tables: ✔ omq_give_donors✔ omq_give_donormeta✔ omq_give_comments✔ omq_give_commentmeta✔ omq_give_sessions✔ omq_give_formmeta✔ omq_give_sequential_ordering✔ omq_give_donationmeta✔ omq_give_revenue✔ omq_give_migrations✔ omq_give_log
GiveWP Cache: Enabled
GiveWP Cache: ✔New Donation✔Donation Receipt✔Donation Processing Receipt✔New Offline Donation✔Offline Donation Instructions✔New User Registration✔User Registration Information✔Donation Note✔Email access❌Renewal Receipt Email❌Admin Renewal Receipt Email❌Subscription Cancelled Email❌Admin Subscription Cancelled Email❌Subscription Completed Email❌Subscription Reminder Email✔Subscriptions Email Access✔Subscription Payment Failed Email
Upgraded From: 3.22.0
Test Mode: Disabled
Currency Code: USD
Currency Position: Before
Decimal Separator: .
Thousands Separator: ,
Success Page: https://unitycommunitycenter.org/donation-confirmation/
Failure Page: https://unitycommunitycenter.org/donation-failed/
Donation History Page: https://unitycommunitycenter.org/donor-dashboard/
GiveWP Forms Slug: /donations/
Enabled Payment Gateways: Stripe - Credit Card, Offline Donation, Stripe - Payment Element
Default Payment Gateway: Stripe - Credit Card
PayPal IPN Notifications: N/A
Donor Email Access: Enabled
Stripe Webhook Notifications: February 25, 2025 7:10 pm Active GiveWP Add-ons
Give - Google Analytics Donation Tracking: ✔ Licensed – by GiveWP – 3.0.1
Give - Recurring Donations: ✔ Licensed – by GiveWP – 2.11.1
Give - Stripe Gateway: ✔ Licensed – by GiveWP – 2.7.0 Other Active Plugins
Avada Builder: by ThemeFusion – 3.11.14
Avada Core: by ThemeFusion – 5.11.14
ICS Calendar: by Room 34 Creative Services, LLC – 11.5.7
ManageWP - Worker: by GoDaddy – 4.9.20
Redirection: by John Godley – 5.5.2
Security Optimizer: by SiteGround – 1.5.7
Speed Optimizer: by SiteGround – 7.7.2
The Events Calendar: by The Events Calendar – 6.10.2
The Events Calendar Pro: by The Events Calendar – 7.4.2
Yoast SEO: by Team Yoast – 24.6 Inactive Plugins
WP Rocket: by WP Media – 3.14.1 Active MU Plugins
ManageWP - Worker Loader: by GoDaddy – 1.0.0 Theme
Name: Avada
Version: 7.11.14
Author URL: https://themeforest.net/user/ThemeFusion
Child Theme: No – If you're modifying GiveWP on a parent theme you didn't build personally, then we recommend using a child theme. See: How to Create a Child ThemeWell, I installed Fatal Error Notifier, and got the test error notification. I’ve then logged out of WordPress and reloaded that page several times without any further email. Apparently, FEN is not picking up what’s going on. So here are all the errors I see in the console using Firefox’s inspector:
Uncaught ReferenceError: jQuery is not defined
537 https://unitycommunitycenter.org/wp-content/plugins/give-recurring/assets/js/give-recurring.min.js?ver=2.11.1:1
n https://unitycommunitycenter.org/wp-content/plugins/give-recurring/assets/js/give-recurring.min.js?ver=2.11.1:1
<anonymous> https://unitycommunitycenter.org/wp-content/plugins/give-recurring/assets/js/give-recurring.min.js?ver=2.11.1:1
O https://unitycommunitycenter.org/wp-content/plugins/give-recurring/assets/js/give-recurring.min.js?ver=2.11.1:1
<anonymous> https://unitycommunitycenter.org/wp-content/plugins/give-recurring/assets/js/give-recurring.min.js?ver=2.11.1:1
<anonymous> https://unitycommunitycenter.org/wp-content/plugins/give-recurring/assets/js/give-recurring.min.js?ver=2.11.1:1
2 give-recurring.min.js:1:58
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” 3 utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” 3 utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self' 'sha256-GYOWnSqienSxfWkrZAx/Dx8ylRNX/4+oGuAlaqo0aRU='” 3 utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self' https://hcaptcha.com https://*.hcaptcha.com” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self' 'unsafe-eval' 'sha256-0m7b6Qc+cU+jCwBIeuVZl8o9AumAMy5E/wN/m6Ps9vs='” 6 utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: (Report-Only policy) The page’s settings would block an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self'” utils.js:42:10
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src https://m.stripe.network 'sha256-5DA+a07wxWmEka9IdoWjSPVHb17Cp5284/lJzfbl8KA=' 'sha256-/5Guo2nzv5n/w6ukZpOBZOtTJBJPSkJ6mhHpnBgm3Ls='” 6 utils.js:42:10Hi @dcsolida ,
I see that you have SiteGround’s Speed and Security Optimizer plugins. Recently, we’ve had some reports with the optimization causing problems with GiveWP. To test if the issue was being caused by it, can you try to disable those plugins first to see if the problem is resolved?
If it does, we can work on the exceptions next.
Looking forward to helping you get to the bottom of this!
Thanks, Robin,
I’ve disabled both SiteGround plugins, but still no visual form showing up at https://unitycommunitycenter.org/2025-tournament-reg/. (No form at all when you’re not logged into WordPress now–I removed the other, classic form.)
We upgraded PHP to 8.3.16 and that fixed the problem. 😀
Oh, and I had to change the page title and url: https://unitycommunitycenter.org/2025-pickleball-tournament-reg/
The topic ‘Visual forms won’t display unless logged into WordPress’ is closed to new replies.
