• Content count

  • Joined

  • Last visited

  • Days Won


alan last won the day on April 19 2012

alan had the most liked content!

Community Reputation

354 Excellent

About alan

  • Rank
    Hero Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Ottawa, Canada

Recent Profile Visitors

11,807 profile views
  1. Ah, the todo list... I can see a Module now.., Tailer—it tails your log files. You tailor the rules and leave it to Tailer to alert you tor any phrase or limit that interests you
  2. Hey @arjen, sorry for the slow response. At the time I was only thinking of the server logs, but it makes total sense (thanks for the suggestion) to log/parse PW logs also, for things I want to know about. Sadly I have not moved forward with this at all :/ This seems an area (logs reporting themselves to you when a condition/keyword occurs) ripe for automation and likely to be highly beneficial, I am surprised I've not yet bumped into a great pan-log solution. Something I'd like to return to researching when time allows
  3. Thanks @adrian, I looked in the Modules list but totally missed your module (what am I like...). Bookmarked ✔
  4. Thanks @Soma, I just created an array in Sublime Text in 3mins and then used a for loop and a modified version your code to create 62 pages in a click, continually amazed by the simple power of PW. PS: This was my code, it's obvious/simple, but just in case there's someone looking for a simple example (caution, only call the function once as it just blasts new pages into creation function make_pages() { $out =''; $mypages = array("1st Degree", "2nd Degree", "3rd Degree", "Abdomen", "Allergic Reaction", "Anger And Indignation", "Animal Bites", "Back", "Bad Fish", "Bad Meat", "Beesting", "Blow To Eardrum", "Blow To Eyes", "Blow To Orbit", "Blow To Outer Ear", "Blow/whiplash", "Body Injury", "Breathway Constriction", "Bruises", "Burns", "Cold", "Crushed Fingers", "Dizziness and Vertigo", "Dog Bites", "Ear", "Emotional Upset", "Extremeities", "Eye", "Fainting/collapse", "Fall On Mouth/teeth", "Fear And Fright", "Food Poisoning", "Fractures", "Frostbite", "General", "Grief And Betrayl", "Head", "Heat", "Heatstroke", "Insect Bites", "Joint Sprain", "Mouth", "Muscular Strains", "Neck", "Nerve Injury", "Nose", "Nosebleed", "Overeating", "Overuse Of Alcohol, Drugs, Tabaco, Food", "Physical Injury", "Poison Ivy", "Puncture Wounds", "Rich Food", "Shock And Loss Of Love", "Skin Rash, Swells", "Snake Bites", "Splinters", "Stomach", "Sunburn/burns", "Teeth", "Throat", "Wounds, Cuts"); $out = count($mypages); for ($counter = 0; $counter < count($mypages); $counter++) { $np = new Page(); // create new page object $np->template = "app_nav"; $np->parent = "/app_nav/"; // or id or page object $np->title = $mypages[$counter]; $np->save(); } return $out; }
  5. Ditto szabesz; I would love to get into that lower-level approach and one day maybe I will get there, until then I have CodeKit to keep me warm
  6. In case anyone else encounters this, I am developing a site and using Under some circumstances CodeKit was re-processing files once per 2 seconds when it should do it only when it sees an edit made by me to a .scsss or .js file etc. The answer was to get CodeKit to ignore /site/assets/ As usual the dev for CodeKit was super-fast to make suggestions and one of those lead me to the fix. Thanks Bryan @ CodeKit
  7. I choose to have the 'From' as (the domain the site is on) and I ensure that domain is valid (good SPF, DKIM etc) then one validation and you're done.
  8. In case using Google for SMTP is the problem (perhaps Google is or may one day, restrict use?), a new account with Postmark gives you 25,000 'credits', but more importantly they are great for transactional emails.
  9. +1 to finding if there is a way to do this?
  10. @kongondo and @BitPoet, thank you guys VERY much for this—v3 compatibility, brilliant!
  11. This is happening again this Black Friday / Cyber Monday
  12. Thanks all. I should have said, these are invariably .mp3 files. I'm (slightly) stuck re the PW version as I am using @kongondo's brilliant Blog module which when I developed the site was not spec'd to run on v3 PW. I will return to this issue since I want to solve it (and understand it), but for now my two workarounds have been; upping the memory enough so the upload completes (albeit seems too high a limit) and the other solution that seems to work is the client uploads a small file, I FTP the large version over the top—not ideal but in this case very workable. I am sure using a form to upload a large file is not the best choice going forward, for very large files. If I had time I'd love to see if I could spec' out a sort of 'lazy upload' module for PW; making this up as I type, but perhaps something like a GUI to identify the upload and 'register' it to happen and a one-time cron-type job that grabs the file from perhaps a Dropbox or Google Drive like location. PS: Although I said I am pretty certain that on one of my tests I had to leave the screen for 20 minutes and when I came back it HAD completed, w/o needing a save to make the GIF disappearing process complete... I will test this again.
  13. I've hit this a number of times and it's one of the very few things that makes me uneasy in the PW world. Why? Because in the past I've felt like I just threw resources at PHP until the problem went away and the step change I had to make in settings always seemed both illogically large and also so big as to make me worry it might mean I am impacting the operation of the site (or other sites when shared hosting). So when a site recently hit this problem I tried a little more to see where the limits were and see if I really had to be so disproportionately generous with resource settings before getting it to work. It seemed so ?:/ Essentially I have some clients who often want to host files of 100mb, 200mb, etc size. I know I should explore using some other space for heavy lifting of files and perhaps thats THE problem, but I would love to know (is using the PW Admin to upload files of 150mb, 200mb, 250mb unreasonable and it's always going to be an uphill struggle?). For example, a 166mb file. After making various php changes that I completely understand such as post_max_size from 16M to 200M upload_max_filesize from 20M to 200M memory_limit from 128M to 200M max_input_time going from 60 to 180 max_execution_time from 30 to 180 Essentially it looks like I need to move from these settings that make sense to memory_limit 655M before a file load would 'complete'* (memory_limit at 647m or less still fails). *When it works, at 655m, what actually happens is the load bar reaches 100% and the activity GIF rotating on the LH side stays visible, never disappearing and the File Description field never appears—unless I click Save, once I click save then, with the 655m setting, I'm all good and the upload is complete and the File Description field is visible - twice now it HAS completed AOK (the GIF disappearing and the 'Description' box appearing aok), it looks like I just need to leave the page longer, not timed it as both times it's happened when I've gone off to do something else. Will post a reply if/when I find more in case helps anyone. PW is 2.7.3. I'm posting this as much to document it as seeking answers, but I would love to know why I appear to need such a disproportionately large jump in settings to allow larger files. For example, I had the exact same error when using a 256mb file and to get its upload to 'complete'* (*all good but need to click save to loose the GIF) I needed to set memory_limit to 850. Seems a lot and I don't understand why... Hope this helps someone, if I find more I'll post here (though I spent a couple of hours+ already experimenting & think I am running out of ideas ATM).
  14. I've got a persistent case of this: I can login AOK if I use an incognito window sessions are stored in the db I've tried clearing out my browser history, cache etc, but clearly PW is now remembering something about my normal browser and not liking it. Is my only option to permanently change "CSRF protection" and "session fingerprints" settings (which is sad as I used to login here AOK and didn't need them changed before), or, is there something I can do on the hosting or in PW to clear out PW's memory of my browser (assuming that is the problem), as noted, I *can* login with incognito. Thanks friends and sorry if I missed something obvious (and hope the answer helps someone else :)) EDIT Even though sessions are stored in the PW database, I checked /site/assets/sessions and found two session files o_O Deleted them and now can login OK. Confused but happy
  15. I may be interested if I get into vue.js (not had time to look at it yet sadly).