Jump to content

mvolke

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

6 Neutral

About mvolke

  • Rank
    Newbie

Recent Profile Visitors

973 profile views
  1. For all of you who want the model stored in files, maybe you should have a look into Bolt CMS. In Bolt you can configure your content types in YAML files and import them via a migration tool integrated into the CMS. In my opinion this is by far the best approach. This enables... versioning of data structure easy deployment working in teams (because branching/merging in Git workflows is now possible) much faster editing of data structure (for professionals) than clicking through UIs What I miss in this discussion is, what is the audience of users of Processwire? Do we want to be attracti
  2. I discovered that if I create two thumbnails with the same size but different additional settings only one file (the first setting) is created because the settings are not reflected in the filename. E.g. $image->size(200, 100, array('cropping' => false)); $image->size(200, 100, array('cropping' => true)); In this case the second image won't be cropped. I would expect that two different thumbnail will be generated.
  3. @mindplay.dk This sounds really great. I think it could be the perfect solution in the long run. Until this module is finished and tested, I can recommend the phpmig migrations approach.
  4. 1) Migrations I had the same problem during my work with Processwire. If you have a team working on a Processwire project where everyone has his own dev server then you need to be able to version the "structure" you put into Processwire and keep it in sync with the template files. I found it to be important to strictly distinguish between structure and data. In 90% of the cases this means templates and field can be seen as structure and pages would be the data. In my current project I tried to use the concept of migrations with Processwire utilizing the phpmig library. If you strictly cre
×
×
  • Create New...