Jump to content

Julien Bourdeau

  • Posts

  • Joined

  • Last visited

  • Days Won


Julien Bourdeau last won the day on July 31 2015

Julien Bourdeau had the most liked content!

1 Follower

Profile Information

  • Location
  • Activity

Recent Profile Visitors

26,117,234 profile views

Julien Bourdeau's Achievements


Newbie (1/14)




Community Answers

  1. What do you mean? I don't get it. I'll have a look for the rest.
  2. Hi, When you install a theme, the custom modules defined by the theme as dependencies are installed. In 1.7, the theme maker can define what he wants to achieve with modules: enable/disable, hook/unhook, and so on. If there is any special modules, they are bundled with the theme and installed at the same time. Everything happens in the theme.yml: http://developers.prestashop.com/themes/gettingstarted/index.html#theme-yml We thought it didn't make much sense to ask anything to the use at this step. If you want to disable a module afterwards, you can do it in your module page of course. I hope this answers your question.
  3. Ah oui ok. C'est pas ce que j'avais compris. Donc non c'est pas possible, je ne peux pas m'engager mais à mon avis ça ne le sera jamais dans le core avec le theme par défaut (trop spécifique). Je pense que par contre prestashop offre la possiblité à ton theme d'implementer ce genre de comportement.
  4. Déjà merci pour ton message, mais ta compaison n'est pas la bonne. La bonne analogie c'est: "c'est un peu comme si vous disiez à un type qui fait une cuisine honnête qu'il ne peut pas être bénévole dans votre resto sous prétexte qu'il ne fait pas de l'assez bonne qualité". C'est ça la situation, et du coup ca me parait quand meme moins choquant. Le fait que ca soit plus rapide pour nous que pour toi ne me semble absolument pas un arguement valide. En soit j'aimerais bien passer plus de temps à debugger et merger avec la communauté (comme tout le monde ici) mais malheureseuement le temps manque cruellement. Par contre bonne nouvelle, Github nous permet depuis peu d'editer les PR des contributeurs, ça devrait regler ce problème.
  5. C'est possible puisque toutes les declinaisons ont une url unique (basé sur l'id combinaison qui a ete rajouté dans l'url). J'ai bien compris la question? Sinon je veux bien un peu plus d'explications.
  6. Hi, Here is the pull request, it will be merged soon. Once merged, you can export your theme with this command: "php app/console prestashop:theme:export themename" :tada:
  7. Have you actually looked at it? I really don't get how you can say that it's not easier/faster. Look at ANY template in default-bootstrap and compare it to the 1.7 template (either StarterTheme or Classic, I guarantee you'll find it **much** cleaner and clearer. I understand it can be hard to re-learn and it's not always nice to see things changing, but if you make this little effort at the beginning, you'll see that you'll never touch default-bootstrap ever again.
  8. Maintaining 2 modules might be complicated but maintaining backward compat' is WAY worse.
  9. 1. you should create a thread dedicated for this I would be happy to share my preferences and I guess many people can join in. 2. Not yet, but I'd like to make one. 3. The best way so far is to create a custom module to do that. Every developer will create their own. We would like to have a special kind of module, a "theme option module" 4. Nope. StarterTheme is agnostic, there is no lib bundled at all. The best way will be to use npm to get bootstrap 4, then import it in your theme.css and theme.js. Then modify templates to use bootstrap classes. 1. Thomas is working hard on the module validator right now, it should be in production soon. 2. Having a module compatible with both version is a **very very very very bad idea**. 1.6 will be maintained for a long time but there is no new features and such so your module shouldn't require much modification. Since 1.7 is a major version, loads of things have changed, like PHP version for example. There is also loads of great new features for front office: widgets, smarty is automatically escaped in 1.7, many smarty functions has been removed. If you want to have your module compatible, it will be hard, plus you won't be able to use ANY new feature (for example because namespace will break on PHP < 5.4. If you want to I believe the best way will be to have 2 modules.
  10. Effectivement il y a 24h de cache. Si tu connais une solution. je suis preneur.
  11. I'm saying it won't during the whole 1.7 cycle. Since we broke compatibility with all existing themes, I believe that it won't be for PrestaShop 1.8 either. Breaking compatibility for 1.7 was required to clean everything but breaking compatibility again to move from smarty to twig seems unlikely (it doesn't bring anthing to the table).
  12. It's true that 1.7 isn't about bringing bugfix on every subject but it doesn't mean we doesn't fix anything! There are plenty of bugs related to the former product.js for example, they have all gone away! 1.7 fixes a hell lot of bugs (at least on the front office part). But yeah, some topics haven't got much attention, including ASM. About Smarty vs Twig, I haven't compared much (I just checked as we're talking about it). Smarty seems a bit faster, okay, but twig documentation is much better and it's used by a lot of frameworks. I think PrestaShop should use more standard and common technologies. Twig performances are still very good. Twig 2 is under development, maybe it will be faster. Also, front office is still using Smarty and I think it's were performance matter the most.
  13. Please don't forget the StarterTheme and almost full rewrite of the front office part. The point is to improve stability and fix LOADS of bugs. it will also make template makers' life easier and improve module compatibility. It will probably introduce some flaws but I believe most of them will be fixed by core update (controller, presenters, objectmodels) without any theme update. I am deeply convinced this is a very very important step for PrestaShop ecosystem: hence the module and theme validation.
  14. Je veux bien des exemples précis stp. On a porté tous les modules les plus utiles. On ne peut pas tout faire dans une version! Si on a viré des modules comme themeconfigurator ou blockstores c'est justement parce qu'on voudrait refaire un système beaucoup plus simple et puissant. Par exemple blockstores, editorial et tout un tas d'autres modules similaires peuvent etre remplacer un module de contenu. Il faut aussi cette fameuse feature de hooker un module plusieurs fois sur le meme hook. L'intéret de cette 1.7 c'est poser des bases pour le futur. Refaire live edit ou la gestion du contenu sera beaucoup plus simple avec ces bases saines.
  • Create New...

Important Information

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