Jump to content

Paul C

Members
  • Posts

    801
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Paul C

  1. The bug tracker is your friend. http://www.prestashop.com/bug_tracker/view/7579/ It even has a search facility Paul
  2. I'm reading this post with interest. I have had no problems whatsoever when recently upgrading a site from 1.2.4.0, so am not really sure what the issues are that people are having. Are there problems? Yes. The CMS issue as one example, was identified a good while back and is in the bug tracker (a free professional tip is to have a good look in there for open bugs relating to the version you intend to upgrade to, particularly ones that relate to features that are essential for your store). CMS SEF links redirect to site root Report #: 7579 Date created: 08 Feb 2011 at 15:48 (UTC+1) Themes likely need major work or they'll either fail, or you won't be able to properly take advantage of the new features. They always do. The other side is down to proper change control and backups. I'm sorry if this sounds harsh, but a backup that doesn't revert you back to where you were before you started isn't a backup - it's a waste of time. I suggest that if you don't have a proper, clean database backup, then unless you can persuade your hosting company to restore it for you from a point before you ran the upgrade script, you're stuffed. There have been many people testing with the latest RC versions (and some of us using the SVN versions and updating daily) and reporting bugs - it's a way of contributing to the project and results in a better product for everyone. This is best done using a real site on a test server. It also lets you iron out any major problems before affecting your production site. Complaining in a forum sadly, is likely going to be ignored I'm afraid, as the developers will concentrate on reported bugs as their first priority. Paul
  3. It's likely related to the layered navigation module. I'm not sure I would recommend anyone using it right now as it is really fairly experimental (and pretty much says so in the module config screen). Paul
  4. You can group CMS pages in 1.4, then displaying the category lets you list the pages within the group how you want, albeit as a "page" of links, not a list you can use anywhere. I'm sure it would be easy enough to create a configurable module to list the links in a group though. I've been playing with creating "plugins" for smarty to aid theme development and am working on a framework to easily allow people to add their own. I guess an analog in Wordpress would be the theme functions (functions.php). Generating a ul from the links in a CMS category might be a good one to look at implementing. It would then be a case of using something like: {list_pages cat='2'} Anywhere in your theme you like, and it would generate the markup. Paul
  5. I suspect that as part of the upgrade extra modules have been added to the modules directory which are relying on a class that doesn't exist in the older version. I would compare the 1.3.x installation files with what's on your server and delete any modules that are either not added by you or do not exist in the 1.3.x install. Paul
  6. Are you getting the same error as the original poster, or a different payment error message? Paul
  7. This is hosting related, not really related to the cart. You can get around it by modifying the validation.php file, or you can find out from your hosting company why they don't let you make an ssl cURL connection. In /modules/paypal/validation.php find the following: // Getting PayPal data... if (function_exists('curl_exec')) { // curl ready $ch = curl_init('https://' . $paypalServer . '/cgi-bin/webscr'); // If the above fails, then try the url with a trailing slash (fixes problems on some servers) if (!$ch) $ch = curl_init('https://' . $paypalServer . '/cgi-bin/webscr/'); if (!$ch) $errors .= $paypal->getL('connect').' '.$paypal->getL('curlmethodfailed'); else { curl_setopt($ch, CURLOPT_POST, true); curl_setopt($ch, CURLOPT_POSTFIELDS, $params); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HEADER, false); curl_setopt($ch, CURLOPT_TIMEOUT, 30); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); $result = curl_exec($ch); if (strtoupper($result) != 'VERIFIED') $errors .= $paypal->getL('curlmethod').$result.' cURL error:'.curl_error($ch); curl_close($ch); } } You'll notice the two lines that have: $ch = curl_init('https://' . $paypalServer . '/cgi-bin/webscr (etc.) Try changing the https to http. Paul
  8. Check the permissions on the payment module. Specifically, if the directories (/modules and /modules/paypal) are set to 777 change them to 755. If the files are set to 777, then change them all to 644. If this resolves the problem, then you should go through all the directories and apply similar changes. Paul
  9. Yes that's a possibility for the future. They do use a "framework" of sorts. In that it's loosely an MVC architecture and much closer now to this than before. Pages are now "Controllers" rather than flat php files with the core included in them, "Views" being handled via smarty and the template files and the "Models" are the core objects themselves. Definitely getting better and I feel that the admin side is more a question of timing than anything else. You can actually do quite a lot in Admin terms just by inheriting the AdminTab class and pointing it at your object, but at the moment customising via class overrides isn't available. Paul
  10. Mrk, Yes, you'll find that in 1.4 you can likely follow your original plan without any modification to the core. To date you still can't easily modify existing admin screens without affecting at least some core files - but as in your approach you can create your new tables and classes and link them to existing objects by storing the db id in your new table/object. It all depends if your new admin screens make sense stand-alone, or if functionality absolutely has to be integrated into the screens for the area it's affecting. Paul
  11. Deyell, Attached is a slightly modified version that first tries cURL and if that is present and fails, then it should fall back on trying to use fsockopen. This may still not help you should your host not allow fsockopen.... I've modified it off the top of my head without testing (don;t have anywhere suitable to hand to test right at this moment), so no guarantees, but let me know and we can fix if required. Paul validation.php
  12. Melinda, To fix the admin tabs you just need to restore the tables: access, tab and tab_lang from your 1.4.0.2 backup I haven't noticed problems with the orders and customer tables. What happens to those? Paul
  13. You got a reply to this same question here earlier today: http://www.prestashop.com/forums/viewthread/91790/upgrading_prestashop/solved_upgrade_failed_cant_resume_to_the_original_status I will repeat that you would only set a directory to 777 if you absolutely have to, and I suspect from what you've posted that you do not. Paul
  14. It's likely that setting the permissions to 777 is what's actually causing the http 500 error. Try setting the directories to 755 and files to 644 and that should fix it. Some servers don't like 777 on directories or on files (and files should never be an odd numbered permission unless they're executable, which php files are not). Paul
  15. Fair comment. I'll try and be more newbie friendly in future Paul
  16. The only thing I noticed deyell is that you're making the same call twice (probably due to the copy/paste): $result = @curl_exec($ch); $result = curl_exec($ch); I would delete the second one and test again, but otherwise it looks fine. Paul
  17. Well in most cases that's because the discussion is about general development issues. In this thread, for example, It's impossible to specify what the filename or the linenumber to modify in ometical's example would be as he doesn't specify which module(s) he would like to hook, and we're talking about adding a new class member function (the choice of where it's added would be up to the person making the change - it could be anywhere in the class definition). In all honesty I'm not likely to tell anyone which Prestashop core files to hack to get something to work, as that is just setting them up to spend hours asking questions on here later when they next try and upgrade and find that they can't. I have always taken the approach that none of the core files should ever be modified to produce custom behaviour; and if you're going to modify them, then you should know what you're doing and not have to ask or you'll be forever dependent upon others goodwill to bail you out. Another issue is that for many of the core supplied modules the version numbers haven't been updated even though the actual code in the modules has changed (through bug fixes - some of which have been major). This means that unless you have exactly the same "version 1.1" of the module that's under discussion, then the line numbers (and some of the specific code quoted) will be meaningless. In saying the above, if there's ever a case where you feel that any of the information I supply is insufficient, then you can always ask for clarification and I may or may not notice and reply Paul
  18. Rats. What version of Prestashop and the paypal module are you using? And make sure that in your edited file the line: @curl_setopt($ch, CURLOPT_SSLVERSION, 3); Is present. Paul [edited]
  19. I'm wondering if you called your override class "_Cart.php" as it would have to be "Cart.php" for it to work.....plus it must be in the override/classes directory i.e. /override/classes/Cart.php Paul
  20. All you need to do is edit the (or assign a) selector for it . The exact css will depend on your theme though. Paul
  21. All you need to do for that is edit the theme - product.tpl - and use h1 instead of whatever it is at the moment. I'm not sure having multiple h1's on a page is a good idea, but then I'm a purist If you want it on the breadcrumbs, then you just edit breadcrumb.tpl. Pretty easy really. Paul
  22. The fix is actually tiny, so I'll publish what I did (in general terms) as there's just too many versions (and variations on versions) to provide files for every case: In the (non-api) paypal module, the issue is in validation.php. Taking 1.7.1 (as in the 1.7.1 in the 1.3.6 distribution which is probably very similar to the one in 1.3.4 but maybe not identical!) as an example. Around line 32 there is: curl_setopt($ch, CURLOPT_POST, true); curl_setopt($ch, CURLOPT_POSTFIELDS, $params); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HEADER, false); curl_setopt($ch, CURLOPT_TIMEOUT, 30); curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); $result = curl_exec($ch); All we need to do is to force the SSL version, so that block of code becomes: @curl_setopt($ch, CURLOPT_POST, true); @curl_setopt($ch, CURLOPT_POSTFIELDS, $params); @curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); @curl_setopt($ch, CURLOPT_HEADER, false); @curl_setopt($ch, CURLOPT_TIMEOUT, 30); @curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); @curl_setopt($ch, CURLOPT_SSLVERSION, 3); $result = @curl_exec($ch); You'll note that I've also added the '@' signs to the function calls - they're not essential but good practice that's been adopted in later versions anyway. Hope this helps, Paul
  23. Having thought about it further I've changed my mind on having the category ID in there just to fix one small case (someone taking the time to manually manipulate the urls). Why? Sitelinks for one - if you have "proper" category names then this gives Google the opportunity to automatically generate them with sensible values. I now think it would make the issue worse rather than better - sacrificing one (little used) user interface issue with another much greater one. There are many examples of sites where removing portions of a url can cause "unexpected" behaviour. I think a better (more generic) approach would be to handle such situations within the context of the 404 page/controller, rather than tampering elsewhere. Paul
  24. You replace settings.inc.php not config.inc.php -- that could be the problem... Paul
×
×
  • Create New...

Important Information

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