Jump to content

PrestaShop Concerns


Recommended Posts

Hi

 

Sad to say that I am getting disillusioned with Prestashop at the moment. It seems that we have had a lot of upgrades lately but no fixes to problems that seem to keep reappearing. I have been using the platform for about 3 years now but feel as it becomes more updated it also becomes less efficient.

 

I have had a few posts regarding carts not being converted into orders which seem to have not been answered. I also have seen many others with the same issue and there does not seem to be an answer.

I have tried to create a voucher with a 10% discount which will not work correctly. Again I have found many posts on this subject with no answers.

 

I have a simple but okay shop and it is starting to finally get business but if it does not function properly, and I do not have the knowledge to put it right, its not really a lot of use if you have to keep apologizing to customers as to why it does not function properly.

 

Can anyone recommend another platform where i could transfer my products over fairly easily and is not to expensive to set up please.

 

Barry

Link to comment
Share on other sites

Barry,

 

Sorry to hear you are having problems. It makes for a long day I know.

 

After many years of upgrade experience (mainframe systems), the problem usually is in the realm of custom code being carried forward or a new behavior of the upgraded system. I see from your posts that you have custom behaviors. What ps release was is your current template written for, or did you purchase an upgraded template? Templates are really programs and must be compliant with your production prestashop release.

 

Maybe consider creating a fresh new base release, with your template, assuming it's compliant. Export your products into the new base and see what modifications if any you need to carry over from your existing system. You might be surprised that the old bug a boo's went away.

 

Suerte!

Link to comment
Share on other sites

I would disagree elpatron, it is the way that updating is done. It needs to be more unified and smarter. Currently what happens is new releases and code updates are rolled in to a new release. Which is great and everything, but it misses the point. Prestashop is great software, but I to find myself migrating away from it too.

 

!important

This is how to keep users

!important

When 1.5 comes out, road map to 2.0. It might already be in the works, I don't know. But let the 3rd part developers worry about adding features with modules. Focus on fixing the bugs. Don't come out with a 1.5.2 and other bs like that. Fix the bugs in a patch style. If it is not too late, add this to 1.5. People do not want to have to reinstall a whole store just to fix a bug. I do not have to delete windows and start over for the month security updates. I am willing to bet that almost 100% of the bug fixes for any one version would not break other areas such as themes. But when you add new features and change other things they do.

 

Think about it from a developers point of view, I charge someone several thousand dollars to make a store, then in a couple months when a new version comes out to fix the bugs in the old version, I have to reinstall and make sure everything works. This is costly and it will lose you developers. If I could just go to the back of the house and apply a patch that just affect a couple lines of code, then nothing would break normally. A perfect example would be with the ssl fix.

 

Basically what happens now is a version is dropped and the developers walk away from it, leaving Mike and others to sort out the mess. At some point, they get notified of the bugs and they roll the fixes into a new version. Leaving all other versions unfixed. It is abandonment strategies like this that keep OOS behind paid software and it is bad for the OOS community.

 

tdlr; Make a version, fix the bugs, make another version, fix the bugs, rinse and repeat.

Link to comment
Share on other sites

I do agree with you that there should be base release, fix1, fix...then one could apply fixes by release..IBM calls them puts (well in my day)..

 

as to whether you agree with my assessment of client migration...let's just agree to disagree...no auto-updater is going to carry forward client custom code...or fix non-compliant templates and modules..starting fresh and carrying forward required application is IMHO a very safe strategy.

 

If I one day become dismayed, I'd like to try cold fusion.

Link to comment
Share on other sites

oh, with custom code there is no telling what will happen. But you can write your custom code in a fashion to *help* it not break. Using overrides is good, also turning php on in smarty and doing something inside the template is good too. That way you do not have to change the actually code base if you want to do somethings.

 

Working off a base release just makes it more attractive to the people that develop on it for a living. Which is the customer base that Prestashop needs. I mean I understand proliferation works out well, but when you have a developer that will pay you several thousand dollars a year to be certified, it out weighs a lot of free users.

  • Like 1
Link to comment
Share on other sites

Thanks for the replies. As somebody who does not understand computer speak, most of what you say is not easy for me to understand.

 

I do get the jist of it though.

 

What DesignHaus42 says about getting the bugs fixed before any more updates is my point as well. If I read the forums correctly, there are to many of us non computer types who are getting frustrated and left behind because of frustration at the many bugs that seem to have crept in to the last few upgrades and not resolved.

 

It is a great concept and I enjoy learning but I need to have a functioning website to earn my income.

 

Barry

Link to comment
Share on other sites

×
×
  • Create New...