Henrijs

@ckadenge Hello. For me they are at the start. They can even be in the Product page, which means instant check-out.

Here you can see that Pay with Apple Pay shows up before any information is even entered (MacOS Safari).

And the parcel selection is all the way at the bottom. That means that the client can pay with Apple Pay without selecting the Parcel box.

If I click the Pay with Apple pay, this is what I see:

So here I can select DPD Pickup points, but can’t select the Pickup point itself.

This all is good, when paying with Card, because I need to press “Checkout” at the bottom.

It would be great to select Apple Pay as the Payment option and only trigger it when “checkout” is pressed, but right now that doesn’t seem possible.

• This reply was modified 3 months, 1 week ago by Henrijs.
• This reply was modified 3 months, 1 week ago by Henrijs.

I’ve tried to change the name of the taxonomy from game-category to game-cat and it worked.
The problem is that we have to change all our themefiles, which mention it and also add the hundreds of games again to those categories.

I’d like to know what’s the root of this problem as the logs are yielding no results.

Also having this issue. Restored to 1.3.18 and it shows up now.

• This reply was modified 1 year, 9 months ago by Henrijs.

Here: https://imgur.com/a/H28VP9y

The theme name and text domain are defined in the style.css file as per all themes I’ve seen.

And note that the previous versions were all working for years.

• This reply was modified 1 year, 10 months ago by Henrijs.

I’m experiencing this issue too.

Polylang and The plugin are updated, but strings in the Front-end are not translating.

Everything works post-related (Blog and WooCommerce products) are being translated, but the custom string are the same.

I have checked the TTfP Settings and everything I need is checked. I’ve double-checked the translations themselves and they are there and are saved in the database.

Here are three screenshots: https://imgur.com/a/QznRtfa
The strings are translated, the setting for the theme is checked, the front-end shows the blog-post translated to English, but the Button (Which is translated using this plugin) is not being translated.

Here are the versions for Polylang and this plugin: https://imgur.com/a/fcUOP7s

I wanted to Rollback but it looks like you’re not using Tags for this plugin: https://imgur.com/a/KCKWWt6

EDIT: I’ve reverted back to Version 3.2.13
This fixed the issue for me, for now.
Comparing the versions and skimming through the main file, I didn’t notice anything that could cause the issue, but still I’m not that familiar of Polylang core functions. One thing I noticed is that you removed all references to domains, could that cause an issue?

• This reply was modified 1 year, 10 months ago by Henrijs.

When is this gonna get fixed?

@temporalnaut what version did you revert back to? Because I still see two lightboxes.

This somehow worked.
What does it do behind the scenes?
It says that it still grabs the regular price, but it changes the main function of the price visibility.

Got it using
apply_filters('advanced_woo_discount_rules_get_product_discount_price_from_custom_price', false, $product, 1, 0, 'all', true);

That’s okay.

The Custom URLs worked flawlessly.

Hoping to see this in the next update.

Overall an absolutely amazing plugin which solves things that plugin developers can’t manage to do themselves.
Waiting for the PRO version. ??

Okay. Somehow when completely reinstalling the plugin, it worked.
The first time I Renumerated orders before changing any settings.
Now I went to the settings beforehand and just saved them. Then Renumerated orders and everything worked flawlessly.
Weird.

I had this issue when I was using Nextgen gallery. If you have it, disable it and see if something changes.
If it works, as a Gallery alternative I personally suggest FooGallery.

Can’t even enter WP-Admin.
Had to uninstall the plugin via FTP.

And randomly when disabling NextGEN Gallery plugin, it works.

This is the second time I have NextGEN breaking an other plugin.

Have there been some reports what could interfere with it?

This is still a problem.
Whenever I update my settings, it just shows this error and no new Galleries can be added.
This render the plugin useless. It’s been 2 months. Can you please fix this?

@joelreed33

Just add the class to the element you want to be clicked on.

This also depends if you’re coding your own theme or just building on an existing one.
If you already have a theme, then maybe the code in my original reply might be the one to work for you.

For example:

<navigation>
    <div class="container">
        <!-- Layout will be according to your theme. -->
        <div class="nav-logo"></div>
        <div class="nav-links"></div>
        <div class="nav-icons">
            <!-- Here add the Icon you want to use -->
            <a href="#" class="open-cart xoo-wsc-cart-trigger"><!--  Where the Class is, add xoo-wsc-cart-trigger -->
                icon
            </a>
        </div>
    </div>
</navigation>