Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


DaveP last won the day on November 13 2014

DaveP had the most liked content!

Community Reputation

948 Excellent

About DaveP

  • Rank
    Old Bloke
  • Birthday 01/23/1957

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Chorley, UK

Recent Profile Visitors

17,058 profile views
  1. Few random thoughts... Log all searches (you probably already do). This works $log->save('search',"Query = '$q' Results = ($results_count) $pages_found"); gives something like 2018-03-12 16:19:08 guest https://example.com/search/?q=taxi Query = 'taxi' Results = (3) 1170|1073|1693 2018-03-13 11:22:27 guest https://example.com/search/?q=9001 Query = '9001' Results = (1) 1021 This is valuable because it shows you what you are up against! Consider incorporating stemming (if you are working in English, at least). The best-known algo is the Porter stemming algorithm. There are PHP implementations on GitHub etc. What you could look at is for each product, hook on product save and have a back-end field programmatically populated with stemmed versions of Product Title etc., then stem search words and build that into your selectors. Also consider a back-end 'search keywords' type field, and if there's a glaring regular user mis-spelling just add that manually. This doesn't scale all that well, but can help with a quick fix. (I built a search for a fishing tackle shop site many years ago - pre-PW - and nearly as many searchers spelt 'Daiwa' as 'Diawa' as those who got it right. Easy quick fix.)
  2. Aaahh, I wasn't understanding correctly. Maybe something like this might be useful.
  3. If I understand correctly, in your $selector, use body^=$q instead of body~=$q. (Note caret instead of tilde.) See https://processwire.com/api/selectors/#operators
  4. Not yet. Let's try some stuff first. There's something going on in .htaccess, because it redirects to www.vivid.black under some circumstances. You might try renaming .htaccess to htaccess.old or some such and replace it with a new copy of the default one in the PW download, see if that changes anything.
  5. Welcome, dubiosa! Well, whatever you've got going on, it's very strange. If I visit the http URL you posted (with a full stop at the end (?)), I get the default Apache page. If I remove the full stop, it redirects to https and I get a certificate error. If I replace the full stop with a slash, I get an actual web page over https. Is the server a VPS? Is it managed or unmanaged? Is it shared hosting? As far as I can see, it's likely to be either a server misconfiguration (Apache etc.) or your .htaccess, or a bit of both. Tell us a bit more and we'll try to help.
  6. Very occasionally you'll come across a deprecated/removed PHP function in a very old module written for PHP 5.3 or 5.4 (what's the earliest version PW worked with years ago?) if you're now using, say, PHP 7.2. Even that kind of thing can be relatively easily Googled, or I'm sure someone on here could help with a specific problem of that kind.
  7. Ok, this should work $image = $child->images->first->width(500); $out .= '<img src="'.$image->url.'">'; See http://cheatsheet.processwire.com/files/image-properties-in-addition-to-those-in-file/image-width/
  8. Just a guess, but try $out .= '<img src="'.$image->width(500)->url.'">'; because I think your version is trying to change the width of the url.
  9. Know exactly what you mean! I had something similar a couple of years ago and did find a kinda solution, but was never happy with it. Just hope I remember about this next time the need arises.
  10. ...and if you need a break from reading, take a look at this if you haven't seen it already. It's a very old video that Ryan did for PW 2, but very much recognisable even now. It covers some of the content management aspects of the PW backend.
  11. Hi, and welcome. The answer to your question is 'Well, yes, probably.' Give us a bit more of an idea of what you are trying to do and we will try for a more detailed answer.
  12. Update re previous post Following on from a bit more testing, I have forked the Indexer module mentioned above and started a new thread...
  • Create New...