Jump to content

lenoir

Members
  • Posts

    137
  • Joined

  • Last visited

Posts posted by lenoir

  1. Just now, MarkE said:

    When you create a repeater field, say 'fieldname', PW automatically creates a template called 'repeater_fieldname'. It looks like you are using this, not the actual field name. If you actually called your field 'repeater_agenda' then the template will be called 'repeater_repeater_agenda' (check your templates list with system templates filter turned on). I wanted to eliminate the possibility that you might be calling the template rather than the field.

    Oh I didn't know this. I actually started calling all my repeaters "repeater_…" but that might not be the brightest idea in that case. But I find sometimes forget which fields are repeaters and which aren't, that's why I started doing this.

    But I guess this isn't the problem, since I'm pointing to the right field.

  2. Hi,

    this seemed quite straight forward, still can't get my head around it…

    I have a repeater with 2 fields (title and datetime). I want to sort the repeater items in the API by the datetime field. But it doesn't work. 

    foreach($page->repeater_agenda->sort("eventdate") as $agenda){
    
    }

    This doesn't do anything. Am I missing something?

  3. Hi,

    I've been using PW on so many websites to this day, can't count them. Still, I'm always looking for a better way to name my fields. A typical problem is when I need multiple textfields on one template.

    I sometime contextualize them (i.e. "lead", "maintext", "detailinformation", etc.) or use "textfield_1", "textfield_2", etc., and I even tried to differentiate them by their type or max characters ("textfield_formatted", "textfield_unformatted", or "textfield_500", …) 

    So my question is… What solution have you found to this issue?? ?

  4. 13 minutes ago, Klenkes said:

    I did something like you want. Add this hook to ready.php:

    $wire->addHookBefore('ProcessPageSearchLive::execute', function(HookEvent $event) {
    	$event->wire()->addHookAfter('FieldtypePageTitle::wakeupValue', function(HookEvent $event) {
    
    		$page = $event->arguments(0);
    		
    		// specify your temlate
    		if($page->template == 'tool') {
    
          		// get the fields you like
    			$prefix = $page->pre;
    			$suffix = $page->suf;
    
    			// add your data to the list
    			$event->return .= " | {$prefix} {$suffix}";
    
    		}
    
    	});
    });

     

    Wow, thanks! That's exactly it. ?

    • Like 1
  5. I'm talking about ProcessPageSearch. Concrete case: the user searches a particular page in the search field top right corner. If they type the name of a tree, there's a bunch of pages that will display with that particular tree. I would need it to display a second field with the location. So they see in the result "tree, location".

    I'm also using ProcessPageList (which is perfect for displaying the pages in the tree (this time I'm talking about the tree of pages in the backend ?). But this is a different need.

    Lister might be an alternative solution, actually ?

    • Like 1
  6. On 5/20/2021 at 9:47 AM, gebeer said:

    I took @bcartier's code from this post and made a configurable module from it.

    change-default-frontend-lang.png.a23bdeaf2a364995919ce3605bfeaa0a.png

    You can find the module attached.

    I can confirm that the redirection to a non-default language works on PW 3.0.172

    DefaultFrontendLanguage.zip 1.35 kB · 49 downloads

    Thanks Gebeer, that was definitely a time saver. Works fine for me. Couldn't go into the trouble of swapping languages by default, not with all content already up there.

  7. Is it possible to let people edit a page without having to have a user-role?

    My case is the following:

    Visitors fill in a form (Formbuilder) which is saved to pages. They get a confirmation email which could contain a unique editing link. In case they need to update some information, they can click on this link, edit the fields and save. 

    Am I totally off? Is there a better practice? 

  8. I'd like to add my voice to this topic. I was just browsing through the modules under "admin themes", sorted them by date and oh… the latest one is 4 years old… And almost all of them stopped with version 2. 

    As much as I like this CMS, I'm having more and more of a hard time convincing clients to use it, and I think it has a lot to do with the looks. It feels old and somehow odd…

    i just came across the module "admin theme boss" by @Noel Boss and what a relief! Finally something I can present to my clients without shaking. ?

    I'm really hoping for improvements in this field, since I'm a true believer in the love at first sight, or at least how important first impressions are.

    • Thanks 1
  9. It's an old post but still a hot topic…

    I create a lot of websites for clients in german, sometimes in french. I often end up with a mix of languages either in the fields or templates names… Anybody working with multilanguage sites with a good practice suggestion? 

×
×
  • Create New...