Jump to content

Apium

Members
  • Posts

    111
  • Joined

  • Last visited

Posts posted by Apium

  1. I can add a product to the cart, yes. So that works.

     

    Now, about the URL format. Like I said before, there are modules for this.

     

    Regarding changes in the product details: it is better to extend PrestaShop than to copy a page and place it somewhere else. That way, you have way more flexibility too. Are you going to make each and every product page static? The sole amount of work warrants writing some code to add custom code in appropriate hooks

     

    I'd advise against copying the page to a different location, and rather just extend Presta to suit your needs.

  2. From http://www.webhostinghub.com/help/learn/prestashop-15-tutorials/performance-and-security-15/using-security-tokens,

     

    When your customers login to your website they are opening a database session.  This session is typically shielded by the fact that your user is connecting to your shop using a secure login.  However, an addtionally option called a security token can be added so that every connection that your customers make to your shop utilizes a unique security token providing yet another security layer.  This option is used to ensure that the session created by your login cannot be duplicated.  Each session will be separated by the unique token. 

     

    I have, however, never quite seen those 'tokens' in action on the front-end. Could you tell me how I can reproduce your problem?

  3. You should get a bit more acquainted with image formats. Your current format, JPEG, does not allow for transparent background (read e.g. http://stackoverflow.com/questions/16906144/transparent-background-in-jpeg-image).

     

    This is not actually your problem, however, as the file content isn't in a JPEG format:

      Filename: [H:\Downloads\christiaan-bekker-logo-1460308205.jpg]
      Filesize: [5986] Bytes
    
    Start Offset: 0x00000000
    NOTE: File did not start with JPEG marker. Consider using [Tools->Img Search Fwd] to locate embedded JPEG.
    
    

    This is because PrestaShop generally (mis)uses the JPG extension for any image type. I assume your image is actually a PNG, which does support transparent backgrounds.

     

    Now, the fix could be quite simple: add a background in a layer in your PNG, and then squash the layers and save a copy as a JPG.

  4. I cannot reproduce, i.e. I am not getting any ?token='' tags on your website. Furthermore, if you do not like having IDs in your URLs, there are many addons for that, like http://addons.prestashop.com/en/16633-pretty-urls.html.

     

    Regarding the custom content - build a module that hooks into the product page on the locations you need and have your content displayed there. No need for static (?) pages.

  5. I just thought about this a bit more, and can't we rewrite this into,

    {category:/}{id}-{rewrite}{-:ean13}.html{#:id_product_attribute}
    

    In that case, the product attribute would use an anchor tag, which Google interprets as being on the same page (same canonical URL) - this'd solve the duplicate content problem, and is indeed also the way PrestaShop used to do attributes pre-1.7.

     

    Now, I've not tested this, but could any of your guys give it a go? :)

  6. I am not sure if I'm late to the party, but I have a few suggestions of my own.

     

     

    On the homepage, the products do not align. The panels are of different height, which looks a bit clumsy.

     

    erk4uc.png

     

     

    On hover (same page), the product panel gets bigger and overlaps the next row. Personally, I'm not a fan of this. See,

    2u5alah.png

     

    The current menu structure (both Office Equipments, and Printers & MFP's is a bit empty. Unorganised.

    72qdxx.png

     

     

    Finally, in terms of performance, your website needs some improvements.

    • Turn on friendly URLs.
    • Enable the cache, and all the performance options.
    • Reduce the dimensions of the slider images (currently 1900x900, but the website is limited to 1170 max-width. This only takes up more bandwidth, making for a slower site).

     

    Anyway, those are just my two cents. Hope it helps!

  7. While the above solutions will work, translating something with an empty string feels like a 'hack', of sorts. It seems like a cleaner solution would be to not show the string altogether, via e.g.

    {if ($lang_iso == "en")}{l s='your string'}{/if}
    

    Not saying the other solutions are at all wrong, but this more closely reflects the actual behaviour you seemed to want.

×
×
  • Create New...

Important Information

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