Forum Replies Created

Viewing 15 replies - 16 through 30 (of 50 total)
  • That is not my experience. It’s still working well on my website — in fact I used it on several product pages yesterday and I checked today and my Simple Product Admin Notes are all right where I expect them to be. My Woocommerce plugin is completely up to date and the General tab in Product Data is still there — it’s also where you enter Prices. I’d attach a screenshot if I could, but this forum doesn’t allow for that.

    Maybe the problem for you is that you are using a grouped product type? See https://awhitepixel.com/blog/woocommerce-product-data-custom-fields-tabs/ “Keep in mind that tab visibility differs depending on product type. For example, “General” tab gets removed when you switch to a grouped product type. So not only should you consider where your custom fields logically fits in, but you need to consider a panel that is visible for all your desired product types.”

    • This reply was modified 2 years, 9 months ago by glazergallery. Reason: Found more info that could be helpful
    Thread Starter glazergallery

    (@glazergallery)

    @gabrielfuentes I just did as you requested, even though that GitHub thread is also marked as “Closed” and has been since December. Did you know that? I see other people have been adding to it, and I just did, too, but how do you know if anyone monitoring it who is in a position to fix the bug?

    I posted this issue on Jan. 25th, too.

    @m155y5 replied and said: This is an issue that was reported here (https://github.com/woocommerce/woocommerce/issues/28557). It is a WordPress Core issue. You can follow it here: https://core.trac.www.ads-software.com/ticket/52038. The fix is planned to be released in WordPress 5.6.1.

    However, I have updated to WordPress 5.6.1 and the issue is still occurring.

    Thread Starter glazergallery

    (@glazergallery)

    Thank you — good to know that a fix is in the works.

    Thread Starter glazergallery

    (@glazergallery)

    Rashed and Riann,

    It worked! Thank you so much for your help!

    –Helen

    Thread Starter glazergallery

    (@glazergallery)

    Thank you, Rashed! I am eager to try this. One question: where the code says “HERE define your product category” would I put the slug? That is, “press-clippings-exhibitions”?

    Thanks,
    Helen

    Thread Starter glazergallery

    (@glazergallery)

    I contacted the host and the tech there was able to help. Storage and plugins were not causing the issue. The problem was that debugging was turned on in wp-config.php. Changing the line < define(‘WP_DEBUG’, true); > from true to false fixed the issue. Why that should matter in terms of making it impossible to add more Categories seemed strange to the tech, but it worked, and I can once again add categories again without the whole site turning solid black. He did say that as a rule it is the best practice to have debug set to true only when actively debugging the site. On the other hand, it’s been set to “true” since July 2017 according to my records, so why it suddenly started acting up just two weeks ago, when no additional plugins or major changes were otherwise made, except for updating WooCommerce to 4.4, is puzzling.

    –HG–

    Thread Starter glazergallery

    (@glazergallery)

    Sorry. Honestly I didn’t know that and meant no harm. It was friendly in tone and not harassing. But won’t happen again now that I know. I hope someone does reply with a fix from the WooCommerce team. Which products would qualify me to get support for that issue?

    • This reply was modified 4 years, 7 months ago by glazergallery.
    Thread Starter glazergallery

    (@glazergallery)

    
    ### WordPress Environment ###
    
    WordPress address (URL): https://www.georgeglazer.com/wpmain
    Site address (URL): https://www.georgeglazer.com/wpmain
    WC Version: 4.3.1
    REST API Version: ? 1.0.10
    WC Blocks Version: ? 2.7.2
    Action Scheduler Version: ? 3.1.6
    WC Admin Version: ? 1.3.1
    Log Directory Writable: ?
    WP Version: 5.4.2
    WP Multisite: –
    WP Memory Limit: 768 MB
    WP Debug Mode: ?
    WP Cron: –
    Language: en_US
    External object cache: –
    
    ### Server Environment ###
    
    Server Info: Apache
    PHP Version: 7.4.8
    PHP Post Max Size: 128 MB
    PHP Time Limit: 300
    PHP Max Input Vars: 10000
    cURL Version: 7.62.0
    OpenSSL/1.0.2k
    
    SUHOSIN Installed: –
    MySQL Version: 5.5.5-10.3.22-MariaDB-cll-lve
    Max Upload Size: 128 MB
    Default Timezone is UTC: ?
    fsockopen/cURL: ?
    SoapClient: ?
    DOMDocument: ?
    GZip: ?
    Multibyte String: ?
    Remote Post: ?
    Remote Get: ?
    
    ### Database ###
    
    WC Database Version: 4.3.1
    WC Database Prefix: wp_
    Total Database Size: 226.16MB
    Database Data Size: 197.90MB
    Database Index Size: 28.26MB
    wp_woocommerce_sessions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    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.02MB + Index: 0.02MB + Engine InnoDB
    wp_woocommerce_order_itemmeta: Data: 0.02MB + Index: 0.03MB + 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.02MB + Index: 0.00MB + Engine InnoDB
    wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
    wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_actionscheduler_actions: Data: 0.08MB + Index: 0.11MB + Engine InnoDB
    wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_actionscheduler_logs: Data: 0.06MB + Index: 0.03MB + Engine InnoDB
    wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_comments: Data: 0.02MB + Index: 0.09MB + Engine InnoDB
    wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_options: Data: 5.48MB + Index: 2.34MB + Engine InnoDB
    wp_pmxi_files: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_pmxi_hash: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_pmxi_history: Data: 0.06MB + Index: 0.00MB + Engine InnoDB
    wp_pmxi_images: Data: 0.34MB + Index: 0.00MB + Engine InnoDB
    wp_pmxi_imports: Data: 9.02MB + Index: 0.00MB + Engine InnoDB
    wp_pmxi_posts: Data: 0.23MB + Index: 0.00MB + Engine InnoDB
    wp_pmxi_templates: Data: 0.23MB + Index: 0.00MB + Engine InnoDB
    wp_postmeta: Data: 93.58MB + Index: 16.03MB + Engine InnoDB
    wp_posts: Data: 81.55MB + Index: 4.75MB + Engine InnoDB
    wp_termmeta: Data: 1.52MB + Index: 0.70MB + Engine InnoDB
    wp_terms: Data: 0.47MB + Index: 0.55MB + Engine InnoDB
    wp_term_relationships: Data: 2.50MB + Index: 1.47MB + Engine InnoDB
    wp_term_taxonomy: Data: 1.52MB + Index: 0.53MB + Engine InnoDB
    wp_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
    wp_wc_admin_notes: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_wc_admin_note_actions: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
    wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
    wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
    wp_wc_product_meta_lookup: Data: 0.23MB + Index: 0.45MB + Engine InnoDB
    wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
    wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
    wp_yith_wcwl: Data: 0.14MB + Index: 0.06MB + Engine InnoDB
    wp_yith_wcwl_lists: Data: 0.19MB + Index: 0.28MB + Engine InnoDB
    
    ### Post Type Counts ###
    
    amn_mi-lite: 3
    attachment: 13258
    custom_css: 1
    jetpack_migration: 2
    ml-slide: 15
    ml-slider: 1
    nav_menu_item: 3
    oembed_cache: 1
    page: 42
    post: 2
    product: 2392
    revision: 3012
    wccaf: 1
    
    ### Security ###
    
    Secure connection (HTTPS): ?
    Hide errors from visitors: ?Error messages should not be shown to visitors.
    
    ### Active Plugins (18) ###
    
    Classic Editor: by WordPress Contributors – 1.5
    Duplicate Page: by mndpsingh287 – 4.2
    MetaSlider: by Team Updraft – 3.16.4
    My Custom Functions: by Space X-Chimp – 4.42
    Products Admin Notes Simple: by Jamie Hall – 1.1
    Simple Image Sizes: by Rahe – 3.2.1
    Page Builder by SiteOrigin: by SiteOrigin – 2.11.1
    SiteOrigin CSS: by SiteOrigin – 1.2.9
    SiteOrigin Widgets Bundle: by SiteOrigin – 1.17.3
    Accessibility by UserWay: by UserWay.org – 1.2
    WooCommerce Visibility: by codemine – 4.1 – Installed version not tested with active version of WooCommerce 4.3.1
    WooCommerce: by Automattic – 4.3.1
    WooSidebars: by WooCommerce – 1.4.5
    WP All Import Pro: by Soflyy – 4.6.2
    WP All Import - WooCommerce Add-On Pro: by Soflyy – 3.2.3 – Installed version not tested with active version of WooCommerce 4.3.1
    YITH Essential Kit for WooCommerce #1: by YITH – 2.1.4 – Installed version not tested with active version of WooCommerce 4.3.1
    YITH WooCommerce Catalog Mode: by YITH – 2.0.2
    YITH WooCommerce Wishlist: by YITH – 3.0.11 – Installed version not tested with active version of WooCommerce 4.3.1
    
    ### Inactive Plugins (0) ###
    
    ### Dropin Plugins (1) ###
    
    install.php: install.php
    
    ### Must Use Plugins (1) ###
    
    WP Staging Optimizer: by René Hermenau – 1.1
    
    ### Settings ###
    
    API Enabled: ?
    Force SSL: –
    Currency: USD ($)
    Currency Position: left
    Thousand Separator: ,
    Decimal Separator: .
    Number of Decimals: 0
    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: #5 - /shop/
    Cart: ? Page not set
    Checkout: #7 - /checkout/
    My account: #8 - /my-account/
    Terms and conditions: #20359 - /privacy-policy/
    
    ### Theme ###
    
    Name: Vantage Child
    Version: 1.0.0
    Author URL: https://siteorigin.com/
    Child Theme: ?
    Parent Theme Name: Vantage
    Parent Theme Version: 1.15.0 – 1.15.1 is available
    Parent Theme Author URL: https://siteorigin.com/
    WooCommerce Support: ?
    
    ### Templates ###
    
    Overrides: –
    
    ### Action Scheduler ###
    
    Complete: 180
    Oldest: 2020-07-06 17:01:18 -0400
    Newest: 2020-08-04 04:32:50 -0400
    
    
    Thread Starter glazergallery

    (@glazergallery)

    Hi Phillip — I already asked one of the developers of my theme (SiteOrigin, the theme is Vantage) before posting this and after some conversing back and forth, he said the arrow behavior I describe was the default behavior of WooCommerce — which it must be, because as I said, it’s right there in the Storefront demo. So if you are saying you could give me the code that would keep the arrows on all the time in Storefront, I’ll take all backup precautions prior to trying it out with my theme, and if it causes a conflict, I know how to delete the code from style.css or function.php or whatever is involved. I know how to modify a Child Theme and will accept the code with the caveat that I need to be prepared for a potential conflict if I’m not using Storefront. But I’d like to give it a try.

    I really do think it is a problematic feature of WooCommerce. I can’t think of any reason it would be desirable to turn off arrows in a lightbox for numerous images.

    • This reply was modified 5 years, 7 months ago by glazergallery.
    Thread Starter glazergallery

    (@glazergallery)

    @m155y5: The behavior I described has nothing to do with Photoswipe: it’s the default behavior of WooCommerce. Don’t believe me? Go to the Storefront demo! https://themes.woocommerce.com/storefront/product/build-your-dslr/#camera-body

    And as far as we’re concerned, a highly problematic default, which we have observed confuses people. We want the arrows to stay on all the time, even if the mouse is not moved. I suppose since you were in such a rush to prematurely declare this “resolved” you might ignore this, but I want anyone else who reads this thread to know you did not address the issue, nor take the trouble to really understand the problem in the first place.

    Thread Starter glazergallery

    (@glazergallery)

    After investigating further I have inquired of the makers of our theme and they said that while it is true that I did not install the Photoswipe plugin, it is a hidden part of theme.

    Thread Starter glazergallery

    (@glazergallery)

    Wait, what?! I am NOT using the Photoswipe plugin! I’ve never even heard of it. Please explain. How can you mark this thread as resolved? If you’re supposed to be a “Happiness Engineer” you have distinctly missed the mark.

    Thread Starter glazergallery

    (@glazergallery)

    They are most definitely not on at all times. They fade out after a few seconds, whether the mouse is in the browser window or moved off the browser window. And we don’t want that.

    Thread Starter glazergallery

    (@glazergallery)

    Thanks for fixing this! Sounds better now.

Viewing 15 replies - 16 through 30 (of 50 total)