Jump to content

Paul C

Members
  • Posts

    801
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Paul C

  1. The problem is that the relative path you're likely using is assuming that the code is executed in the module folder, so you're referencing relative to that - however that isn't how modules work as they are in the main eval'd The answer may well be in the error message I also think that in the 1.2 distribution the PayPal API module may well reference some classes that are in the module directory - take a look at that maybe? Paul
  2. If you're not taking UK cards (e.g. Maestro) then all you need is the DirectPayment module and the PayPal express checkout one from the new PayPal API module. You MUST offer express checkout if you use Direct Payment as per PayPal's WPP terms of service. The module on my site works fine, although it does lack the expiry date and issue number fields that would have to be added for UK cards. Paul
  3. I wouldn't recommend modifying the original - just makes the next upgrade a pain to be honest, but yes, if all you want to do is use the same css but without the javascript, then that will work just fine. Paul
  4. If you look at the Free Prestashop Modules page you may find something else you like too Glad it worked for you. Paul
  5. My apologies I read into your post that you'd switched to using your PC for testing - and noted that you're running magento on that domain. Please remember that I, like you, am a user of this software not one of the developers, so am only trying to help in the spirit of "community". There is obviously something about your server configuration that Prestashop doesn't like - and I have an interest in finding out what that is, fo my own education too. You say that there shouldn't be a .htaccess file in there however the error in the log extract you posted: Suggests that mod_rewrite is being called at some point. Paul
  6. * Make a copy of the files /modules/blockcategories/blockcategories.php and /modules/blockcategories/category-tree-branch.php * Place the copy of these files in /themes/modules/blockcategories/ * Edit those two files to produce the markup you require. I suspect that just changing the class names and id's will be enough to get you most of where you want to go, as by default all it's doing is generating nested unordered lists - it's jQuery that is making it "dynamic" based on the class/id of the elements. Paul
  7. Not sure I can offer you much help as you've now changed server which likely will cause other problems (the callback from PayPal will need to be able to make a connection to the webserver on your PC, so you will need to configure it appropriately to allow that). As I said the php errors you posted above lead me to believe that there are a few server configuration issues, so for example with the API module the error: Will cause it to fail as it needs to use the mcrypt library which appears to be missing. Paul
  8. As of version 0.6.3 I've used my convention for creating configuration values etc. in that module, so actually it's even easier than it was before to create a clone. In essence the process to create a clone called addstuff2 would be (assuming you've made a copy of the module directory locally): * Rename the addstuff directory and the files addstuff.php and addstuff.tpl to addstuff2, adstuff2.php and addstuff2.tpl * In your addstuff2.php change line 2 from: class AddStuff extends Module to class AddStuff2 extends Module * Again in addstuff2.php change line 9 from: $this->name = 'addstuff'; to $this->name = 'addstuff2'; * In addstuff2.tpl replace each occurrence of addstuff to addstuff2 i.e. <!-- MODULE Addstuff2 --> {$addstuff2_code} <!-- /MODULE Addstuff2 --> And I think that should do it :cheese: You can get the most recent version from the AddStuff module page Paul
  9. OK Karin, which module from my site are you using? The one I would suggest you use is: http://www.ecartservice.net/08092008/beta-v2-paypal-module-prestashop/ This one should add extra messages in the back office which may help us determine what is going wrong. I would suggest that you uninstall the current version and then install that one (the above module completely replaces the default one) - as the install function does set up some required elements. Paul
  10. The answer to your question isn't an easy one I'm afraid. You may need to look into your local laws to determine what steps you should take to ensure privacy and even what data protection reporting you may be subject to (depending on the information you gather at registration). Many people might expect a reputable organisation to protect their name/address details using an encryption technology on their website - others will not care Paul
  11. Those errors are most likely server configuration errors. Are you running with friendly urls? If you are, then delete the .htaccess file(s) you've created and try again. The error "Request exceeded the limit of 10 internal redirects" is a sure sign that you've created rules that will never resolve. Paul
  12. Have you searched the forum pluggyboy? :cheese: Paul
  13. Can I ask which version of Prestashop you're using, and was it a fresh install (and database built from scratch) or an upgrade? The ‘Â’ looks to me like a character encoding issue. Pul
  14. I'm not 100% sure I'm following what you're trying to do, maybe: 1) Customer is referred to site via an affiliate, so capture the cart_id and affiliate details (from a cookie?) in a table 2) Update this table with the order status changes to track sales progress etc. 3) Produce reports based on this table I'm assuming that there's a reason you can't use the referral module that comes with PS? The only puzzle I guess is which hook to use to do (1) as far as I can see? Paul
  15. What is the address of the (store) test customer you're using? It doesn't have france as the country by any chance does it? Paul
  16. This has already been worked through in this forum. It can be any of several issues but all are easily solved If you post the actual errors that you see in the integration console then that will help. Paul
  17. My utmost apologies - you are indeed correct. My mistake - I was looking at an older version, and you are indeed correct that they have left what looks to me -- like their debugging code in there. (Note that I have nothing to do with writing the core PrestaShop code). I upgraded the test store to 1.2.1.0 via a shell login and hadn't sync'd the local copy on my machine. I'm happy that us (3rd party) developers could use this to see what's going wrong with our code, but as you say it's a BIG no for production code. I would be happy if those were replaces using trigger_error() -- that way the error condition can be logged correctly and we're all happy I've attached a version of the mysql class file that uses this technique, for anyone who is concerned about using the original. Paul MySQL.php
  18. Sorry rocco, other than minor changes such as the one you're suggesting there isn't an "easy" way. I wouldn't advise messing with the Link class as it could do more damage elsewhere, out-weighing any benefit. Are there specific issues regarding the upgrade that you fear? :-) Paul
  19. La première approche est la bonne, mais il semble que la base de données utilisateur que vous avez créé ne l'était pas. Vous devriez être capable de créer un autre utilisateur. Un problème avec justhost? Paul
  20. Laws and regulations regarding the protection of your customer's information will vary. I believe that a dedicated SSL certificate is indeed a sign that you are a legitimate, serious business -- so I believe that it's a small and worthwhile cost. Installing the actual certificate on the server shouldn't present any problems at all, but you'll need to be careful with regards implementing in your store, and make sure that any additional scripts, images etc. that you use are properly referenced (i.e. if they are external to your site, then make sure they use https when they are presented on a secure page). Good luck! Paul
  21. Er, just where exactly are you seeing the queries? The only lines I see in the MySQL class that use die are in the connect() function (called way before you're in a position to run any queries at all): 22. die(Tools::displayError('The database selection cannot be made.')); 25. die(Tools::displayError('Link to database cannot be established.')); 28. die(Tools::displayError('PrestaShop Fatal error: no utf-8 support. Please check your server configuration.')); If you've properly configured your SERVER then you shouldn't be displaying PHP errors (although you may want to silently log them to a log file) either. You should just show a blank screen. Prestashop will try and impose this on your store, although on some servers it will not be allowed to turn error display off. Paul
  22. Right, it appears that the 1.2.1.0 update broke my version again, so attached is 1.4.4 (I'll update the first post in the thread I think with the latest version, and remove all the old ones to prevent confusion). This one should work with or without "friendly" urls in both 1.2.0.x and 1.2.1.x I've also added the urls for the images, I guess you can always prevent them being crawled with robots.txt should you choose to -- although it will cause errors/warnings in webmaster tools if you do. Paul gsitemap_1_4_4.zip
  23. Grif, I think you've confirmed that the 1.2.1.0 sitemap still doesn't work, but now we've added images that don't work either I don't think adding the images to the sitemap helps us a great deal to be honest -- see my previous post. Paul
  24. It was really written for 1.2 onwards, so the format of the tags has obviously changed from 1.1 -- it's almost impossible to keep things working across the versions due to the amount of change involved in each upgrade I'm afraid.
×
×
  • Create New...

Important Information

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