Jump to content

reclipse3

Members
  • Posts

    60
  • Joined

  • Last visited

Everything posted by reclipse3

  1. This 1.6.0.9 problem wasted MANY hours of my time but I FINALLY figured it out. It has nothing to do with anything that has been mentioned above or in any other posts (I've read them ALL). The problem can be created and solved on demand by simply connecting to Prestashop Addons from the admin page. In the top/right of your admin page - if you're not connected already - you will see "Not connected to PrestaShop Addons". In this state, you will not see the problem. Most people probably don't even bother to connect to PrestShop Addons so they don't experience the error. However, if you connect your back office to PS Addons, the problem exists. Meaning, if you connect and then go to Preferences > Themes you will see, "Error during zip extraction". With this error displayed, you cannot add a new theme or change your site's logo. The quick fix is to simply log out of your admin area and then log back in, which will also disconnect you from PrestaShop Addons. SIMPLE. I tore the entire PS code apart searching for what was causing this issue and I would've paid someone $50 for the solution! P.S. Why is there only "Report A Bug" section for all other languages but english?? The report tracker only goes up to version 1.5
  2. * SOLVED! (1.6.0.9)* This problem wasted MANY hours of my time but I FINALLY figured it out. It has nothing to do with anything that has been mentioned above or in any other posts (I've read them ALL). The problem can be created and solved on demand by simply connecting to Prestashop Addons from the admin page. In the top/right of your admin page - if you're not connected already - you will see "Not connected to PrestaShop Addons". In this state, you will not see the problem. Most people probably don't even bother to connect to PrestShop Addons so they don't experience the error. However, if you connect your back office to PS Addons, the problem exists. Meaning, if you connect and then go to Preferences > Themes you will see, "Error during zip extraction". With this error displayed, you cannot add a new theme or change your site's logo. The quick fix is to simply log out of your admin area and then log back in, which will also disconnect you from PrestaShop Addons. SIMPLE. I tore the entire PS code apart searching for what was causing this issue and I would've paid someone $50 for the solution! I'm going to post it as a bug.
  3. Whenever I receive a new order email, the state is not showing in the address area. I can see the full address from the admin panel's order section, but I was wondering if anyone else is having this problem and/or if there was a fix (?). Thanks!
  4. Does anyone know what file I can edit to modify the email that I as store admin receive whenever a new order is made? I find all the other emails but not this one. Thanks!
  5. Yet another benefit of PS charging for a new/stable version.... users bickering would become irrelevant. I understand how easy it is to get off topic, but discipline needs to be exercised and tolerance practiced.
  6. My opinion is that PS should just come out with a new/stable version and start charging for it. Bringing in funds should allow them to provide much better support on a timely manner. If you're running a shop you're obviously making money and can afford to pay for such great software. The ones who aren't willing to pay can use oscommerce, or whatever other software you feel is better.
  7. It was my main point. I guess we weren't on the same page.
  8. I'm not blind or def to the future, in which is PS. Oscommerce is the past.
  9. Yet you're still using PS and contributing to their forum yourself..... After another 3 php versions, PS will still be more advanced than oscommerce because PS builds on the latest trends. Every script and new feature has bugs and PS is working on them just like oscommerce. If PS is being compared to oscommerce already, that says something in itself. oscommerce needs to dump the old backwards compatible coding and create a new platform with newer code (i.e. get with the times). That is because osCommerce was build when php3 was arround and has been backwards compatible ever since. PS is php5 only, wait another 3 php versions and lets see what the script looks like then. Furthermore, every feature PS has and lacks can be build in osCommerce, give and take a few bugs. The userbase is larger + the support is widely and thereforme much more stable. Like I said before, if the PS team would stop introducing new features but create a stable version first, would take more care about these forums and play a more active role on these forums + better moderating things would look much brighter......
  10. Perhaps there's many bugs, but that's because it hasn't been around as long as oscommerce. However, it would be nice if oscommerce had the look, feel and many of the latest features in shopping carts that you see with PS. I've setup a few oscommerce sites myself, with addons, custom templates, etc. but that script just feels as old as it is. PS is more cutting edge in my opinion.
  11. Yeah right. If PrestShop started charging tomorrow, I guarantee you wouldn't start using osCommerce or any other shopping cart script. PrestShop is hands down the best script out there for an ecommerce site. Charging for it would eliminate a bunch of the amateur sites out there that don't give the script proper credit. Then, the sites that would be left out there would be run by people willing to back it and the feedback would be much higher quality (eliminating a bunch of kids and/or people not really interested in running a shop, just messing around, etc.). A superior script should be worth something, is all I'm saying. If it would have some features that it is missing now, then maybe.
  12. I understand. However, it's worth $300+ at least.
  13. I created a new template and then removed the prestashop template. Now, if you click to view source code, it doesn't show the name prestashop anywhere. Of course people familiar with the script will know, but that's not who I'm trying to keep from figuring out.
  14. Some niche sites (like mine) have too much competition. If my competitors knew what shop software I was using, they'd quickly copy me. Prestashop is the best shop software available and in my opinion it shouldn't be free. I'd be willing to pay $300+ for the software. But that's just my opinion.
  15. So people don't see what shop I'm using via source code.
  16. Yes, in theory. However, that's why I asked. I didn't want to find out the hard way.
  17. Hello, I currently have Prestashop setup on a subdomain. If I wanted to change the subdomain, what would I have to do on the shop's configuration side (i.e. what files need to be edited)?
  18. UPDATE: Within the same file (blockviewed.tpl), adjusting the truncate numbers helped a little bit (but did not solve the issue). You'll see one truncate number for the product name and one for the product description (they simply tell the program how many characters to allow to be shown). I've set mine as follows: truncate:15} truncate:30 n=15} Though, everybody should adjust them to their own liking by trying a number, upload/refresh browser, then trying another and repeating. Paying attention to how the Viewed Products block looks each time. Hopefully this issue gets an official fix by Prestashop with the next update. Making it look like the New Products block would surely fix it.
  19. I no longer have an issue, as your fix worked. With your first edit it only fixed it halfway, as it only fixed the product's title and not the thumbnail photo (I was testing the issue by clicking the photo and not the title, so it only appeared not to work). But your second edit added the thumbnail edit which fixed it completely. The only problem I'm seeing now is that if a product has a long title, it runs over the second product's thumbnail pic in the Viewed Products block; the top product's title runs over the bottom product's pic and the bottom product's pic runs out of the block, onto the next block below (if there's a block below). I tried strategically inserting a space tag after the product's code, but that did not fix it. Any ideas? P.S. Long product titles are also a problem on the product's page, where it runs a second line and doesn't look too nice. You'll also see this with not so long product titles, but within a few subcategories deep, causing the path to be long.
  20. This new file edits a different line. Should we revert the first edit made from the previous file, and make this change only? Or do we add this edit the to first edit made, so that the file has been edited on two lines? EDIT: Actually, I see why it wasn't working with the first edit. Because your first edit only added the path to the product's title, and not the thumbnail. Your latest file edits the thumbnail to include the path. However, you may want to edit the file again so that anybody who comes across this thread knows to edit both lines. Thanks again for the fix! Side Note: I notice that the link actually shows two forward slashes in the path, but works nonetheless (e.g. yourdomain.com // productname).
  21. Great simple fix (for most of the problem)! However, the problem that still remains is with clicking a product that shows in the New Products block. I guess it doesn't work because there Prestashop doesn't give a "path" (but should - to the product's category/subcategory) when an object is shown in the New Products block. I wonder, could this same fix be applied to the New Product's template file?
  22. Am I missing something? Please check your code, as it appears to be the exact same thing.
  23. The problem is not happening on just some products, it's happening on any product I click on from the Featured Products block, the New Products block, or either of the Carousel mods (I have them both). It's not a problem when clicking a product from navigating the categories, or the Specials block. I just tried it with IE and everything works/doesn't work exactly the same. To be more clear, the problem is that if you click a product from either of the carousel mods, or Prestashop's Featured Products block, or Prestashop's New Products block, the URL isn't set properly for these items if you click on them from Prestashop's Last Viewed Products block. The path is absent and only shows the item part of the URL, not the entire item's URL path, so the link doesn't work. Just hovering your mouse over the item will show you the path in the bottom left corner of the browser without clicking it. So it looks like this has to be fixed in the core shop as well as some mods.
×
×
  • Create New...