muzzer

Members
  • Content Count

    115
  • Joined

  • Last visited

Community Reputation

87 Excellent

About muzzer

  • Rank
    Sr. Member

Profile Information

  • Gender
    Male
  • Location
    Marlborough, New Zealand
  • Interests
    Webdev, squash, scuba diving, alternative power systems, carpentry, guitar, and don't mind wasting a bit of time on dirt bikes every now and then.

Recent Profile Visitors

4,961 profile views
  1. Hey @abdus, Thank you! I was not aware you could do anything like this! Love it. BTW the ugly styling in my screenshot was just the default from the snipping app, I never meant you to copy it so accurately! Bonus points for that. @tpr thanks for the AdminOnSteriods suggestion, it looks interesting, will check it out. Cool name too.
  2. Similar (related) question. I have templates with up to 50 fields. I don't work in the Admin much but do use it to lookup values on pages and with my poor memory, and even with pretty good naming convention for my fields (some are similar) I often lose track of field names. Is there any way (short of manually appending the field name to the label) to show both label and field name above the field input. Essentially, is there somewhere an option to automatically append the field name to the field label. Please see screenshot for basic idea: Thx
  3. muzzer

    I have what is building to be what I would consider a large site and am starting to notice a few pages running slower than I would like. I've been looking at various options for speeding them up and it seems the database interactions are probably the part which drag the most. So now I'm trying to understand how PW handles queries and pages objects so I can program more efficiently, so my question is: $bookings = $pages->get('/bookings/')->find('room=roomOne'); foreach($bookings as $booking) $roomData = $booking->find('date=' . $today); In the above snippet is the third line performing the find() on the $bookings pages object in memory or is it querying the database again and using the $bookings ojects to refine the query? I'm trying to reduce the database queries (especially repeat queries) so understanding this would be helpful.
  4. I just had a duh! moment and thought I should share as it may be useful to others, especially PW beginners. I know a lot of you will go "yeah well duh...." and yeah, well I feel like a bit of an idiot but anyways.... I had a page outputting a table detailing data from about 200 records (PW pages). For each record it searched for child pages of a certain template, probably averaging 3 child pages per record and added some data from those pages to each row of the table. Simple stuff. The page was averaging about 12 seconds to load. Anyway, today I got frustrated enough to try to work out why it was so slow. Turns out I realised that the child pages I was searching for were all direct children, so I changed my search method from $pages->get(....)->find(.....) to $pages->get(.....)->children(.....) and blow me down the page load has gone from 12 seconds to a tad over 1 second. Turns out each child page had many child pages of their own (thousand of pages in total) and all these were being searched with the find() method. Stupid mistake, but I think right from the beginning of my learning of PW the find() method was ingrained. So hopefully this helps some newbies and others like me. Check out http://cheatsheet.processwire.com/page/built-in-methods-reference/page-find-selector/ and http://cheatsheet.processwire.com/page/built-in-methods-reference/page-children-selector/ for more info on these methods and others.
  5. muzzer

    kia ora Robin, Yeah, that looks like an ideal start. And I will likely start learning about PW modules in the process. Sweet as, cheers mate.
  6. muzzer

    Hey thx Adrian, agree with you. I do use Lister Pro which is awesome, but I also use the page tree a lot when flicking between pages, hence the question....
  7. muzzer

    I can't find the following but I'm sure I'm not the only one who would use such functionality so it must have been thought of and perhaps implemented in a module; I find when I'm using the page tree in the PW admin that I'm often opening (editing) many pages just to check the field values - one of my sites has a lot of user input so fields change regularly without my necessarily knowing. This can get annoying as I either lose the page tree when clicking the edit link, or I need to open in a new tab, both of which are slow processes when checking multiple pages, and I end up with loads of open editing tabs. I'm wondering if anyone has created a module to simply show basic page field info in an ajax tooltip when hovering pages in the page tree? If not, is this something a intermediate programmer such as myself could feasibly develop into the PW system or is this realistically a project for gurus only?
  8. muzzer

    Have to agree Pierre-Luc, mandrill is pretty sharp. I've been using it for about four weeks with this module and it's been 100% reliable (which I can't say for my previous SMTP setup. The API is sweet and the dashboard is pretty bloody good to boot. This is one system I'll use again and again. Cheers Craig for getting me onto this.
  9. muzzer

    I trialled a subdomain to get concurrent requests. It worked, but the domain lookup time for the subdomain killed and benefit I got from concurrent requests. How does one get around this, how can I set the domain caching to say two weeks to minimise domain lookup delay? Or am I on the wrong track?
  10. muzzer

    Hey @horst, seems this is indeed the issue, I presume singular:true only allows or reuses a single instance of the class. Thx
  11. muzzer

    Yeah thx @tpr, that's what I was originally doing. However I was extending wireMail with added the module WireMailMandrill to send via Mandrills API, but this in conjunction with new wireMail(), causes the WireMailMandrill function tags() to throw an error: tags does not exist or is not callable in this context $mailTwo = wireMail(); $mailTwo ->to('recip@two.com', 'recip two') ->from('some@address.com', 'Sender Two') ->subject('Subject two') ->tags('my tag') ->send();
  12. muzzer

    If I wish to make two wireMail calls one after the other - how do I reset the member vars set in the first call? $mailOne = wireMail(); $mailOne ->to('recip@one.com', 'recip one') ->from('some@address.com', 'Sender One') ->subject('Subject one') ->bodyHTML($htmlMsg) ->send(); $mailTwo = wireMail(); $mailTwo ->to('recip@two.com', 'recip two') ->from('some@address.com', 'Sender Two') ->subject('Subject two') ->send(); $mailTwo appears to have both recipients recip@one.com and recip@two.com, and also has $bodyHtml content set from the first wireMail instance. I'd like all $mailTwo member vars to be unset to being with. I would have thought this was default behaviour, where am I going wrong? Are $mailOne and $mailTwo not complete separate instances of wireMail?
  13. Thx for this Alan, been checking out Mandrill since reading your post earlier, and running some test emails etc. Looks like a pretty sweet system. Will check out the API over the weekend as that looks pretty sharp also I think I'll be moving all my site emails to Mandrill. Cheers.
  14. In summary, i think that maybe there should be an emergency shut off in AIOM+, because without the method described above, how would you keep a site online say if AIOM+ was just totally failing? Yes, I have also experienced a few weeks back exactly the same as you describe here, and resolved it essentially the same way. As with you I had unwanted downtime while I sorted the issue. As a result I've also implemented a system similar to yours, which makes me think others are probably doing the same also. If this is something that is being repeated on multiple sites then ideally it should become part of the AIOM module.