Jump to content

Hurme

Members
  • Content Count

    86
  • Joined

  • Last visited

Community Reputation

17 Good

About Hurme

  • Rank
    Full Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you, I managed to miss the pageName subpage and all the relevant information in it.
  2. Just a short question about sanitizer->pageName. if I have a page title that has scandic letters in it. "Pääskynen" as an example, the pagename will be "paaskynen", but if I use sanitizer->pageName on it, I will get "pskynen" instead. Would it be possible to get what the backend sanitizer does with page names, or is there another sanitizer that works in similar way (changing ä > a instead of dropping letters)?
  3. Thanks to you both, The numbering option was something I thought about too, but it seems bit clunky in the end. I'll take a look at your hook next week, thanks for that!
  4. Heya, Is there any way to affect the order of templates in the backend, specifically when you create a new page and select the template it uses? It would be useful to have the most used template at top of the list as an example.
  5. Well yes, your example is what I'm trying to do. But in this case I get an error when I'm trying to save the "child". I was assuming it was because PW couldn't save those two pages back to back in same operation, so I relegated creating and saving the child into a hook that takes place after the first page has been saved. But your example seems to work fine, so I'm just going to go back and check my code.
  6. I need to create a page and then add a children to it when user fills in a form. I can create the parent page by putting the code on the form page itself, and then the child by using a pages::added hook and bringing the needed information to the hook via session. Is there any more straightforward way of doing it or is this a good approach?
  7. @kixe I'm probably doing something wrong, but I cannot get your example to do anything.
  8. I've always included a "path" to the field when including fields inside a repeaters or matrix fields. I'm not actually sure if it's really needed or if I've just been too meticulous about it. matrix_field.regular_field|matrix_field.repeater_field.regular_field Perhaps repeaters and matrix fields having their own template has something to do with it.
  9. Hello, Any advice on how to hook page, so its fields get populated by something else than the actual saved content? The below works fine for frontend (it's in ready.php), but has no effect in front-end editing or backend, and that is the problem here. $this->addHookBefore('Page::render', function($event) { $page = $event->object; $page->exampleField = '123'; }); The information doesn't need to be saved into PW itself. It's been fetched and then on save, delivered to another database.
  10. Hey, Thanks for the replies all. @bernhard We'll take a look at Rockfinder 2. We don't have that many pages yet, as this is more about future proofing the site, but eventually it has potential to grow very large indeed. I'll get back here once we are further along.
  11. Hey, I know there has been lots of discussion on this subject already, but I feel like I need some clarification on the subject, especially in the light of the new $pages->has('selector'). So lets say we have a site with a couple of million pages and we need to find one or more pages from that pile. 1) Usually direct database search would probably be recommended at that point, but does the $pages->has('selector') speed things enough to be considered a serious alternative? 2) If I wish to load a list of all the Names with say one extra field from all the pages, will PW always load the whole page (times million), or is it possible to only get the fields I'm looking for and nothing more?
  12. Yes, that would be nice. Especially since the philoshophy of PW for pretty much everything else is so streamlined. Right now it looks like I'll try to manage with the PW's own <edit> functionality or cook up my own solution. Neither of the modules I linked earlier really did anything useful in this case.
  13. Hi @kongondo, Yes I mainly meant the drag&drop functionality and the ability to edit images and so on.
  14. Hi @Ivan Gretsky, Yes I noticed the iframe now. That's an even bigger bummer. Ideally I would like an inline view of the wanted fields, without any kind of modal or iframe at all, so I could customize them as I see fit, while still retaining the drag&drop functionality and other nice features. That's probably a pipedream. I'm currently looking into these: http://modules.processwire.com/modules/front-end-edit-lightbox/ http://modules.processwire.com/modules/admin-bar/
  15. Hello, I'm building a site where frontend editing is integral part (you could say the only part) of the sites function. Is there any way at all, to humanely customize the frontend editing modals? I've found out that it wont work properly with new jQuery (which is something we use) which is bit of a bummer, but can be solved with jQuery migrate (see link below). The modal also looks sort of fugly compared to rest of the site and overriding the appearance with css alone, while not impossible, is a major pain in the ass. jQuery issue link: https://github.com/processwire/processwire-issues/issues/609 If customization isn't an option, the next step is probably to build our own forms, but for images and files especially, it would be nice to use the existing tools.
×
×
  • Create New...