Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

10 Good

About kp52

  • Rank
    Jr. Member

Recent Profile Visitors

1,582 profile views
  1. Don't know about the hook, but the PHP "if" condition needs fixing (double equals for comparison operator): if($page->template == 'product') { 🙂 KP
  2. I got a very similar message this morning, posted to the contact page of a website I look after. Bit of a giveaway when the messages includes "This is not a hoax, do not reply to this email". I've seen a number of similar ones via this and other contact pages in the past. Nothing bad has happened yet after ignoring them! I would only take any notice if they posted me something from the database that shouldn't be accessible to them. I looked up the IP on stopforumspam.com and found several other reports from this morning, with a variety of names and emails submitted.
  3. "500 Internal Server Error" may be a red herring - it seems to be PW's way of avoiding display of plain old PHP errors on the front end on a production server. Can you see the PHP error log on your hosting? Do you get the error when you log in to the back end? if you can log in, Tracy will be your friend.
  4. If your site's URL is http://localhost/processwire/ (the front end, where visitors to the site will see published pages), your administrator login page (to get to the admin pages, the back end) will be at http://localhost/processwire/processwire/ unless you chose a different address for it when you were installing. You can change it after logging in, if you want. KP
  5. Update the Parent via Edit > Settings > Parent.
  6. I tried the module after reading this thread, using Server Directory method, and had a problem because ready.php *was* included. The installer complained about a hook I use to process submissions to a FormBuilder form: "Call to a member function addHookAfter() on null ", where the call is $forms->addHookAfter('FormBuilderProcessor::render', function($e) Temporarily renaming ready.php in the profile and resetting it after installation got me where I wanted to be. It's very useful to install a ready-made set of modules like this.
  7. Thanks for this and all your other work on the module. I'm in the process of converting sites from Clipper (MODX Evolution fork), and find that Latte has just the right level of intelligent templating for me. Together with the Processwire API, it means I've been able to replicate pages without constant hopping in and out of PHP and, so far, without having to write a single database query. KP
  8. Thanks for the tip! The big bold button is what I need. Site is Ascot Brass, which I converted from a gruesome heap of tables within tables to Clipper a couple of years ago when asked to become webmaster. I decided to try it out as my first Clipper to PW conversion when faced with creating the Members page. Use of templating in Clipper made it reasonably easy to do the original conversion; and I've found the TemplateLatteReplace module suits my way of working in PW. KP
  9. Newbie question: where? How to access it? Your module looks to be just what I need. I recently converted my brass band's site to Processwire (from Clipper, using Latte templating, but that's another story), and am extending it to allow a private Members area. I'd like some others to be able to add notices about rehearsals etc. I've managed to make a simple front-end form that lets them create a new post comfortably from the front end, entering date and a brief title; it then takes them to the back end if required to add full details and file attachments. I want them to get back to the main members page on completion, so the module looks a good fit for that. I'm just curious what and where the built-in functionality is.
  10. Ha! Now I have another ten pages to read, along with those 30 designer depot etc. articles piled up in my inbox and a couple of issues of .Net gathering dust under the bed. I'm actually working on ClipperCMS, a fork of Evo, now, and it's while researching something that cropped up during a write-up of its API that I found your post. I suspect it's what I needed some time last year to help me make sense of PW, since my brain has been rewired to view the world from an Evo standpoint. And now I'll have to read it and have another look. Pretty much like MODX, in fact - my first reaction to that was: "Oh no, another CMS that keeps everything in the database" (after finding Joomla site after Joomla site like watching paint dry as the page built up from bits & pieces). Something spurred me to have another look at MODX later, and I latched on to it immediately second time around. I'm pretty committed to Clipper, I think it has a great future for Evo fans, but I'm sure it's worth having a go at PW as well, and your guide could well give me the boost I need to do that in a reasonable time. TVM! KP
  • Create New...