Forum Replies Created

Viewing 15 replies - 31 through 45 (of 45 total)
  • Thread Starter elaborate

    (@azinfiro)

    looks like you need it to understand how things works

    Rather than make snide remarks, I suggest you use this feedback to at least improve your documentation—preferably directly on the plugin page since your https://products-filter.com/ domain is also inaccessible.

    I understand if it’s difficult to change the current implementation to account for it, but the issue still remains that the plugin overrides customizations made in Gutenberg, in styles.css, and in functions.php. Maybe it’s possible to find a workaround?

    this is part of search link, and thi is not a directory (folder)

    Thanks for pointing that out. “Directory” is the official technical term used to describe sections of a URL between slashes, as defined in RFC 1738 by Tim Berners-Lee.

    Thread Starter elaborate

    (@azinfiro)

    Just as a quick follow-up, it looks like the plugin generates its own endpoint when filters are applied. Filtered results are shown under the /swoof/ subdirectory rather than at the endpoint where the filters were originally applied. It doesn’t seem to be possible to customize /swoof/ result pages independently with Gutenberg.

    On another note, the domain https://pluginus.net where the plugin’s documentation is hosted is blocked in Indonesia (403). I’ve confirmed it’s accessible from the Netherlands.

    Thread Starter elaborate

    (@azinfiro)

    I’m not alleging your plugin is specifically altering files, but of course your plugin is responsible for somehow overriding the Gutenberg blocks; yours is the only active plugin apart from WooCommerce.

    As for making customizations in functions.php and style.css, that’s a standard way to customize a child theme. I don’t know how you could possibly claim otherwise.

    I’m leaving the review as it is for anyone else to read, including your response here.

    Have a nice day.

    Thread Starter elaborate

    (@azinfiro)

    The issue is with this plugin. The only other relevant active plugin is WooCommerce. The customizations that are being overridden are:

    1. All changes made in the Gutenberg editor, including changes to the product card (e.g., the discount badge’s color and position).
    2. Some custom styles in the theme’s main stylesheet (style.css) that target the product collection block and product card block.
    3. Custom translations added in the theme’s functions.php file (using the gettext hook and specifically targeting the woocommerce and the woo-gutenberg-products-block translation domains).

    Disabling the plugin returns everything to normal.

    But it seems like you have read many articles from some beginner’s site and decided that your opinion is the most correct. However, the world is not as you imagine it in your head.

    What an unprofessional way to respond to criticism.

    Thread Starter elaborate

    (@azinfiro)

    My apologies, I’m wrong. It turned out to be a plugin implementing the feature without documenting it.

    Thread Starter elaborate

    (@azinfiro)

    Just to confirm, are you looking to modify the behavior so that the “Select Options” button for variable products is replaced with “Add to Cart” when a default variation is already set?

    No. That’s already the default.

    This would allow customers to add the product to their cart without selecting options manually—am I understanding that correctly?

    Please note, this isn’t possible with the core WooCommerce functionality. You would need either a custom plugin or custom code to achieve this.

    Sorry, but I think you’re confused. What you’re describing is not only possible in the latest version of WooCommerce, it’s the default behavior when all product attributes have default terms configured.

    I’m asking to turn off the behavior.

    Unfortunately, the only way to remove this – aside from using Javascript after the page loads – is to override Woo’s product-image.php file.

    Javascript is only used to toggle the image. It should be possible to override the CSS responsible for any transition effects, even the inline styling.

    Here are some CSS rules that disable both the animation and the zoom-on-hover effects on a recent site I’ve worked on. It’s tailored to that specific project, so it won’t solve the problem well for all sites, but it might serve as a basis for someone else to solve the problem on theirs:

    /* Product image gallery. */
    .zoomImg {
    display: none!important;
    }
    .woocommerce-product-gallery__image img {
    pointer-events: none!important;
    position: static!important;
    max-height: 400px;
    max-width: 100%;
    width: auto!important;
    height: auto!important;
    object-fit: contain;
    object-position: center;
    }
    .woocommerce-product-gallery__image {
    display: flex!important;
    place-content: center;
    }
    .woocommerce-product-gallery__image a {
    cursor: default;
    }

    /* Convert product image gallery controls into CSS grid. */
    .flex-control-nav.flex-control-thumbs {
    display: grid!important;
    gap: 10px!important;
    grid-template-columns: repeat(auto-fill, minmax(80px, 1fr))!important;
    }
    .flex-control-nav.flex-control-thumbs li {
    width: auto!important;
    user-select: none;
    }

    /* -- Highlight currently selected image more clearly. */
    .flex-control-nav.flex-control-thumbs {
    padding: 5px!important;
    padding-left: 15px!important;
    border-left: 2px solid var(--wp--preset--color--tertiary);
    }
    .flex-control-nav.flex-control-thumbs img {
    border-radius: 5px;
    filter: opacity(60%);
    }
    .flex-control-nav.flex-control-thumbs img.flex-active {
    box-shadow: 0 -3px 2px white, 0 1px 5px rgba(0,0,0,0.2);
    filter: opacity(100%);
    }

    /* Disable product image gallery animations. */
    .flex-viewport {
    height: fit-content!important;
    display: flex!important;
    place-content: center!important;
    }
    .flex-viewport .woocommerce-product-gallery__image:not(.flex-active-slide) {
    display: none!important;
    }
    .flex-viewport .woocommerce-product-gallery__image.flex-active-slide {
    display: flex!important;
    }
    .woocommerce-product-gallery__wrapper {
    transform: none!important;
    }

    @xue28 maybe a feature proposal could be made to let users toggle animations within the Product Image Gallery Gutenberg block?

    Looks like someone else has already asked for help with including variant-specific details in the confirmation e-mail on StackOverflow:

    https://stackoverflow.com/a/66292926/1662230

    Sorry, I don’t have experience with that.

    After poking around, it looks like you’ll have to edit the WooCommerce e-mail template for the order confirmation e-mail, meaning you’ll need to write some PHP code. If you can’t find a snippet online or a plugin that solves it for you, I would either ask for help on StackOverflow or hire a freelance developer if you’re not able to code the solution yourself (or feel like learning just for this task). An experienced developer should be able to solve it in a few minutes; an inexperienced one, in less than an hour.

    Maybe someone else will be able to chime in here in case there’s a more simple solution.

    Good luck.

    You can enter a unique description for each variant which is displayed both on the product page once the variant is selected and as a note on the product when it’s in the cart.

    The description field is available in the product editor, under the “variations” tab after you click the “edit” button to the far right of each variant.

    Does that do what you need?

    To fix the issue on your local WordPress installation, you can use a filter function to intercept WooCommerce when it fetches any translated string and replace the exiting string with a string of your choice.

    Here’s an example of a filter function:


    /* Fix incorrect WooCommerce translations. */
    function replace_incorrect_translations( $translated_text, $text, $domain ) {
    switch ( $translated_text ) {

    case 'Ich bin froh!' :
    $translated_text = __( 'Ich bin ernst.', 'woocommerce' );
    break;

    case 'Ich bin traurig.' :
    $translated_text = __( 'Ich bin ernst.', 'woocommerce' );
    break;
    }

    return $translated_text;
    }
    add_filter( 'gettext', 'replace_incorrect_translations', 20, 3 );

    You need to place the function above inside your child theme’s functions.php file.

    • This reply was modified 5 months, 2 weeks ago by elaborate.
    • This reply was modified 5 months, 2 weeks ago by elaborate.

    WooCommerce allows volunteers to contribute translations on the official WordPress community translation platform. Here’s the link to the editor for all German WooCommerce translations: https://translate.www.ads-software.com/projects/wp-plugins/woocommerce/stable/de/default/

    Be careful not to hit Enter or Shift+Enter until you’re ready to submit a translation. You can’t remove submissions or submit already-submitted translations. GlotPress, the software that powers translate.www.ads-software.com, has a very challenging UI in general, so be careful when you interact with it.

    Forum: Hacks
    In reply to: Allow only specific usernames

    Hi, did you figure this out?

    Thanks!

    I second this.

Viewing 15 replies - 31 through 45 (of 45 total)