Jump to content

Peter Falkenberg Brown

  • Content Count

  • Joined

  • Last visited

  • Days Won


Peter Falkenberg Brown last won the day on November 28 2019

Peter Falkenberg Brown had the most liked content!

Community Reputation

145 Excellent

About Peter Falkenberg Brown

  • Rank
    Sr. Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Maine, USA
  • Interests
    Web database application programmer, specializing in Processwire.

    Visit https://webdatabaseapps.com/ to hire me to do your custom web database application.

Recent Profile Visitors

7,995 profile views
  1. Hi, The Developer site is still broken. Can't log in. When I fill out my username and email at: https://directory.processwire.com/login/ it simply refreshes the screen without logging in. I've tried it in Firefox 72.0.2 and in Chrome. @ryan - thanks for looking at this. Peter
  2. Hi, When I try to log into the PW Developer forum to create a profile, it breaks and takes me to: https://login/ Yours, Peter
  3. @Robin S @netcarver Hi Robin and Steve, Robin, the method you outlined above, with the ready.php code, worked perfectly! Thank you! The module from @kixe generated errors, and after looking at a thread on it, I used your ready.php code instead. Using the date/time method in the field could, I suppose, encounter a race conflict, but in this case, there's only one admin user. @ryan Ryan: I do think this deserves the addition of the id field in the code, and/or a switch option to do this exact function, with the auto-increment id, especially to avoid race conditions. But... this works for me, today. Thanks again to both of you! Peter
  4. @netcarver Thanks, Steve, for your response. I'll dig into it! @ryan and Ryan and Dev Team: I really do think that this would be a fabulous feature for ProcessWire: - in every template, have a setting that could turn on a function to fill in the name and title fields with the auto-increment ID automatically, skipping that initial step where you see those two fields, and going right away to the main edit screen, where one would see the title value and the displayed url as the ID number. In my work with PW, there have been numerous times when I wanted the name and title field to only be the ID, and it was a pain to have to program around that issue. I think you'd get a LOT of positive feedback about this feature, especially if the setting was also in the API, i.e. add a record without having to specify the title and name field, but have them populated by the auto-increment ID. Thanks! Peter
  5. Hi Netcarver and Ryan and All, This is exactly what I'm looking for, I think. I have a client who wants to add page content quickly, with just 3 input field (publish_date, body, tags) and not have to mess with the title or name fields, which we want to default to the page id. Now, one has to type in something like "n" (for new) in those fields, and then change them on the next screen by hand to the generated ID field. I've programmed a user interface in a previous application (i.e. not using the admin pages), where I would fill in those fields with a temporary random number, and then replace them with the the actual page ids (I probably should have figured out how to grab the auto-increment number instead). But doing an auto generate function like this for title and name should, in my opinion, be an option in PW, like a setting for a template that says: "Check here if you want to bypass the title and name fields (on page creation), and have them filled in automatically with the auto-increment ID." That would be GREAT. Since that's not real yet, is the code above ready for production use, or is there something that someone else has done that will do this? Thanks! Peter
  6. Hi Jacmaes, Thanks for answering. Looks like Ryan needs to update his shop listings: ProDevTools doesn't list ProMailer as part of it. And there's no single site version over there either. Hmm... of course, Ryan must be incredibly busy. :-) I'll wait and see if a single site version of ProMailer appears... at least for a little while. Thanks again! Peter
  7. Hi Ryan, I'm intending to purchase ProMailer -- looks FANTASTIC. Do you have a "Single" version? I only saw Dev and Agency. Thanks, Peter
  8. Thank you all, for these comprehensive replies! I'll check out the links, etc. The right tool for the right job is indeed the point. So far, at least, I'm VERY happy with ProcessWire. Who knows: I may never need Laravel at all. Time will tell. Thanks again! Peter
  9. Howdy PW Gurus Who Also Know Laravel or Symfony, I built a few web applications with PW, and was very happy with the result. For example: - an email to web help ticket system, with a front-end login - a Linux account management and multi-server account creation app, with a front-end login and PW server scripts run from the command line - a complex business app to test the viability of business ideas against a variety of metrics and algorithms, with a front-end login. The front-end logins displayed pages specific to the app needs, entirely bypassing the normal PW admin backend. => My question is: since PW can build the types of apps above, what can Laravel and Symfony do that PW cannot? Thanks for any insights! Peter
  10. Hi Elabx, Thanks for that link! It answers my question completely. Form Builder looks like it rocks! I shall buy it. Peter
  11. Hi Ryan and All, I've been using a Perl script called "SimpleForm" that I've written and updated over the years. One reason I like it is because I created pre-processing and post-processing functions that allowed me to add any type of custom code I wanted to do, either before the data was processed as a submit, or afterwards. However, it doesn't fit into the PW framework, since it's in Perl. Thus, I'm exploring buying Form Builder, but in reading the feature list, I couldn't quite get whether it allows this type of totally customizable, code-able pre and post processing. I might have missed that, but can someone let me know if Form builder has that functionality? Also, I want to be able to collect and save data, then send someone to the free PayPal site, and then have the person return to a PW page where the form data can be updated "as paid." Has that been done with Form Builder? Thanks! Peter
  12. Hi Macrura, You are exactly right. I don't remember placing this line in the module backend data field "Default Link to XSL Stylesheet" "/site/templates/styles/rss_feed.xsl" but it was there. So, I removed it, and then uncommented the line in the module, and all was well. I suppose I could have placed that value in the data field: I just don't remember doing so, and never had that file on my system. Oh well... mystery solved, and the module has no error. It was human error! Oy. Ugh. Thank you VERY much for clarifying this. Peter
  13. Hi Dragan, Yep, that worked. This is the line that I had to comment out: /* if($this->xsl) $out .= "<?xml-stylesheet type='text/xsl' href='{$this->xsl}' ?>\n"; */ This would be a good thing to fix in the module, I do believe. This is one of Ryan's core modules, I think. Thanks! Peter
  14. Hi Ryan and Team, I'm using the module "RSS Feed Generator" v1.0.2, in PW 3.0.42. (I'm going to upgrade when 3.1 comes out.) I just noticed that my rss feed here: http://significatojournal.com/rss/ doesn't display anything in Chrome (but works in Firefox). (The source xml is being generated.) I also saw that Chrome requires an RSS extension to display RSS: https://chrome.google.com/webstore/detail/rss-feed-reader/pnjaodmkngahhkoihejjehlcdlnohgmp?hl=en so I installed it, but still nothing. I then went to the NY Times and saw that their feed worked in Chrome *if* the extension was installed. I compared the raw xml at the NY Times against the raw xml in my feed, and saw a significant difference. However, since the xml is generated by the module, I didn't really want to mess with it. Here are the two snippets from the headers. (The rss tree looks similar -- it's just the first set of declarations that look different.) RSS FEED GENERATOR AT SIGNIFICATOJOURNAL.COM: <?xml version='1.0' encoding='utf-8' ?> <?xml-stylesheet type='text/xsl' href='/site/templates/styles/rss_feed.xsl' ?> <rss version='2.0' xmlns:dc='http://purl.org/dc/elements/1.1/'> NY TIMES FEED: <rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:nyt="http://www.nytimes.com/namespaces/rss/2.0" version="2.0"> I believe that the module should be modified, for Chrome support. Any thoughts? Thanks! Peter
  15. Dear Abdus, That worked! Thank you! Really appreciate help from you, and BitPoet, and OF COURSE, Ryan and team for making such a great CMF! Peter
  • Create New...