Jump to content

Lutz

Members
  • Content Count

    42
  • Joined

  • Last visited

Community Reputation

22 Excellent

About Lutz

  • Rank
    Jr. Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,070 profile views
  1. Hi @dragan, I'm doing the same, using Rockfinder on the frontend, building my own pagination. b), 'url': since you know the parent (1041), you could query 'name' instead of 'url', and add it to the known path.
  2. My workaround was because of unsorted query results from a Page Reference field inside a Repeater Matrix field. If you can use $pages->find(), the results should get sorted: Try loadOptions and set joinSortfield to true. Test: $items = $pages->getById([1182,1061,1079,1082]); d($items); The result is a PageArray, the items => array is sorted in the order of the ids in your selector. Update: It doesn't seem to work with $pages->find(), but you can use $pages->getById.
  3. Hi Torsten thanks for the question, I also stumbled upon this problem and couldn't find a solution so far. There are simple solutions in ExpressionEngine and Craft (https://docs.expressionengine.com/latest/channels/entries.html#fixed_order, https://docs.craftcms.com/v3/dev/element-queries/entry-queries.html#fixedorder), maybe I missed something. Here's a workaround, temporary test code from a current project: $itemIdsA ia an array of ids, $finder3A is an array with results from a rockfinder query. if(count($itemIdsA)) { foreach($itemIdsA as $key => $value) { foreach($finder3A as $item) { if($value == $item['id']) { echo '<li>'; $datumVon = strtotime($item['datum_von']); echo 'Autor: ' . $item['autoren_title'] . ' / Datum: ' . date('d.m.Y H:i', $datumVon) . '<br />'; echo '<h3>' . $item['title'] . '</h3>'; echo '<p>' . $item['teaser'] . '</p>'; if(isset($pma[$item['id']])){ echo '<p>Test Anzahl Leserbriefe: ' . $pma[$item['id']][0] . '</p>'; } echo '</li>'; } } } }
  4. It was closed on 10 Jun 2016, but it's still (or again) an issue (PW 3.0.132).
  5. @kongondo Yes, thank you, this is what I had expected and hoped for. My question was in terms of scalability, regarding file system limits. In PW, files are stored in subdirectories under /site/assets/files, therefore we normally have to deal with max directory limits (e.g. 32k). We have $config->pagefileExtendedPaths, but it's marked as beta. So as you mentioned +500k, I hoped for an info regarding the stability of pagefileExtendedPaths (or another way to avoid collisions with max directory limits). When they manage +500k, did they enable pagefileExtendedPaths?
  6. @kongondo To prevent a misunderstanding: each media is stored in the database, not in the file system?
  7. @kongondo Good to know (+500k), do they use $config->pagefileExtendedPaths, an unlimited file system or are there special features of the Media Manager for storing the images?
  8. @adrian I think we were wrong. $pages->get() should return a NullPage, but with $categories->get() you are using WireArray::get()!?
  9. You are right: $categories returns a PageArray, so I thought that get() should return a NullPage in both cases.
  10. get() should return a NullPage in both cases, if $categories returns a PageArray. Since find() could return a PageArray or an array: what does $categories return?
  11. @teppo Thank you very much. Yes, I plan to go with ProCache and to avoid template caching for most of the templates. I think I misunderstood the comment of Soma regarding the template cache problem, thanks for the hint.
  12. Ok, I read the issue 432 thread again, so yes, the need to "revisit" (Ryan) could refer to the implementation of the template cache only. However, it would be good to know if pagefileExtendedPaths is a reliable option and I'm glad that you suspect that this is true.
  13. @teppo Maybe I'm wrong, but no, the config option pagefileExtendedPaths is a result of that discussion and the comments of @Soma and @ryan refer to the concept of extended paths.
  14. @teppo I hope so. There's an open ticket "Feature-Request: More options how to store files under site/assets/files" from 2014, where @Soma warned regarding problems with pagefileExtendedPaths when using template cache and @ryan answered in his last comment: "That's a good point, as the structure is flat. Will have to revisit that with a similar solution to the files at some point in the future." https://github.com/ryancramerdesign/ProcessWire/issues/432
×
×
  • Create New...