mario.scalabrino

Solved

I found the solution, it is perfectly designed in the plugin “Cookie Category” section.
Creating new languages and translating the string works smoothly.

Great plugin!

I mark this as solved

Hello zequester,

I have the same problem, I setup my registration form to automatically login in three languages (EN, ES, IT) registration pages, but it redirects always in English.

I hoped the redirect_url would work like this but it doesn’t.
[user_registration_form id="21706" redirect_url="https://www.certifydoc.eu/es/mi-cuenta/"]

Would it work if I use the filter below and based on language redirect to the right language account page? Would this be triggered in the automatic login with registration?

Adding in the child theme’s functions.php:

add_filter( 'user_registration_login_redirect', 'ur_redirect_after_login', 10, 2 );
function ur_redirect_after_login( $redirect, $user ) {
     return home_url();
}

Waiting for your news

Thank you

Cheers

Hello,

it seems that somehow it is another author and almost the same name.

That’;s what I see in the plugin section.

If it is not you sorry for the unjustified complain.

WooCommerce PDF Invoices & Packing Slips Premium Templates
Deactivate | Translate	

Premium templates for the WooCommerce PDF Invoices & Packing Slips extension
Version 2.6.3 | By Ewout Fernhout | View details

I cant’ waste my time like this having paid the plugin.
I need an email, now it is urgent.
I did what you suggested, I’m not respondsible for a broken process.
An email will slve every problem

I wrote in the other form as suggested, please confirm you received it
Thanks

Great, happy that it helped.

Mike, thank you for the great plugin and the prompt support.

I posted a more detailed explanation of the solution it worked in my case here:
https://www.ads-software.com/support/topic/polylang-conflicting-with-woocommerce-paypal-checkout?replies=5

Resolved.

I found two possible solutions, Mike which one do you think is the safest?

1).The first is to go to functions.php and make a private patch as explained here https://www.ads-software.com/support/topic/polylang-and-woocommerce-paypal-ipn-issue?replies=3

function custom_rewrite_basic_wc() {
  add_rewrite_rule('^wc\-api/(.+)/?', 'index.php?wc-api=$matches[1]', 'top');
}
add_action('init', 'custom_rewrite_basic_wc');

I didn’t test this though.

2). The second that worked for me is to go back to the polylang settings settings>languages>settings>url modification (click settings) and click on the check box “Hide URL language information for default language”
This check box has the effect that only for the default language (in my case /en/) polylang doesn’t add the ../en/.. part.
Now it works because when paypal send the IPN to the URL given by woocommerce the listener is there at https://www.yourdomain.eu/wc-api/WC_Gateway_Paypal/

Now I receive the IPN and my orders are updated to completed (not pending payment anymore)

Hope this can help you both. I ignore if my case has some relevance with yours, but I’ll try.

It is a big mess of overlapping permalinks (or however you want to call them)

First check how polylang is configured in settings>languages>settings>url modification (click settings). Remember it.
These are polylang “permalinks” that are applied after the wordpress “institutional” Permalinks.

Every resulting page of your website combine first the wordpress permalink chose, and then the polylang permalink.
When it gets to woocommerce products another additional “product permalink” can be configured but this is another long story of conflicts between polylang and woocommerce (three simultaneous permalinks combined…).

Now, whan woocommerce standard paypal integration (paypal express checkout) gives the control to paypal, it also send the return URL where the IPN listener is supposed to be. It is automatic and controlled by woocommerce. You can find it in paypal log configured in the paypal integration woocommerce>settings>checkout>paypal>debug log> enable logging (here you can find the path to the file.

This is an example of this from my log
05-09-2016 @ 17:46:01 – Generating payment form for order 2387. Notify URL: https://www.yourdomain.eu/wc-api/WC_Gateway_Paypal/

If you click on that URL probably you won’t find any page (404 error) because polylang added something that you configured at the beginning (I asked you to remember earlier). In my case it adds ../en/.. or ../es/.. or../it/.. (my three languages).

In fact if you try this three URL you will find the listener answering to you that this is bad call, but it is there alive and cicking.
https://www.yourdomain.eu/en/wc-api/WC_Gateway_Paypal/
https://www.yourdomain.eu/es/wc-api/WC_Gateway_Paypal/
https://www.yourdomain.eu/it/wc-api/WC_Gateway_Paypal/

Now you can do at least two things.

1).The first is to go to functions.php and make your patch as explained here https://www.ads-software.com/support/topic/polylang-and-woocommerce-paypal-ipn-issue?replies=3
function custom_rewrite_basic_wc() {
add_rewrite_rule(‘^wc\-api/(.+)/?’, ‘index.php?wc-api=$matches[1]’, ‘top’);
}
add_action(‘init’, ‘custom_rewrite_basic_wc’);

I didn’t test it though.

2). The second that worked for me is to go back to the polylang settings I told you to remember settings>languages>settings>url modification (click settings) and click on the check box “Hide URL language information for default language”
This check box has the effect that only for the default language (in my case /en/) polylang doesn’t add the ../en/.. part.
Now it works because when paypal send the IPN to the URL given by woocommerce the listener is there at https://www.yourdomain.eu/wc-api/WC_Gateway_Paypal/

If I said something wrong, please correct me, I’m not an expert and I like to learn.

Also let me know if it was helpful

Cheers

Mario

I made the testing you suggested and I found the problem.

It is Polylang plugin. In my configuration it adds ../en/.. or ../es/.. or ../it/.. to every page.

If I activate again polylang and save permalink I have the same problem because it adds the language info.

The IPN listener is active at these URLs with Polylang activated.
https://www.certifydoc.eu/en/wc-api/WC_Gateway_Paypal/
https://www.certifydoc.eu/es/wc-api/WC_Gateway_Paypal/
https://www.certifydoc.eu/it/wc-api/WC_Gateway_Paypal/

Any suggestion? Is there a way to tell woocommerce to add the language, for example /en/?
Or a way to exclude that page in polylang (I know I should ask polylang for it)?

In the apache2 website directory root /var/www/html/.htaccess file I have only this

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

To make the above work I had to go to the file /ect/apache2/apache2.conf and change AllowOverride from “none” to “FileInfo”

<Directory /var/www/>
Options Indexes FollowSymLinks
#AllowOverride None I have changed this
AllowOverride FileInfo
Require all granted
</Directory>

Thank you Mike for your fast response.

I’ve already tried this; I found it in another thread. Anyway I did it several times now saving multiple times, going back and forth from one permalink to the other but it didn’t work.

You can see it yourself just by clicking the two URLs, the listener stays the old one. The new one is a 404 error.

I copy a screenshot of the actual permalink situation, maybe it is useful.
https://snag.gy/rFcdWu.jpg

What can I try now? Any idea on how to wake up the new listener?

Marco, that doesn’t make sense, I guess you don’t know how the support industry is working then… Impreza support will never support your button. It is your duty, not theirs.

Anyway, it is clear now that this is a non supported plugin, I’ll take it as it is, nice job anyway.

It is an unresolved topic after more than 4 weeks.

Unfortunately not ??

I just left it with the error one day, now a week has passed.
You can’t see the error becaause “Auto block” is disabled, not because it’s working.

If you tell me when you can have a look I’ll check the box, unfortunately I cannot do it differently.