David
Forum Replies Created
-
Thanks for looking into it, Lucian.
We might try a little to see if the REST API might help, and will update you if that’s successful.
In the meantime, we can use WP 2FA with LDAP auth, and that is working fine for us.
David
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/
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.)
Well, 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:10Thanks, 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 ThemeSaurabh,
We’ve allowed access to admin-ajax.php, and that did the trick. Users off-campus are now able to save and continue.
Thank you for your help!
David
Thanks, Saurabh. I’ll look into that and let you know.
David
Thanks, Dmytro,
That did it! I created a form on yet another site, where I haven’t done anything in the .htaccess file. The radio dots show up as expected, and all is well.
Have a great day (and holiday, if you celebrate Thanksgiving!)
David
Hi Nithin,
I’ve done that, and went and tested a third site using the Forminator plugin. Dots weren’t showing up in the radio circles there. I found the .htaccess in the uploads folder that for that site and took a look at it.
Where there was an “Options -ExecCGI” line in the other two, this one had a blank line, and it wasn’t until I commented out the second options line: “Options -Indexes” that dots started to appear on the form on that site.
David
So there was a .htaccess file there, Adam, and it had two lines that started with “Options”. I commented out both of them, and that appears to have fixed the problem. I can now see the dots on the radio options on the DailyMonster site.
However, that didn’t fix it for the OWU Forms site. But, whaddya know? there was also a .htaccess file in a forminator directory in that site’s uploads folder. When I did the same there, it fixed it for that form as well.
So, if I do that in every .htaccess file in every uploads folder for every site that uses the plugin, will they get overwritten the next time the plugin has an update?
David
I also just upgraded WP core from 6.3.2 to 6.4.1 on both servers, and still have the issue.
BTW, here’s another sample form we’re using to test: https://sites.owu.edu/dailymonster/test-forminator-page/
Thank you for the prompt response, Kris!
I’ve now added “/var/www/html/wp-content/uploads/forminator/” as our Custom File Uploads Storage path, and that hasn’t helped.
I’ve replaced the contents of the /wp-content/plugins/forminator folder with those from a freshly downloaded zip file, and that hasn’t helped.
I also disabled all but four other plugins (that are network activated) and, alas, that also didn’t fix it. We also have a WP multisite test server (that’s behind our campus firewall) and I was able to deactivate all plugins, other than Forminator, there, and we still have the issue with the radio dots there too.
Any other ideas?
David
Forum: Fixing WordPress
In reply to: WP 5.83 – 5.9 update – websites showing critical error@zanton I replaced wp-settings.php and wp-includes/script-launcher.php (that I had modified) and all appears to be well. Thanks!
Forum: Fixing WordPress
In reply to: WP 5.83 – 5.9 update – websites showing critical errorSame here on our production multisite server. The automatic upgrade said it had failed, but I was still able to navigate network admin. Several site home pages gave critical errors, caused by this
PHP Fatal error: Uncaught Error: Call to undefined function wp_get_global_stylesheet() in /var/www/html/wp-includes/script-loader.php on line 2322I temporarily commented out that line, (the following line simply returns, if stylesheet is empty,) and no more error. I hate hacking core code to fix a fatal error…
However, now our server says it’s running 5.9, despite the upgrade failure. I will follow advice above, and replace the mentioned subdirectories.
Forum: Plugins
In reply to: [Classic Editor] Editor Options Not Showing Up in SettingsI also found the option on the Network Settings page.
Thanks,