dedotombo

I verified that it’s not a plugin/theme incompatibility issue. The problem is present even with default theme and only TranslatePress + WooCommerce enabled as plugins.

Yes, we translated the slug in each language (two actually: default Italian, 2nd English)

Thank you Jules, much appreciated.

Let me be more precise: actually the fully translated URL actually works fine if entered manually but is not the default one e.g. in the shop category page, which instead proposes the partially translated URL I mentioned.

For me it happens also with PixelYourSite and as far as I understood (and verified) it’s the Facebook Pixel Helper extension itself generating that second call. Probably most traffic on my website is still coming from agency staff using Facebook Pixel Helper.

I have the same exact issue. Only Facebook for WooCommerce installed (latest version) and using Omnibug I am sure both PageView events are firing from Facebook for WooCommerce.

It looks like a redirect issue caused by URL parameters encoding/decoding. Both PageView events have the same timestamp, one calls with URL encoded values while the second has decoded values.

Nope, same issue.

Pastebins modified again.

I improved the single sign out code, fixed a plugin bug and reimplemented automatic login, now everything should work fine.

Same links, different code.

Modified admin/admin-menu.php: https://pastebin.com/bMzDrPzB
Modified classes/wp_cassify_plugin.php: https://pastebin.com/QbAgdeAW

I have modified the pastbins.

Automatic login through gateway mode does not seem to work anymore (not even modifying the theme files as suggested by the developer) so I dropped it.

I have improved the Single Sign Out code that is much less hackish now, I’d say production ready.

Same links, different code.

Modified admin/admin-menu.php: https://pastebin.com/bMzDrPzB
Modified classes/wp_cassify_plugin.php: https://pastebin.com/QbAgdeAW

As I said, it’s a little bit hackish but I hope that sharing the code could improve the solution. The single sign out function should be solid and secure, I ported it from the phpCAS library.

Modified admin/admin-menu.php: https://pastebin.com/bMzDrPzB
Modified classes/wp_cassify_plugin.php: https://pastebin.com/QbAgdeAW

That’s it, once uploaded two new checkbox (“Enable gateway mode” and “Enable Single Sign Out”) should appear in WP Cassify admin menu.
Maybe you’ll have to modify the service validate servlet to “p3/serviceValidate” (if it isn’t already configured this way), “p3/” is not added automatically anymore in my version.

Thank you Michael!

In my case the problem was due to Cloudflare’s Rocket Loader feature.

For the moment I disabled it, but I would like to keep using it.
This would be possible by adding the attribute data-cfasync=”false” to the analytics.js script tag.

How can I do it with AIO SEO?

Here you are the complete email log.

Connection: opening to smtp.gmail.com:587, timeout=300, options=array ()
Connection: opened
SMTP -> get_lines(): $data is ""
SMTP -> get_lines(): $str is "220 smtp.gmail.com ESMTP gj6sm7386594wjb.29 - gsmtp"
SERVER -> CLIENT: 220 smtp.gmail.com ESMTP gj6sm7386594wjb.29 - gsmtp
CLIENT -> SERVER: EHLO ~^(.*)$
SMTP -> get_lines(): $data is ""
SMTP -> get_lines(): $str is "501-5.5.4 HELO/EHLO argument "~^(.*)$" invalid, closing connection."
SMTP -> get_lines(): $data is "501-5.5.4 HELO/EHLO argument "~^(.*)$" invalid, closing connection."
SMTP -> get_lines(): $str is "501 5.5.4 https://support.google.com/mail/?p=helo gj6sm7386594wjb.29 - gsmtp"
SERVER -> CLIENT: 501-5.5.4 HELO/EHLO argument "~^(.*)$" invalid, closing connection.501 5.5.4 https://support.google.com/mail/?p=helo gj6sm7386594wjb.29 - gsmtp
SMTP ERROR: EHLO command failed: 501-5.5.4 HELO/EHLO argument "~^(.*)$" invalid, closing connection.501 5.5.4 https://support.google.com/mail/?p=helo gj6sm7386594wjb.29 - gsmtp
CLIENT -> SERVER: HELO ~^(.*)$
SERVER -> CLIENT: 
SMTP ERROR: HELO command failed: 
SMTP NOTICE: EOF caught while checking if connected
Connection: closed
SMTP Error: Could not connect to SMTP host.
SMTP connect() failed. https://github.com/PHPMailer/PHPMailer/wiki/Troubleshooting

The server info is below.

OS: Linux server 4.2.0-30-generic #35~14.04.1-Ubuntu SMP Fri Feb 19 14:48:13 UTC 2016 x86_64
PHP version: 5.5.9-1ubuntu4.14
WordPress version: 4.6.1
WordPress multisite: Yes
openssl: Available
allow_url_fopen: Enabled
stream_socket_client: Available
fsockopen: Available
cURL: Available
cURL Version: 7.35.0, OpenSSL/1.0.1f

Thanks for the help.

• This reply was modified 7 years, 10 months ago by dedotombo.