jayPEG
Forum Replies Created
-
Hello, I hadn’t heard back and wanted to follow back up. Do you have any other suggestions? I can create DB tables manually if needed if you think that might work.
Thank you Bruna. I set the PHP version back to 7.4 and went back all the way to version 4.0.1 before being able to activate it successfully. I then ran the update and it caused a critical site error. I changed PHP back up to 8.2 to ensure that it wasn’t that.
Forum: Plugins
In reply to: [Broken Link Checker] WPMUDEV_BLC Webhook WarningOkay, this is strange, but there were other errors going on specifically with Ninja Tables Pro. I went ahead and disabled this since it was less crucial to the site working and found that the errors went away for both Plugins. I then re-activated Broken Link Checker Plugin and neither of the errors have returned in the last 24 hours. There must have been some conflicting processes with those two Plugins that was hung up that deactivating the Plugin cleared out. I’ll let you know if it returns, but for now, I’ll mark this as resolved. Thank you very much.
Forum: Plugins
In reply to: [Broken Link Checker] WPMUDEV_BLC Webhook WarningThank you Imran,
I ran the error logs through AI and was told this.“The
parse_request()method in your plugin is declaring the$wpparameter by reference (&$wp), but WordPress core firesdo_action('parse_request', $wp)by value. This causes a PHP warning in PHP 8+ and needs to be corrected in the plugin code. This is not a theme or plugin conflict but a compatibility issue with the plugin’s function signature.”
I’m not sure if that’s helpful, but I though I’d try that before spinning up a staging site.
Best,
-ThomasForum: Plugins
In reply to: [Broken Link Checker] WPMUDEV_BLC Webhook WarningThank you Saurabh. The site is using PHP 8.2.29.
Thank you Matthias.
Very strange, but I’m no longer seeing any of these errors so it must have been a fluke. I did look and seewp_realmedialibrarywas created and it’s the free version. Since I no longer see those in the error logs, I’m guessing it was some other issue, but if it returns, I’ll let you know.Forum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Scan FailedTerrific! Thank you very much for the excellent support.
All the best,
-ThomasForum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Scan FailedThank you! That fixed it!
It is failing with the GoDaddy Firewall re-enabled, but that’s a different issue of course. Is it only 35.83.41.128, 52.25.185.95, and 54.148.171.133 that need to be allowed for WordFence?Thank you,
ThomasForum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Scan FailedVery strange. I don’t see any blocking. I had noticed that the client had purchased the GoDaddy Website Security plan which I immediately thought could be the issue and disabled the Firewall part of it.
I looked back at the cURL issue and there doesn’t appear to be any additional information offered there. No details to expand. I’ll provide images for each of these.
Additionally, I looked in their CPanel to ensure that no IP’s were added to the IP Blocker list.
Forum: Plugins
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Scan FailedThank you Scott. I just ran it again and it failed again. It doesn’t appear intermittent. It’s every time I run it now. Here are the last of the logs from when it just failed.
[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/wpforms-lite/assets/images/payments/status/icon-partrefund.svg (Size: 611 B Mem: 139 MB)
[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/wordpress-seo/migrations/20171228151841_WpYoastPrimaryTerm.php (Size: 1.4 KB Mem: 139 MB)
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/revslider/public/assets/svg/busy-icons-svg/money5.svg (Size: 11.53 KB Mem: 139 MB)
[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanned contents of 2155 additional files at 7.12 per second
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/revslider/public/assets/svg/notification/ic_airline_seat_legroom_extra_24px.svg (Size: 313 B Mem: 139 MB)
[Oct 17 15:38:31] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:31] Scanning contents: wp-content/plugins/us-core/templates/sidebar.php (Size: 7.45 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/busy-icons-svg/laptop-diagram.svg (Size: 10.08 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/src/Admin/Forms/BulkActions.php (Size: 9.64 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/busy-icons-svg/arrow-left.svg (Size: 4.43 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/js_composer/include/templates/editors/popups/ai/sad-ai-logo.tpl.php (Size: 23.23 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/contact-info/phone/editor.js (Size: 185 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/templates/admin/settings/email-heading.php (Size: 530 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/json-endpoints/jetpack/class.jetpack-json-api-modules-list-endpoint.php (Size: 311 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/src/Helpers/CacheBase.php (Size: 11.49 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/slideshow/slideshow.js (Size: 6.14 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/markdown/test/__snapshots__/markdown-renderer.js.snap (Size: 1.75 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/image/ic_exposure_neg_2_24px.svg (Size: 679 B Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/wpforms-lite/vendor/woocommerce/action-scheduler/classes/abstracts/ActionScheduler_Abstract_RecurringSchedule.php (Size: 3.1 KB Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/extensions/blocks/business-hours/editor.js (Size: 182 B Mem: 139 MB)
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/revslider/public/assets/svg/editor/ic_strikethrough_s_24px.svg (Size: 1.07 KB Mem: 139 MB)
[Oct 17 15:38:32] iconv(): Detected an illegal character in input string (8) File: /home/jong5nw19fur/public_html/wp-content/plugins/wpforms-lite/vendor/symfony/polyfill-mbstring/Mbstring.php Line: 409
[Oct 17 15:38:32] Scanning contents: wp-content/plugins/jetpack/_inc/blocks/vendors~map/mapbox-gl.f81f5e1d3c950198407d.js (Size: 651.6 KB Mem: 139 MB)
[Oct 17 15:53:59] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=fca5719f75cda5e48acd424c39d33001eddb5c003493468df291a73f9f8f15e76a6e126dfa47327274aa25beff62b8a07beb5dbd5e9697edafcac8ec83b905b16da7b70e6c63782da54547283c33037f&s=eyJ3cCI6IjYuNi4yIiwid2YiOiI3LjExLjciLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc29jaWV0eWZvcmRpc2FiaWxpdGllcy5vcmciLCJzc2x2IjoyNjk0ODg1MTEsInB2IjoiOC4zLjExIiwicHQiOiJsaXRlc3BlZWQiLCJjdiI6IjcuODcuMCIsImNzIjoiT3BlblNTTFwvMS4xLjF3Iiwic3YiOiJBcGFjaGUiLCJkdiI6IjEwLjYuMTgtTWFyaWFEQi1jbGwtbHZlIiwibGFuZyI6ImVuIn0&action=resolve_ips
[Oct 17 15:54:03] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=fca5719f75cda5e48acd424c39d33001eddb5c003493468df291a73f9f8f15e76a6e126dfa47327274aa25beff62b8a07beb5dbd5e9697edafcac8ec83b905b16da7b70e6c63782da5454Certainly. The site is using the Impreza Theme along with the following Plugins...
Admin Menu Editor
Advanced Custom Fields
CMS Tree Page View
Enable Media Replace
Gravity Forms
Indeed Ultimate Membership Pro
Multiple Admin Email Addresses
Plugins List
Pods - Custom Content Types and Fields
Seriously Simple Podcasting
Slider Revolution
Speed Optimizer
UpdraftPlus - Backup/Restore
UpSolution Core
User Menus
Wordfence Security
WPBakery Page Builder
XML Sitemap Generator for GoogleHello. We’ve been experiencing the same issue beginning a couple of months back. It may be unrelated, but I thought you should know just in case there’s an issue. The site we have it on doesn’t have a lot of Plugins and hadn’t been having the issue until recently, but no new Plugins had been added. It’s possible that an update to some Plugin(s) caused it.
Terrific! Thank you!
I can confirm that this is the case. I found this issue on 5 separate sites where the Plugin had been updated to version 1.3.1.
Forum: Themes and Templates
In reply to: [ColorMag] Broken Theme after UpgradeThank you Barsha. I found the issue. The site was using a child theme with a stylesheet that was copied from the parent them. Updating it solved the issue.