No suitable basket found

14 years 9 months ago #103431 by beat
Replied by beat on topic Re:No suitable basket found
Hi joshcarr6,

Got your PM.

Looks like you solved your issue. Pressed Visa button, could enter a test # and got
"Bad credit card number: please check credit-card number again"

So up to payment works as expected (as it seems to not be the auth.net test-gateway).

Best Regards,

Beat - Community Builder Team Member

Before posting on forums: Read FAQ thoroughly -- Help us spend more time coding by helping others in this forum, many thanks :)
CB links: Our membership - CBSubs - Templates - Hosting - Forge - Send me a Private Message (PM) only for private/confidential info

Please Log in to join the conversation.

14 years 9 months ago #103439 by joshcarr6
Replied by joshcarr6 on topic Re:No suitable basket found
That is just the issue I am having. It works sometimes and then others you get the error.

I haven't changed anything since we last talked.

After you said it worked I tried it on two computers and got the error both times.

I can't believe I am the only person with this problem.

GRRRR so frustrating.

(Just tried it again and it worked???)

Please Log in to join the conversation.

14 years 9 months ago #103455 by beat
Replied by beat on topic Re:No suitable basket found
Ok, great news: could just reproduce now on your site :)

Now need to reproduce here and debug.

Which Joomla version do you have exactly ?

Beat - Community Builder Team Member

Before posting on forums: Read FAQ thoroughly -- Help us spend more time coding by helping others in this forum, many thanks :)
CB links: Our membership - CBSubs - Templates - Hosting - Forge - Send me a Private Message (PM) only for private/confidential info

Please Log in to join the conversation.

14 years 9 months ago #103457 by beat
Replied by beat on topic Re:No suitable basket found
Ok, spent last hour and a half analysing your issue, and could find the cause I think.

Something adds to your https live_site the unneeded :443 (https port number).

Just try accessing your site with https: in front, and click on any link, the :443 gets added by your SEF...

It's not technically wrong, but by default https is 443, that's why it's not added if it's that port. Any link, not just CBSubs...

However when CBSubs redirects to https: while keeping session for the credit-card payment, there is suddenly a mismatch, and one of the numerous security levels built into CBSubs detects that mismatch, and the payment basket doesn't correspond to the "logged in payment session", thus your errror.

I tried reproducing on latest Joomla 1.5.11 with core SEF enabled without success.

2 fixes possible on your side:

1) Check your SEF settings (you probably have a SEF extension, as core joomla does not do that)

or as workaround:

2) Change the param in your CB Login modules to switch to https for registration and login. But test if registration and login then work when starting from http: (without s) homepage.

On our side we will remove the port number in the live-site from our match checking for upcoming CBSubs 1.0.2.

#1112

Beat - Community Builder Team Member

Before posting on forums: Read FAQ thoroughly -- Help us spend more time coding by helping others in this forum, many thanks :)
CB links: Our membership - CBSubs - Templates - Hosting - Forge - Send me a Private Message (PM) only for private/confidential info

Please Log in to join the conversation.

14 years 9 months ago #103558 by joshcarr6
Replied by joshcarr6 on topic Re:No suitable basket found
Ok so I have no idea how to fix what you are talking about. Want to make a quick buck on the side to fix this for me ;)

I don't have any SEF other than the core.

I disabled all components and tested and got the same error.

I upgraded CB from 1.2 to 1.2.1 to see if that would make a difference - nope

I upgraded Joomla from 1.5.1 to 1.5.11 but that didn't matter either.

The only solution I have found is to force the entire site to SSL this makes everything crazy slow but there are no errors.

How soon before CB Subs 1.0.2 and a possible solution for my weird issues?

If anybody can think of a work around that doesn't require me to make the entire site https it would be greatly appreciated.

Please Log in to join the conversation.

Moderators: beatnantkrileon
Time to create page: 0.214 seconds

Facebook Twitter LinkedIn