Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • We have tried all plugin options created by you including simple captcha alternative with cloudflare turnstyle, reCaptcha for WooCommerce and all of them fail miserably in providing any useable benefit. While they appear to work to block spam order and carding issues, they fail to allow valid customer to complete their orders often stating that they need to verify they are human, yet there is no checkbox that allows them to provide a response. Sometimes the checkbox does appear, the human checks the box, and the order still fails to proceed.

    Are there any plans to fix these issues in the immediate future or can anyone with a successful implementation to protect again carding issues provide what product you are using and the level of support and responsiveness that is provided by that provided

    Thread Starter jpennuto

    (@jpennuto)

    Follow-up Question…

    We have just purchased the premium version and prior to doing any installation the following concerns have arisen.

    1. The install documentation tells us to deactivate and delete the older Free version of the plugin before installing the Premium version. How will this process impact already created grouped product on our existing site? Will we lose and have to recreate each of the grouped products once the PREMIUM version is installed?
    2. The install doc also states that we must enable notifications to hear about updated to the plugin via your website and ONLY then, can we access your site and perform a similar download of the zip file to manually perform the updates. Why does the built in PLUGIN UPDATE features of WORDPRESS sites not manage this feature moving forward ESPECIALLY since the premium product is paid for and License keys are part of the site? Am I misunderstanding something? WordPress plugin updates and many hosting companies that manage WOOCOMMERCE sites such as ours have processes to ensure automated updates are applied after performing quality checks for US, their customers. Help me understand or clarify my misunderstanding. I am the site owner and we self-manage our site based on keeping a simple set of plugins and tools that meet our business needs without cluttering our site with nonsense. Your product is one that has helped us keep that sense comfort, but this update process and the unknowns are very worry some. Any clarification you can provide as soon as possible would be helpful. We are planning to proceed with this upgrade tomorrow evening and these answers may help us move ahead quickly or at least help us identify additional safety steps we should complete before that. Thank you….
    Thread Starter jpennuto

    (@jpennuto)

    so both of these responses do not resolve or clarify the issue at hand. Let me repeat, our existing Production site is running the free version 4.3.3. We applied the 5.0.0 update to our Staging site and that when things broke. Our variations defined by our grouped product no longer displayed. Rolling back to 4.3.3 in staging resolved that issue. Therefor my first question is does the 5.0.0 update automatically disable the variations and variable product option and force us to purchase the premium version to resolve that issue?

    question 2: the question related to license keys required for production site and a staging site. As stated in your reply the staging site and use the same license key during install but will not be updated as new version are release. Can we manually apply updates to staging site that would

    keep it current or a version ahead of the production site to allow for plugin testing and functional check before applying update to production? Or will we be forced to buy an additional license. Response will dictate ongoing use of this product

    Thread Starter jpennuto

    (@jpennuto)

    So I may have been unclear with the situation i was describing. to clarify, If a customer has a saved cart that was created a week ago, and now our site admin removed that product from availability, or the product has a date field associated with the product being purchase, ie. a scheduled future class date, and now we have cancelled that product. How do we ensure that any carts that may have been saved prior to the change are all cleared and force the customer to re add the product with appropriate update info to a new cart? The clear sessions tool appears to be the option we need to use but based on your explanation of that it would appear that this would also clear and current carts in progress. Is there a simple tool we can use to see all saved carts or in progress carts so we can determine this exposure?

    Thread Starter jpennuto

    (@jpennuto)

    So can the support team provide me with information as to why WooCommerce 6.3.1 is forcing the use of a plugin also support by WooCommerce, to use for PayPal Payments when it is apparent that that option is fraught with errors, issues and failures that appear to render sites unable to process orders. How is this viewed as a viable suggestion. What is the testing and certification process that both WooCommerce and PayPal are using to ensure that existing store owners can continue to process sales without issue, and have access to IMMEDIATE support to rectify any issues that occur during transition to this plugin? Placing a message here does not solve for that need as responses can take days and business lost is business that NEVER returns. This is an unacceptable process!
    Does this plugin option respond that same way as the former PayPal standard and allow customers to simply checkout as a guest and provide their credit or debit card without requiring a login to a PayPal account? Many customers do not want to create a PAYPAL account for obvious security and privacy issues and that should be respected and Paypal should continue to just act as the merchant services provide to our business account.
    How can we escalate this to find a SOLID, SUPPORTED solution or should we and all other store owners switch to another merchant provider that has a solid supported and PCI compliant offering? Any help would be appreciated

    Thread Starter jpennuto

    (@jpennuto)

    All, thanks for the suggested snippet. I did use this by adding the Code Snippet plugin and then copying the code into a new snippet creation. I then activated it and it appears to have worked. Until now. I recently patched Woocommerce to the current version of 6.3.1, and now a product that I had with 2 location and 6 variations just combined all the display items based on my original message. My follow up question would be:
    1. When a date/time variation is no longer used It simply goes back to a default setting and this caused th repeat of the original issue. But if I go in to modify the variation and DISABLE that variation, then everything realigns correctly. I know that standard response will be, “Then go ahead and disable every time to avoid the issue but why is this happening this way?

    2. Do I have to deactivate and reactive the snippet ever time there is a version upgrade to Woocommerce?

    2. the original snippet code provided above has a couple of variables listed as $qty and $product. is this the correct syntax for the command if on my site the variations I am controlling are Choose LOCATION and CHOOSE DATE/TIME? not sure if it matters or not.

    Thanks for any response

    Thread Starter jpennuto

    (@jpennuto)

    Mirko, I am confused at your suggestion above. When I reviewed the hyperlinks attached to your response and other responses, there are some discrepencies in what action I actual need to take for my site. I am not a developer, but I am confident I can follow detailed instructions on how to fix this issue myself.
    First, the hyperlinks differ in what they display for the syntax of the code snippet and how I set the actual threshold to increase to say 150 variations. Your snippet shows what I think is what you are suggesting but at the end of that code line you have // followed by some comment. Is this required and if not where and how do I terminate the respective code line to insure it doesn’t break my site? The second line of code “add filter…” includes the custom_wc_ajax_variation_threshold and some number at the end. What is the relationship of these variables and the number at the end and do I need to change anything to reflect the number of variations I am looking to grow to?
    I am really trying to find the easiest way to resolve this issue without worrying that any plugin or theme updates will overwrite these changes and resort back to the original limitations. Does Woocommerce have any built in admin function that would allow this change?

    Thread Starter jpennuto

    (@jpennuto)

    Margaret, the reason you were unable to see the actual failure as described is due to the fact that we had to roll out the additional variations to allow the site to function correctly and not confuse customers. But, as stated, this is a capability that is drastically need by us in order to fully show all available options for a set period of time. We are considering a temporary workaround that may hold us over, but we would prefer to have some type of settings or other admin function that would allow us to manage this ourselves. We do not have access to any cpanal functions only what is available to us as the site owners and within the standard wordpress/woocommerce admin feature. Is the any way to add some simple CSS code to our ASTRA theme customization that might help solve this? Please excuse my ignorance as I am not a web developer, but I am trying to understand options so that I can communicated the needs to our hosting company.
    Thanks again for any guidance…

    Thread Starter jpennuto

    (@jpennuto)

    Here is a copy of the system report...  
    
    ### WordPress Environment ###
    
    WordPress address (URL): https://ctlifesaver.com
    Site address (URL): https://ctlifesaver.com
    WC Version: 6.2.1
    REST API Version: ✔ 6.2.1
    WC Blocks Version: ✔ 6.7.3
    Action Scheduler Version: ✔ 3.4.0
    WC Admin Version: ✔ 3.1.0
    Log Directory Writable: ✔
    WP Version: 5.9.1
    WP Multisite: –
    WP Memory Limit: 2 GB
    WP Debug Mode: –
    WP Cron: –
    Language: en_US
    External object cache: ✔
    
    ### Server Environment ###
    
    Server Info: Apache
    PHP Version: 7.4.28
    PHP Post Max Size: 2 GB
    PHP Time Limit: 600
    PHP Max Input Vars: 16384
    cURL Version: 7.29.0
    NSS/3.53.1
    
    SUHOSIN Installed: –
    MySQL Version: 5.5.5-10.3.29-MariaDB
    Max Upload Size: 2 GB
    Default Timezone is UTC: ✔
    fsockopen/cURL: ✔
    SoapClient: ✔
    DOMDocument: ✔
    GZip: ✔
    Multibyte String: ✔
    Remote Post: ✔
    Remote Get: ✔
    
    ### Database ###
    
    WC Database Version: 6.2.1
    WC Database Prefix: wp_
    Total Database Size: 83.01MB
    Database Data Size: 59.13MB
    Database Index Size: 23.88MB
    wp_woocommerce_sessions: Data: 0.12MB + Index: 0.01MB + Engine MyISAM
    wp_woocommerce_api_keys: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
    wp_woocommerce_order_items: Data: 0.27MB + Index: 0.08MB + Engine InnoDB
    wp_woocommerce_order_itemmeta: Data: 1.52MB + Index: 2.00MB + Engine InnoDB
    wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
    wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
    wp_woocommerce_shipping_zones: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_shipping_zone_locations: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_shipping_zone_methods: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_payment_tokens: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_payment_tokenmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_woocommerce_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_actionscheduler_actions: Data: 0.16MB + Index: 0.08MB + Engine MyISAM
    wp_actionscheduler_claims: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_actionscheduler_groups: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_actionscheduler_logs: Data: 0.14MB + Index: 0.09MB + Engine MyISAM
    wp_bp_activity: Data: 0.02MB + Index: 0.16MB + Engine InnoDB
    wp_bp_activity_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_bp_notifications: Data: 0.02MB + Index: 0.11MB + Engine InnoDB
    wp_bp_notifications_meta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_bp_xprofile_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_bp_xprofile_fields: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
    wp_bp_xprofile_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_bp_xprofile_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_comments: Data: 1.52MB + Index: 1.09MB + Engine InnoDB
    wp_esp_answer: Data: 0.13MB + Index: 0.13MB + Engine InnoDB
    wp_esp_attendee_meta: Data: 0.31MB + Index: 0.36MB + Engine InnoDB
    wp_esp_checkin: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_country: Data: 0.05MB + Index: 0.00MB + Engine InnoDB
    wp_esp_currency: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_esp_currency_payment_method: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
    wp_esp_datetime: Data: 0.13MB + Index: 0.11MB + Engine InnoDB
    wp_esp_datetime_ticket: Data: 0.06MB + Index: 0.03MB + Engine InnoDB
    wp_esp_event_message_template: Data: 0.05MB + Index: 0.03MB + Engine InnoDB
    wp_esp_event_meta: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_esp_event_question_group: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_event_venue: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_esp_extra_join: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_extra_meta: Data: 3.52MB + Index: 1.52MB + Engine InnoDB
    wp_esp_line_item: Data: 3.52MB + Index: 1.88MB + Engine InnoDB
    wp_esp_log: Data: 0.09MB + Index: 0.05MB + Engine InnoDB
    wp_esp_message: Data: 20.56MB + Index: 2.20MB + Engine InnoDB
    wp_esp_message_template: Data: 0.14MB + Index: 0.02MB + Engine InnoDB
    wp_esp_message_template_group: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_esp_payment: Data: 7.52MB + Index: 0.13MB + Engine InnoDB
    wp_esp_payment_method: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_price: Data: 0.11MB + Index: 0.02MB + Engine InnoDB
    wp_esp_price_type: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_esp_promotion: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_esp_promotion_applied: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_promotion_object: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_promotion_rule: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_question: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_esp_question_group: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_question_group_question: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_question_option: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_registration: Data: 0.45MB + Index: 0.78MB + Engine InnoDB
    wp_esp_registration_payment: Data: 0.13MB + Index: 0.13MB + Engine InnoDB
    wp_esp_rule: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_esp_state: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_esp_status: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_esp_ticket: Data: 0.14MB + Index: 0.05MB + Engine InnoDB
    wp_esp_ticket_price: Data: 0.06MB + Index: 0.03MB + Engine InnoDB
    wp_esp_ticket_template: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_esp_transaction: Data: 1.52MB + Index: 0.14MB + Engine InnoDB
    wp_esp_venue_meta: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
    wp_events_answer: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_attendee: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_attendee_cost: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_attendee_meta: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_category_detail: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_category_rel: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_detail: Data: 0.02MB + Index: 0.22MB + Engine InnoDB
    wp_events_discount_codes: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_discount_rel: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_email: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_locale: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_locale_rel: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_multi_event_registration_id_group: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_events_personnel: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_personnel_rel: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_prices: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_qst_group: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_qst_group_rel: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_question: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
    wp_events_seating_chart: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_events_seating_chart_event: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_events_seating_chart_event_seat: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_events_seating_chart_seat: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_events_start_end: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_events_venue: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_events_venue_rel: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_layerslider: Data: 0.17MB + Index: 0.00MB + Engine InnoDB
    wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_my_custom_php: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_options: Data: 4.52MB + Index: 0.06MB + Engine InnoDB
    wp_postmeta: Data: 6.52MB + Index: 9.03MB + Engine InnoDB
    wp_posts: Data: 3.52MB + Index: 1.02MB + Engine InnoDB
    wp_signups: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
    wp_termmeta: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_term_relationships: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_usermeta: Data: 0.13MB + Index: 0.03MB + Engine InnoDB
    wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
    wp_wc_admin_notes: Data: 0.03MB + Index: 0.00MB + Engine MyISAM
    wp_wc_admin_note_actions: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
    wp_wc_category_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_customer_lookup: Data: 0.18MB + Index: 0.15MB + Engine MyISAM
    wp_wc_download_log: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_order_coupon_lookup: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_order_product_lookup: Data: 0.23MB + Index: 0.20MB + Engine MyISAM
    wp_wc_order_stats: Data: 0.15MB + Index: 0.12MB + Engine MyISAM
    wp_wc_order_tax_lookup: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_product_meta_lookup: Data: 0.01MB + Index: 0.03MB + Engine MyISAM
    wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_wc_reserved_stock: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wc_tax_rate_classes: Data: 0.00MB + Index: 0.01MB + Engine MyISAM
    wp_wc_webhooks: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_wpmm_subscribers: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_yoast_seo_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
    wp_yoast_seo_meta: Data: 0.03MB + Index: 0.02MB + Engine MyISAM
    
    ### Post Type Counts ###
    
    attachment: 59
    course: 8
    custom_css: 1
    customize_changeset: 3
    espresso_attendees: 2307
    espresso_events: 61
    espresso_venues: 2
    forum: 15
    nav_menu_item: 32
    page: 15
    pm_insight: 716
    pm_page: 157
    pm_report: 54
    pm_site_change: 15
    post: 2
    product: 17
    product_variation: 107
    question: 73
    quiz: 9
    reply: 9
    revision: 216
    shop_coupon: 2
    shop_order: 2281
    testimonials: 6
    topic: 14
    unit: 83
    wp_global_styles: 1
    wpcf7_contact_form: 1
    
    ### Security ###
    
    Secure connection (HTTPS): ✔
    Hide errors from visitors: ✔
    
    ### Active Plugins (6) ###
    
    All-in-One WP Migration Unlimited Extension: by ServMask – 2.44
    All-in-One WP Migration: by ServMask – 7.56
    Contact Form 7: by Takayuki Miyoshi – 5.5.6
    WooCommerce: by Automattic – 6.2.1
    WP Maintenance Mode & Coming Soon: by Themeisle – 2.4.4
    WP Rollback: by Impress.org – 1.7.1
    
    ### Inactive Plugins (1) ###
    
    WooCommerce PayPal Checkout Gateway: by WooCommerce – 2.1.3
    
    ### Dropin Plugins (4) ###
    
    advanced-cache.php: advanced-cache.php
    fatal-error-handler.php: fatal-error-handler.php
    maintenance.php: maintenance.php
    object-cache.php: Redis Object Cache Drop-In
    
    ### Must Use Plugins (1) ###
    
    Nexcess Managed Apps: by Nexcess – 1.26.5
    
    ### Settings ###
    
    API Enabled: ✔
    Force SSL: –
    Currency: USD ($)
    Currency Position: left
    Thousand Separator: ,
    Decimal Separator: .
    Number of Decimals: 2
    Taxonomies: Product Types: external (external)
    grouped (grouped)
    simple (simple)
    variable (variable)
    
    Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
    exclude-from-search (exclude-from-search)
    featured (featured)
    outofstock (outofstock)
    rated-1 (rated-1)
    rated-2 (rated-2)
    rated-3 (rated-3)
    rated-4 (rated-4)
    rated-5 (rated-5)
    
    Connected to WooCommerce.com: –
    
    ### WC Pages ###
    
    Shop base: #1144 - /shop/
    Cart: #1145 - /cart/
    Checkout: #1146 - /checkout/
    My account: #1147 - /my-account/
    Terms and conditions: #2066 - /aha-disclaimer-refund-policy/
    
    ### Theme ###
    
    Name: Astra
    Version: 3.7.7 (update to version 3.7.9 is available)
    Author URL: https://wpastra.com/about/?utm_source=theme_preview&utm_medium=author_link&utm_campaign=astra_theme
    Child Theme: ❌ – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
    WooCommerce Support: ✔
    
    ### Templates ###
    
    Overrides: –
    
    ### Action Scheduler ###
    
    Complete: 685
    Oldest: 2022-03-06 19:53:49 -0500
    Newest: 2022-03-07 12:59:05 -0500
    
    ### Status report information ###
    
    Generated at: 2022-03-07 13:57:47 -05:00
    
Viewing 9 replies - 1 through 9 (of 9 total)