Jump to content

F.P.

Members
  • Posts

    58
  • Joined

  • Last visited

Everything posted by F.P.

  1. If I read the comment from TropischBruin that an order summary is not a big miss I am asking myself why all other shopping cart have such a function before order confirmation? If it is not a big miss, why do oscommerce, opencart, magento, zencart, xtcommerce, xtcmodified and all other ecommerce systems provide that. If it is not a big miss, why do those developers develop an order summary as standard function. PS is the only ecommerce system, which does not provide that. The customer sees just the amount and has to pay for whatever. But it is not a bug, it seems to be a feature!
  2. The biggest problem of PS is that there is no order summary before order confirmation. That is something important and therefore I did choose opencart. There are some people in the German forum to develop such a module to add that essential functionality into PS and as far as I can see, the problem is that every payment module needs to be included somehow to offer that functionality. That means that if someone adds a new payment module the order summary needs a code change. That tells me too, that a function like order summary cannot be integrated with a module. A core code change is necessary and there is zero answer until today from the developers.
  3. But in the case of OpenCart I did buy the UPS Shipping, which works like a charm for about 15$ and the payment modules are not very expensive too. I was even able to copy an existing one, changing a few things in the coding (I am not an excellent programmer) and now I have a module for Directebanking. Another advantage is that the code is xhtml strict and the template engine is much faster than smarty. Opencart has the advantage that some essential functions like agree to privacy and especially an order summary before the final checkout confirmation are already built in. I was even able to get my old osc module for cron import from a distributor to work. I do not say that Opencart is perfect, but the core functions for legal things are already there and the small community is very helpful if there are questions. Does Presta offer built in product reviews, product ratings, downloadable products or cross sell? I like Prestashop too but if someone wants to migrate from OSC to a new system it is easier to do it from OSC to Opencart as to migrate to Prestashop. There is even a contribution to accept osc customers passwords, so the important thing of migrating customers and orders is pretty easy. A disadvantage of Opencart is the layout in the admin section, but that can be done by css and template change.
  4. Miva is not Open Source and Magento is very difficult to configure. Additionally it is still slow. The only advantage is the InnoDB but it is not a killer argument. Oscommerce and Zencart (just a fork of oscommerce) lack of a developement perspective. Prestashop is robust with a lot of functions but it still has a lack of core functionallity in the checkout process (order summary before confirming order). But there is another shopping cart (open source) worth to mention: OpenCart.
  5. Does the UPS Module work, if used in conjunction with the USPS module for european shops or is it for US only?
  6. Man sollte eben die Informationen über die InnoDB nicht nur selektiv erwähnen, sondern auch den Rest erzählen. InnoDB beinhaltet eine Crash-Recovery Funktion (MyIsam eben nicht). Die Funktion, die dafür verantwortlich ist, dass bei Löschung z.B. von Kategorien dafür verantwortlich zeichnet, dass dies auch durch alle Instanzen stattfindet, hat was mit foreign key constraints zu tun, dies ist eben nur in einer InnoDB vorhanden. Zurück zu den Modulen: Es ist ja schön, dass bzgl. Rechtssicherheit einige Bemühungen von externen Entwicklern stattfinden, dies sollte aber Bestandteil des Shopsystems sein. Das Ausweisen der Mehrwertsteuer und das Ausweisen des Rechnungsbetrages in seiner Gesamtheit vor der Bestellung ist in OSC schon ewig lange drin, auch Magento kann das (ohne Zusatzmodule). Magento beinhaltet (und zwar funktionstüchtig) alle relevanten Zahlungsarten und ebenso Versandmodule, die eine Live-Kostenberechnung erlauben. Mir gefällt zudem auch nicht das Herumgefrickele mit Smarty, aber das ist Geschmackssache. Es liegt mir fern auf Prestashop herumzuhacken, allerdings hat drdre3 schließlich auch keine Hemmungen auf Magento herumzuhacken.
  7. Das sehe ich nicht so. Prestashop ist momentan für den deutschen Markt nicht geeignet, weil abmahngefährdet. Bzgl. Modulen ist dem auch zu widersprechen. Magento hat z.B. gut funktionierende Versandmodule eingebaut, es gibt für fast alle Zahlungsanbieter entsprechende Module und die API ist wesentlich besser dokumentiert, als dies bei Prestashop der Fall ist. Ebenso ist die InnoDB von Magento wesentlich fehlertoleranter und sicherer. Beispiel: Löscht man in Magento eine Kategorie, die Unterkategorien beinhaltet, im Admin, so werden auch die Unterkategorien gelöscht. Ähnliches gilt auch bei den Produkten. Dies gilt so für Prestashop genausowenig wie für oscommerce und dessen Derivate. Es bleiben "Leichen" in der Datenbank, die nur sehr aufwendig zu finden und zu löschen sind. Dies nur mal als kleines Beispiel.
  8. Was hat Prestashop funktionell so besonderes, dass man überhaupt darüber diskutiert. Eigentlich ist nur das Smarty-Template wirklich gut, das Design ist sehr gelungen. An den meisten anderen Dingen: funktionierende Zahlungsmodule, Real-Time-Versandmodule usf. fehlt es doch, mal ganz abgesehen von den rechtlichen Dingen.
  9. Als zugegeben kostenpflichtige Alternativen gibt es z.B. noch cs-cart und x-cart. Diese beinhalten allerdings noch jede Menge Zahlungs- und Versandmodule und noch weitere Module, die den Preis von um die 265 US-Dollar allemal wert sind. Bei kostenlosen Shopsystemen gibt es auch noch die Community Version von Oxid, der es allerdings, wie Prestashop auch, an Zahlungs- und Realtime Versandmodulen fehlt. Wenn man die Foren mal etwas durchforstet, gibt es offensichtlich bzgl. Bestellbestätigung auch Probleme in den Niederlanden, den USA, in Kanada. Ich kann mir auch nicht vorstellen, dass es in vielen der übrigen EU Ländern möglich ist einem Kunden einfach zu sagen: Zahle Betrag xyz ohne aufzulisten, wie sich dieser Betrag zusammensetzt.
  10. Richtig ist, dass Prestashop momentan nur für den französischen Markt geeignet ist, eben wegen der wie ich auch finde grotesken Gesetzeslage in Deutschland und weil einige Rechtsgelehrte das Internet bzgl. Abmahnungen als ständig sprudelnde Einnahmequelle entdeckt haben. Da wir aber nun mal diese Gesetzeslage haben, es betrifft auch nicht nur Deutschland, ist Prestashop eben eine ungeeignete Shoplösung für die betreffenden Märkte. Allerdings sind Magento bzw. oscommerce diesbezüglich eben kompatibler, ebenso andere allerdings kostenpflichtige Shoplösungen. Ich versehe es aber nicht, dass das Entwicklerteam nicht in der Lage ist, fakultativ das, was im Shopping Cart angezeigt wird, noch einmal vor der Bestellbestätigung abzubilden.
  11. Es lohnt sich nicht in dieses System Arbeit zu stecken, solange die Entwickler der Überzeugung sind, dass sie den Nabel der Welt erfunden haben. Prestashop gibt es ja schon seit einiger Zeit und die Ausbeute an Modulen ist verschwindend gering. Wenn es etwas taugen würde, dann würden die Payment Provider schon längst auf den fahrenden Zug aufgesprungen sein. Für Magento gibt es inzwischen dort zahlreiche Module und zwar kostenlos. Bzgl. Versand funktionieren die dort integrierten Module inzwischen gut (z.B. UPS). Es gibt auch noch andere kostenlose Shop Systeme, von OScommerce über Zencart bis zu Virtue Mart und Oxid PE, die entweder schon fertig für den deutschen Markt inkl. Rechtssicherheit out of the box funktionieren oder für die entsprechende Module vorliegen. Ich habe schon im deutschen Forum gepostet, dass sich, nach ziemlich barscher Anmache eines Entwicklers des PS Teams bzgl. Datenbankeignung für automatischen Massenimport für mich Prestashop erledigt hat. Externe Entwicklung ist unerwünscht, darauf lässt auch die fehlende Dokumentation zum System schließen. Mir wurde jedenfalls geantwortet, dass ein Massenimport gefälligst über die PS Classes zu erfolgen hätte und ob ich schon mal was von entity gehört hätte. Wie schön, dass dann gleichzeitig das PS System überhaupt nicht dokumentiert ist, es gibt lediglich eine Übersicht über die Datenbank, also muss ich ja davon ausgehen, dass ein solcher Import dann auch über die Datenbank direkt erfolgen kann, da ja nur diese marginal dokumentiert ist. to kdk: volle Zustimmung, das ganze ist schon dabei sich selbst zu erledigen.
  12. Yes, the mentioned shop solution costs money. I agree. but you can have that functionality and even more with magento. And that costs nothing. Do you really think, that the developer team of Prestashop does not want to earn money. And indeed I would pay for special modules or designs. But the problem is that the core is still problematic. Those legal issues prevent Prestashop from gaining a bigger audience, what would increase the interest for templates or modules. If about 70 % of the countries cannot use Prestashop, what kind of future can have such a project? As you can see, Magento offers a lot of working modules (Shipping and Payment) and the developers as well as external developers or designers start to develop something. I like Prestashop but I cannot use it because those legal issues prevent it. It is possible to hack the source code to gain some of the desired functionality. But if you hack the core files for that purpose: What about future updates or upgrades? Actually it is not sufficient to change something in the template to receive those functions. And you have to hack the database, rewrite the complete shop system to bring it to the functions Magento or OScommerce have now and since a couple of months or even years.
  13. Dear Tropisch Bruin, I am very much in doubt about the further developement. I did post three bugs in the bug tracker, one about the order process, one about Javascript Buttons (what happens if a customer does not use Javascript?) and something about the product image management of prestashop (i.e. renaming the images and loosing the original path). The first thing is marked in the Bug Report: needs more information The second one: Cancelled (it is not a bug, it is a feature) The third one: deleted Further questions? Just one link:http://static.interspire.com/isc-demo/index.html That is how it should work.
  14. Dear AnimeCYC, the following errors occur in the shop frontend: Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 111 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 195 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 202 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 133 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 181 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 111 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 195 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 202 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 133 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 181 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 111 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 195 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 202 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 133 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 181 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 111 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 195 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 202 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 133 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 181 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 111 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 195 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 202 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 133 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 181 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 111 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 195 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 202 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 209 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 133 Notice: Undefined offset: 0 in /Applications/MAMP/htdocs/shoppresta/classes/upsRate.php on line 181 And in the shop backend I receive the following errors: Notice: Undefined variable: error in /Applications/MAMP/htdocs/shoppresta/modules/blockups/blockups.php on line 64 Notice: Undefined index: submitUPS in /Applications/MAMP/htdocs/shoppresta/modules/blockups/blockups.php on line 76, Notice: Undefined index: submitShipping in /Applications/MAMP/htdocs/shoppresta/modules/blockups/blockups.php on line 78 and the same for line 335 and line 273
  15. Just did try it with the SVN-Version. It does not work with the SVN Version. I receive a lot of errors with undefinded offsets in upsRates.php. And I did try it with the official version: Result is a blank order page.
  16. I did download the new module version and in my download there is still upsRate.php in the classes folder. In the sql file there is an insert: CREATE TABLE IF NOT EXISTS `PREFIX_ups_method` ( `id_ups_method` int(10) unsigned NOT NULL auto_increment, `upsName` varchar(255) NOT NULL, `xml_code` varchar(255) NOT NULL, `upsActive` tinyint(1) DEFAULT 0 NOT NULL, `zone` varchar(255) NULL, `freeShipping` tinyint(1) DEFAULT 0 NOT NULL, `id_carrier` int(10) NOT NULL, PRIMARY KEY (`id_ups_method`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1; In the readme.txt there is: CHANGE LOG :: Version 0.2.1 Optimized caching Overhaul of code Fixed free shipping Fixed minor OOP discrepancies Updated upsRates.php to contain all code related to module Reverted Cart.php back to its original state Removed free shipping check from Cart.php (temporary) Seems it should work without the zone definition of Prestashop itself. And it should work with the original cart.php without patching it.
  17. Just did take a look at the csv import tool. As far as I can see there is no possibility to import subcategories with products. You should first create those subcategories manually or by import with the csv categories import. There is something called parent category. The parent category is what you already did create before. And for the new subcategory it seems to be the field Name. but because Prestashop does not allow to export something, I cannot tell you what to put into Parent Category. It could be the Category Name of the main category or it could be the id. If those subcategories have been created manually or maybe with the category csv import tool try to create a csv for the product import and put the category name (in your case the newly created subcategory name) into the field Categories (x,y,z...). Best way to try out is to create just one subcategory and import just one product into the new subcategory to see whether it works or not. Hope that works. There exists a feature request post dealing with the problem of creating categories and subcategories which could have the same name. Categories and subcategories should be identified by an id and not by the name. Otherwise the csv import can create very messy results.
  18. Prestahop seems to identify categories by name (not by id). So You should create an import file with the name of the desired category, which already exists as a category. Be carefull to not use the same category name for subcategories, because prestashop (as a running bug) sorts products into categories by name and not by id, as it should logically be.
  19. Not just Canada and the US. The majority of the countries do need that function before confirming the order. There is no other shop system with such a lousy order process. The legal issues start with those javascript buttons (what about Javascript deactivation in browser and legal discussion afterward) and end with illegal order process. Very nice.
  20. Today I received an answer for my posted Bugs, that it is a feature request with should be posted as a feature request and not a bug. Maybe it is the 1. April, so the developers joke a little bit around.
  21. Dear Tropisch Bruin, I just did wrote something into the Bug Tracker http://www.prestashop.com/bug_tracker/view/1633/ Most things are for legal issues in Germany but as I did see in some other posts for a lot of other countries too. Maybe You can add a comment to my Bugtracker Post with additional requests. So we may or may not see whether the developers do care about or not. If they don't care about it is better to choose another shop system.
  22. Also, wenn es nur um die Anzeige der Mehrwertsteuer geht, gibt es noch einen einfacheren Weg. In der Cart.php folgenden Eintrag suchen: 'total_products_wt' => number_format($this->getOrderTotal(true, 1), 2, '.', ''), dort unten drunter: 'total_products_wot' => number_format($this->getOrderTotal(false, 1), 2, '.', ''), einfügen. Danach in shopping-cart.tpl (unter Themes) unterhalb von {l s='Total products:'}{convertPrice price=$total_products_wt} folgendes einfügen: {l s='gesetzl MwSt:'}{convertPrice price=$total_products_wt-$total_products_wot} Bei mir funktioniert dies zumindest in der neuen SVN Version problemlos.
  23. Schön, dass eine Antwort kam. Wenn es nur mit der Anpassung an die Rechtssicherheit getan wäre. Allerdings befinden sich in der Datenbank selbst einige Features, die es bei vernünftigem Nachdenken nicht sinnvoll machen, dieses Shopsystem zu nutzen. Ich habe schon auf die sehr merkwürdige Verwaltung von Produktbildern öfters hingewiesen, ebenso auf die Kategorienverwaltung und die Indexierung, um nur zwei solcher Features zu nennen, die selbst in der Altversion von OSC besser und zukunftsträchtiger gelöst sind. Die Datenbank ist das eigentliche Herz des Shops und wenn dies von Anfang an schlecht konzipiert ist, dann kommt es schnell zum Kollaps. Mir scheint es so, dass mehr Wert auf ein hübsches Outfit des Frontend gelegt wurde, als auf das Backend und die Datenbank.
  24. Ich habe mir schon OSC3 angeschaut und es macht jetzt schon einen stabilen Eindruck. Zumindest sieht die Database so aus, dass keine gravierenden Denkfehler eingebaut sind. Zudem ist die Community nicht tot, es gibt, obwohl erst Alpa Status, fast täglich schon irgendwelche Module. Auch wenn Harald momentan der einzige Entwickler ist, der am Core von OSC arbeitet, so tut er dies doch zumindest gut. Was nutzt mich hier, wenn ich die Bilder von 5 oder 10 Entwicklern sehe, die kaum Antworten im Forum liefern und ansonsten auch nicht viel mehr als ein paar zusätzliche Gimmicks entwickeln wie Statistik Module. Die sind wirklich für den Rest Europas erst dann relevant, wenn man mit dem Shopsystem live gehen kann, ohne direkt eine Abmahnung zu kassieren. Für mich sieht Prestashop auf dem localhost oberflächlich schön aus, mehr aber auch nicht. Man kann sich auch eine entsprechende interaktive Powerpoint-Vorlage im Presta Stil erstellen, die erfüllt momentan den gleichen Zweck, wie das Shopsystem selbst. Nutzlos für den Rest Europas.
  25. Dear Hoodgrown, let me just explain what are the legal issues for a lot of countries. 1. A new customer has to agree to the terms of privacy and he must have the possibility to choose to have newsletters or not. There is no option to agree to the terms of privacy in Prestashop. The agree to receive newsletters is available but the implementation is lousy. You do not have to click on the little button (to hit the button), just click outside and the button is selected. 2. In a lot of countries, the customer must see the complete order with tax, shipping costs a.s.o. before confirming the order finally. That does not exist in Prestashop. You, as a customer, see just something like: Pay the amount of .... There are structural problems in the database: i.e. categories and images and a few other things. Just take a look at the method prestashop treats images. It automatically changes the names of those images to (category_id)-(product_id).jpg. If You work together with some wholesellers and You would like to actualize your products by a cronscript, which puts it directly into the database instead of the slower import in the admin backend of PS, You can't import pictures in Prestashop, because Prestashop needs self changed image names and not your original image names with the path where to find the images. I do not like to import thousands of images and match them to fit with the scraptastic Prestashop database.
×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More