Author Topic: Paypal (new API) problems  (Read 47731 times)

stinga

  • Contributing Developer
  • Full Member
  • *
  • Posts: 872
    • Squangle ltd
Re: Paypal (new API) problems
« Reply #45 on: June 06, 2013, 12:12:04 pm »
you will probably need a programmer to cast their beady eye over the code to determine what is going on.
Stinga.
614869 products in 747 categories with 15749 products in 1 category.
                                             Document Complete   Fully Loaded
                Load Time First Byte Start Render   Time      Requests      Time      Requests
First View     2.470s     0.635s     1.276s          2.470s       31            2.470s      31
Repeat View  1.064s     0.561s     1.100s          1.064s       4             1.221s       4

lejeannotfr

  • Jr. Member
  • **
  • Posts: 59
Re: Paypal (new API) problems
« Reply #46 on: June 06, 2013, 16:48:32 pm »
you will probably need a programmer to cast their beady eye over the code to determine what is going on.

Thanks for your answer...
You told that : "The redirect is not working, so it goes to this page rather than paypal. Shouldn't be hard to fix."
I said that the redirection was working, but before you get to paypal payment page, I begins with this page first. This problem happens only in "chrome", Safari and IE9, not with Firefox. And it happens since i'm in 1.1.9...Before that I did not have this problem.
I also said that my shopping in 3 steps, not 4 ... that he has consequences?

Now pay a developer for that, to be honest I prefer this : given the time spent managing problems and bugs with virtuemart (even for its updates) if I have to pay me a developer, it will migrate to another CMS more suited to e-commerce and more professional level monitoring. With Joomla and VM when a new version comes out, nobody wants to take support within 6 months. It is not possible at the level of sales professionals online, too many incompatibilities between all needed components and VM to run a store professionnaly. You must update all your website every week!! It's impossible to manage like this a live shop. Thank you for answering me but telling me to pay a developper, this one will meet the same problem and it won't read all your code to find the problem. So it is unwise to pay a professional to find a solution. ???

I work in the internet since 15 years, i wanted to start my first own shop with joomla and VM but since 2 years i work on it, I've never had the same sense of being powerless to operate correctly a store with joomla and all its components. Knowing that I lost a lot of time to get a proper layout with my template.

Profitability, VM is very questionable. Even paypal Support refuses to help VM users (the tell to see on this forum to find a solution).  :o
In my place what would you do? Becoming a developer to use correctly VM? Why using open source CMS?  :-\

jenkinhill

  • UK Web Developer & Consultant
  • Global Moderator
  • Super Hero
  • *
  • Posts: 27099
  • Always on vacation
    • Jenkin Hill Internet
Re: Paypal (new API) problems
« Reply #47 on: June 06, 2013, 17:10:30 pm »
I think you are stuck because you are using an old version of Joomla and VirtueMart rather than the current versions. Updates in browsers and then php versions on hosts can cause problems, and recently PayPal themselves changed their protocols which have cause some old eCommerce software to stop working properly. In the current VM2 version the PayPal issues have been dealt with but there are no longer developers working on the 1.1 series as the CMS platform, Joomla 1.5 is no longer supported by joomla.org

I can't offer solutions as I no longer have any VM1.1.9 sites to test on.

A programmer may be able to get the system running again for you, but after a while it becomes no longer something that can be fixed without updating to the current VM version or as you say, migrating to another platform. Magento is really good, but needs a lot of time spent to get working properly - and even then you will have updates to deal with every couple of months or so.
Kelvyn

Jenkin Hill Internet,
Lowestoft, Suffolk, UK

Unsolicited PMs/emails will be ignored.

Please mention your VirtueMart, Joomla and PHP versions when asking a question in this forum

Currently using VM 3.4.3.9989 on Joomla 3.9.1 PHP 7.0.32
Testing VM 3.4.3.9993 on Joomla 3.9.1

AH

  • Global Moderator
  • Sr. Member
  • *
  • Posts: 2820
  • VirtueMart Version: 3.4
Re: Paypal (new API) problems
« Reply #48 on: June 06, 2013, 20:34:41 pm »
No matter what you choose, you have to be prepared to do some work on updates. We would all like the software to be stable and last for years but that is not going to happen!  E-commerce is changing relentlessly, we keep up or get out of the game.
regards
A

Joomla 3.8.13
php 7.1

lejeannotfr

  • Jr. Member
  • **
  • Posts: 59
Re: Paypal (new API) problems
« Reply #49 on: June 07, 2013, 10:38:56 am »
This is a strange argument you are defending: It is as if Microsoft or Apple refused to provide any updates to Windows Vista or MacOSX under one pretext that a new version is available on the market? What do you do in anticipation of your applications? Prestashop for example offers a support for the 4 last versions of its CMS edited since 2 years! At the opposite, all the Joomla community and VM says : "no upgrade = no support".  ??? This reasoning can not be applied to e-commerce, e-shops have specific constraints. If you had yourself a VM shop to manage every day, you may realize that you couldn't waste weeks working on updates and debugs while the problem concerns only one page in your shop! I started 2 years ago with VM 1.1.2, i have spent many many many days to update to 1.1.9, and solve problem with other components, modules, plugins, and problems with the server, and with the hosting provider, and more. I saw that some bugs meet in the 1.1.6 were always existing in the update 1.1.9. :o  And then you can confirm that updagrading to V2 will solve all problems?

Your never considered that when your shop is running and must be upgraded at this stage, you must upgrade all your applications : Buy a new template, buy upgrades of commercial components, spend weeks to resolve all problems and debug the new version that is supposed to be up to date, etc etc. My version works fine except for this little issue i raised in this topic. Ultimately what you suggest is to redo an entire and complete, brand new shop from scratch, and so work weeks to do so. This is why even if i should do so, i would prefer switching to another CMS and avoid having this kind of issues in the future.

Thanks for your answers.