wjwc
Forum Replies Created
-
Updated my previous post. This will be marked as resolved.
That is just so weird. I tested it for the first time, although it doesn’t have direct to guest checkout, after i clicked pay with card, the url directed me to the correct country and state.
The 2nd time i repeat, with a new incognito, the url directed me to US with empty state.
As far as i remember, it always directed me to US with no state field with the default paypal, and yours is no difference. Which is so so wrong. How can i, when i clearly input my fields correctly in WC, but gets redirected to US with blank state, is just utterly ridiculous.
The key point here being, something is just not picking up this 2 fields.
https://i.gyazo.com/3d7f8385882a010e351576cc3f136bbe.png
I’m so done with WC in general. I only got involved not too long ago but it’s just not worth my time spent to debug an issue as important as payment gateways. I retract all my negative attitude towards you, no offense. But WC itself for having this /bug/ is just unacceptable.
No no you’re getting it wrong again.
I don’t mean your plugin populating the WC checkout page.
What i am doing is going through WC checkout > Paypal express
Not Paypal express > WC checkout
But i;ll try it again with the default WC default one and see what happens.
What i am trying to say here is that, WC checkout > paypal express > country + state field not picking up WC checkout field
- This reply was modified 8 years, 1 month ago by wjwc.
Yes, i’m using a form filler.
I mean, i can’t be the only one experiencing this issue, as i’ve mentioned my setup doesn’t involve any other script just plain install with your plugin.
The mobile? Yes, that’s from chrome browser’s mobile simulation. Desktop browser works the same. I just made it this way to record easier.
I don’t really want to spend so much time here trying to debug this issue. But i’ll see what i can do with the logs.
In essence, clearly what is going on here is that either WC doesn’t have the proper way for the country and state field that express checkout likes, or that express checkout by your plugin doesn’t pick it up properly. I’ve provided what i can, I think the least you can do is to replicate this issue on your end as i’ve listed my steps very clearly.
WC + Storefront + Your plugin
Checking in to see if you have any feedback
- This reply was modified 8 years, 1 month ago by wjwc.
Problem #1
State not prefilled
Problem #2
After returning from same session, the country went to US, also with no state.
And, paypal seems to randomly choose a landing page (with a different URL), whenever there is a guest checkout. Take note, this is produced from the same session, how could it show me a different landing page? It even brought me to yet another variant (very random), which the url is something like this. /guest/checkout/signup
I have never experienced that in shopify at all. I tested a ton of times, shopify always brings me to this landing page variant, which is a check mark “save your payment info”. And, of course, shopify always prefill it correctly.
Hey. Sorry for the confusing post. Let me rewrite it again.
Initially, i found a few problems that are actually caused by me not setting things up correctly.
Now, I just have left 1 more thing that is not settled, which is at the last reply.
-
The state field is not brought forward via the woocom checkout field
. The rest are there, including country. When i tested, it didn’t bring forward “selangor” which is one of the states from “malaysia”. Not sure if you can replicate it from your end.
Also, another problem is, maybe it stores some type of cookie which prevents data from being passed to paypal, but i’ve tried changing the field in woocom, but it refuses to pick up the country. Only when i use incognito, will it ever work, but the moment when i edit the field, it is not updated on paypal. The country went to US again, with a blank state.
You can’t be any more wrong. Are you part of the devs? Is that a human answer or a robot?
I managed to solve part of the problem with another plugin already, whereby i was directed straight to guest checkout.
All it needs from what i read is to include a line of code and the url scheme will end with /guest but of course i need to know where to modify the code for it to work.
Oh and btw, i listed 2 issues, you only answered 1, which is not even an answer.
- This reply was modified 8 years, 1 month ago by wjwc.
Ahh. I found one of the issue. I should have enabled to use the standard gateway, now the payment can be go through using paypal express.
And i also found a fix to the blank checkout field. Apparently if no shipping zone is set, ie, it won’t be considered a shippable item.
So there’s one more thing left that still remains. The country field defaults to US, and the state is blank. Which comes back to around the same problem i was trying to solve from the beginning.
I’ve tried locale setting on/off, shipping zone etc, none of it actually managed to pass on country and state field properly.
Edit: Ok, that’s it. Apparently it’s browser cache issue. Now country field is passed. But the state remains unselected.
Thanks for the tips. I will try to implement them.
Acording to amazon, there are sometimes miscofigured health checks by unknown people, and they said i could file a report and have my site removed from their check list. It’s still strange though, as who would want to spend the money to monitor a site that has zero authority in the www.
Yes, that’s the captured page of what the WF logs are showing. Not long after I bought the domain and set up the site, some idiot began doing health checks at a rate of 1 per minute on all the locations. So now my site is roughly around 4 months and thus the 200k hits.
I have already blocked them, but they still show up in my logs.
Doesn’t this means they are still trying to access my website and use my server resource first? Unless it is blocked on the DNS level.
I have zero clue who is watching me, as I have not signed up for any monitoring services.
If they misconfigured their dns to point to me for mispelled name, that could be it. But as for the how and why, i can’t seem to figure.
I want to know how WF blocks the traffic, and are they “fast”? Because the IP needs to first hit and resolve, before the script kicks in. That means it is still using server resources to block them.
Check this out 200k hits per IP.
https://prnt.sc/ba139kForum: Plugins
In reply to: [MailPoet Newsletters (Previous)] SPF record problemIt seems you do not understand what I am complaining about.
Let me simplify it:
The bounce domain email should be set as the sender’s email by default.
Long explanation:
Nothing much to add other than what I have stated in above replies.
Edit:
“but I assume you are saying that an email address with your “main domain” was added into your email headers as the bounce address (Return-Path Header). If that’s the case, then this is done automatically by your email server.”
This is wrong. Wrong way of setup. This should be picked up by your plugin, and set the bounce email using the sender’s email, automatically, by default.
Sender email:
[email protected]
Bounce email:
[email protected]Is that so difficult? Why leave it blank in the plugin?
Forum: Plugins
In reply to: [MailPoet Newsletters (Previous)] SPF record problemSo you’re now blaming this on cloudflare? Used by millions of people?
Are you serious?
Explain your reasoning, while my issue was entirely not a CF issue but the way your bounce email was setup. Addons on cpanel is common, but the main domain should not be picked up by your system. It uses the main domain that was registered with cpanel and there’s no way to verify that domain being the sender for the addon domain.
If there’s a way, please state it. If there’s none, you should have set the same domain as the sender in the field, just like you would set the sender domain automatically.
How would anyone wants the bounce email to be sent to a single main domain and not it’s own individual domain is beyond me. Some people might do it, so be it, but I believe the majority would want the bounce to be sent back to the actual email, and not cluster all hundreds of bounce back to the main.
If your purpose of setting up the same bounce was to simplify the SPF record issue, then there must be a way to also verify the bounce (main) domain as the rightful sender.
Forum: Plugins
In reply to: [MailPoet Newsletters (Previous)] All emails land in spam folderWhat does the SPF record say? Blacklist record?
Forum: Plugins
In reply to: [Comments - wpDiscuz] Count the replies-toYes thats strange indeed. On admin page the comment shows the exact count, but the actual front end shows only 1st level reply and did not count the nested replies.