Jump to content


  • Posts

  • Joined

  • Last visited

About JulienPct

  • Birthday 08/26/2000

Profile Information

  • Location
  • Activity

Recent Profile Visitors

635 profile views

JulienPct's Achievements


Collaborator (7/14)

  • Dedicated Rare
  • Collaborator Rare
  • First Post Rare
  • Conversation Starter Rare
  • One Month Later Rare

Recent Badges



  1. That's normal, this is why we never make any big update like 1.6 to 1.7. For exemple, I tried to upgrade from 1.7.7 to 1.7.8 and my homepage style just get destroyed. You can fix all bugs if you want but I hope that you are motivated. Btw if you want to install a new ps version but still use the same folders, then you'll have the same problems except if you keep only the theme and modules folders but I think you'll get some errors.
  2. Hello, Major upgrades like this are very complex to implement, rarely is it a good option. I don't understand why you want to download a new PS 1.7 when your site is in 1.6 ? Ok it's for upgrading but, unless there is a big need, not changing seems to be the best solution. Even more when you know how much better the 1v6 version was but I'm not saying anything As for your site not working, major updates, as their name indicates, make major changes to the "structure" of Presta so many themes may not be compatible, some files will be deleted and / or replaced by new ...
  3. Il est lent au début comme vous n'avez plus de cache, le temps de chargement des pages est plus long. Normalement si vous retournez sur une page sur laquelle vous avez déjà cliqué, cela devrait aller plus vite non ?
  4. Bonjour, Avez-vous vider votre dossier de cache manuellement ? /var/cache/ Dans le cas où l'erreur persisterait, pouvez-vous activer le mode debug afin de voir le problème ?
  5. Dans le style Il faut alors surcharger le tpl d'un des modules positionné à cet endroit ou directement le fichier tpl du header Encore dans le style
  6. Bonjour, Pourrions-nous avoir un accès au front de votre site afin de voir les balises ?
  7. Les premiers if sont juste pour que mes changements ne s'applique que sur une page de catégorie {if $page.page_name == 'category'} {if $page.page_name == 'category'} Ensuite j'y créer tout simplement mon block avec les élements que je souhaite, si vous voulez seulement un <p>, alors ne mettez qu'un <p>
  8. Voici le contenu de mon layout-both-column : <!doctype html> <html lang="{$language.iso_code}"> <head> {block name='head'} {include file='_partials/head.tpl'} {/block} </head> <body id="{$page.page_name}" class="{$page.body_classes|classnames}"> {block name='hook_after_body_opening_tag'} {hook h='displayAfterBodyOpeningTag'} {/block} <main> {block name='product_activation'} {include file='catalog/_partials/product-activation.tpl'} {/block} <header id="header"> {block name='header'} {include file='_partials/header.tpl'} {/block} </header> {block name='notifications'} {include file='_partials/notifications.tpl'} {/block} <section id="wrapper"> {hook h="displayWrapperTop"} ------------------------------------------------------------------------------------------------------------------------------------- {if $page.page_name == 'category'} <div id="js-product-list-header"> {if $listing.pagination.items_shown_from == 1} <div class="block-category card card-block"> {block name='breadcrumb'} {include file='_partials/breadcrumb.tpl'} {/block} <i class="icon-{$category.link_rewrite}"></i> <h1 class="h1">{$category.name}</h1> {if $category.description} <div id="category-description" class="text-muted">{$category.description|truncate:300:'...' nofilter}</div> {if $category.secondDescription} <a href="#footer" class="category-description-link">Lire la suite</a> {/if} {/if} </div> {/if} </div> ----------------------------------------------------------------------------------------------------------------------------------- {elseif $page.page_name == 'cms'} <div id="js-product-list-header"> <div class="block-header card card-block"> {block name='breadcrumb'} {include file='_partials/breadcrumb.tpl'} {/block} <h1 class="h1">{$page.meta.title}</h1> </div> </div> {/if} {if $page.page_name != 'index'} <div id="content-wrapper"> {/if} {block name="left_column"} <div id="left-column" class="col-xs-12 col-sm-4 col-md-3"> {if $page.page_name == 'product'} {hook h='displayLeftColumnProduct'} {else} {hook h="displayLeftColumn"} {/if} </div> {/block} {block name="content_wrapper"} <div class="left-column right-column col-sm-4 col-md-6"> {hook h="displayContentWrapperTop"} {block name="content"} <p>Hello world! This is HTML5 Boilerplate.</p> {/block} {hook h="displayContentWrapperBottom"} </div> {/block} {block name="right_column"} <div id="right-column" class="col-xs-12 col-sm-4 col-md-3"> {if $page.page_name == 'product'} {hook h='displayRightColumnProduct'} {else} {hook h="displayRightColumn"} {/if} </div> {/block} {hook h="displayWrapperBottom"} {if $page.page_name != 'index'} </div> {/if} <footer id="footer"> {if $page.page_name == 'category' && $category.secondDescription} <div id="before-footer-category-long-desc"> <div class="before-footer-category-long-desc-desc"> {$category.secondDescription nofilter} </div> </div> {/if} {block name="footer"} {include file="_partials/footer.tpl"} {/block} </footer> </main> {block name='javascript_bottom'} {include file="_partials/javascript.tpl" javascript=$javascript.bottom} {/block} {block name='hook_before_body_closing_tag'} {hook h='displayBeforeBodyClosingTag'} {/block} </body> </html> La partie qui vous intéresse est entre les "-"
  9. There is a style. Remove the width or the height.
  10. Si tu ajoutes cette ligne au dessus de l'order by ? WHERE o.id_customer = "id_souhaité"
  11. Hello, First of all, why doesn't it work to override the Controller? Have you looked at the functions of the Category class? Could you give us a screen to better visualize the problem or a site access?
  • Create New...

Important Information

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