irocwebs
Forum Replies Created
-
This is occurring only on sites that have Jetpack installed:
Error Details
=============
An error of type E_ERROR was caused in line 429 of the file /home/sitexxx/public_html/wp-content/plugins/everest-forms/includes/class-everest-forms.php. Error message: Uncaught Error: Call to undefined function evf_get_screen_ids() in /home/sitexxx/public_html/wp-content/plugins/everest-forms/includes/class-everest-forms.php:429
Stack trace:
#0 /home/sitexxx/public_html/wp-includes/class-wp-hook.php(341): EverestForms->maybe_load_integrations()
#1 /home/sitexxx/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#2 /home/sitexxx/public_html/wp-includes/plugin.php(522): WP_Hook->do_action()
#3 /home/sitexxx/public_html/wp-admin/includes/class-wp-screen.php(424): do_action()
#4 /home/sitexxx/public_html/wp-admin/includes/screen.php(243): WP_Screen->set_current_screen()
#5 /home/sitexxx/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-sender.php(535): set_current_screen()
#6 /home/sitexxx/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-sender.php(637): Automattic\Jetpack\Sync\Sender->get_items_to_send()
#7 /home/sitexxx/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-sender.php(490): Automattic\Jetpack\Sync\Sender->do_sync_for_queue()
#8 /home/sitexxx/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-sync/src/class-actions.php(716): Automattic\Jetpack\Sync\Sender->do_sync_and_set_delays()
#9 /home/sitexxx/public_html/wp-includes/class-wp-hook.php(341): Automattic\Jetpack\Sync\Actions::do_cron_sync()
#10 /home/sitexxx/public_html/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters()
#11 /home/sitexxx/public_html/wp-includes/plugin.php(570): WP_Hook->do_action()
#12 /home/sitexxx/public_html/wp-cron.php(191): do_action_ref_array()
#13 {main}
thrownForum: Plugins
In reply to: [WooCommerce] The plugin was updated automatically. Why?Just received this from WooCommerce:
Hello,
We’re reaching out to let you know that a security vulnerability identified in WooCommerce has been patched. If your store runs WooCommerce version 8.1 or newer, we recommend updating to the latest version, WooCommerce 10.4.3, as soon as possible. At this time, we have no indication that this vulnerability has been exploited.
If your store has automatic updates enabled, or if your store is hosted by Automattic (via WordPress.com, Pressable, WordPress VIP, or with any host using WP Cloud), the patch should already be applied. You can check your version by following the steps below.
What you should do
While there is no indication that this vulnerability has been exploited, you should update WooCommerce to the latest patched version,10.4.3, as soon as possible. You can do this by:- Going to Dashboard → Updates in your WordPress admin.
- Select WooCommerce.
- If your current version of WooCommerce is 10.4.3, no further action is necessary.
- If you are not using version 10.4.3, or if you see “Update now,” please click on that link to get the latest version.
What happened
A security researcher recently reported a vulnerability in WooCommerce’s Store API that could allow logged-in customers to view order details belonging to guest customers (those who checked out without creating an account). As soon as we became aware of the issue, our team developed and deployed patches for all affected versions.Our investigation confirmed that this vulnerability:
- Required a user to access a very specific API endpoint, and would not be discoverable without prior knowledge of the exploit.
- Could only make information visible from guest customer orders.
- Required a user to have a registered store account and be logged into the store.
- Has existed for approximately two years with no known exploitation.
What information may have been involved?
If exploited, the vulnerability could have exposed guest customer order information, including names, email addresses, phone numbers, shipping and billing addresses, types of payment methods used, and items purchased. No credit card or other financial details would have been exposed.
Upon discovering the vulnerability, the Woo team immediately developed patches for all 23 affected WooCommerce versions (8.1 through 10.4.2) and carried out testing to ensure the patches would resolve the issue without disrupting store functionality.
If you have any questions or concerns, simply respond to this email or click here, and someone from the Woo Happiness team will get back to you.
Thank you,
The Woo TeamForum: Plugins
In reply to: [Pricing Table by Supsystic] Automatic apostrophe escaping issueI can confirm this is an issue. Any timeline for a fix or should we start looking for a replacement?
Forum: Plugins
In reply to: [Yotpo: Product & Photo Reviews for WooCommerce] Last update crash my websiteI can confirm. Error log:
[20-Jul-2023 11:36:58 UTC] PHP Fatal error: require(): Failed opening required 'lib/widgets/qna-widget.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /home/user/public_html/website.com/wp-content/plugins/yotpo-social-reviews-for-woocommerce/wc_yotpo.php on line 18[20-Jul-2023 11:43:07 UTC] PHP Warning: Invalid argument supplied for foreach() in /home/user/public_html/website.com/wp-content/plugins/woocommerce-services/woocommerce-services.php on line 1115Forum: Plugins
In reply to: [WooCommerce] Number of orders – how does it work?There are several plugins that you can use. https://ww.wp.xz.cn/plugins/search/woocommerce+sequential+order+numbers/
Forum: Plugins
In reply to: [WooCommerce] Number of orders – how does it work?WooCommerce uses the default WordPress post id as the order number. WordPress gives everything a unique post id (images, pages, posts, products, etc.) Since you may upload an image or add a post between orders, the post id would be incremented to the next available number and assigned to your order.
Forum: Plugins
In reply to: [Better Font Awesome] Wordfence AlertWordfence updated the url to https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/better-font-awesome/better-font-awesome-203-authenticated-contributor-stored-cross-site-scripting-via-shortcodes
So this applies to 2.03 and earlier, but still shows as a vulnerability. So NOT for current version 2.04.
Forum: Plugins
In reply to: [Better Font Awesome] Wordfence AlertConfirmed here.
You can go here https://ww.wp.xz.cn/plugins/post-expirator/advanced/ and scroll to the bottom to get previous versions of the plugin.
Forum: Plugins
In reply to: [Responsive Mortgage Calculator] Amortization & ChartAwesome! Thanks for your help.
Forum: Plugins
In reply to: [Better Font Awesome] BFA 2 beta ready for testing. . . again!After upgrading to WP 5.6, the plugin stopped working. Plugin wouldn’t insert the shortcode via the iconpicker. The error via the console window was pointing toward iconpickerItem.context not having a value. A rather simple fix that worked for us.
File old version: better-font-awesome/vendor/mickey-kay/better-font-awesome-library/js/admin.js
File beta version: better-font-awesome-2.0.0-beta4/vendor/mickey-kay/better-font-awesome-library/js/admin.jsAt or around line 41 on the old version & line 61 on the beta version, replace:
// Set up icon insertion functionality. $( document ).on( 'iconpickerSelect', function( e ) { var icon_title = e.iconpickerItem.context.title.replace( '.', '' );with:
// Set up icon insertion functionality. $( document ).on( 'iconpickerSelected', function( e ) { var icon_title = e.iconpickerItem.title.replace( '.', '' );Hope to see this continue to be developed. Thanks for your hard work!
- This reply was modified 5 years, 4 months ago by irocwebs.
I can confirm that it is working again!
This is the issue tracker that pertains to our issue:
I can confirm the issue but it’s not just Simple Calendar. It seems to be all Google Calendar APIs at this time. We are running custom Google Calendar API scripts (non-Simple Calendar) and are having issues with those sites as well.
- This reply was modified 5 years, 11 months ago by irocwebs.
Forum: Plugins
In reply to: [Caldera Forms - More Than Contact Forms] Fatal error: Cannot use on line 10What version of PHP are you using? Same issue reported here? https://ww.wp.xz.cn/support/topic/heads-up-php-5-6-error/