alan

Hi Bill, Ever since I found Susy I've not used any other. I'm not a Flexbox user so can't comment on that, but Susy + SASS is a delightful combo, good luck to you Cheers, -Alan

@horst — you're boss

Horst, please can you tell me where the changelog for 0.2.2 is (I checked the usual spots), or am I safe to assume any _ . _ . N level change is so minor I can always just install it without any other checking on my sites etc? Thank you

Thanks Jan for your take on this, and welcome to the forum! I'm the other way, I don't work in hosting, only use it, so I am assuming that the Bitnami 'layer' will help reduce my learning curve. I am going to put a site on Bitnami+Google to see what I find. If I find a 'rule of thumb' guide to costs along the lines "If your VPS use is this then your cloud hosting cost would be that" then I'll post that here as that's probably the deal maker/breaker for me (since I assume the hosting experience will be roughly comparable to VPS).

I don't know about Debian but you can install and run PW in the cloud, powered by Amazon or Google via Bitnami. And by significant change I was hoping significantly cheaper

Has anyone gone from a VPS type hosting setup to Bitnami running on Google (or Amazon) and found a significant change in cost? Wondering if I ought to junk my traditional VPS hosting and move sites to Bitnami + Google (will be testing one soon as never tried bitnami other than a 1hr demo). Cheers! [clicks a virtual beer]

@kongondo You're generosity at making this excellent module available and providing all the help you do is so much more than one should expect; NO problem re [Hope to get some time soon to look into your questions...sorry...] thanks again for this module and good luck in all your endeavours, cheers

Hi kongondo, Sorry to bother you with a question and thanks if you get any time to answer If I use the Auto-publish from... field and its date-picker the field gets populated like this 2016-05-16 hh24:05:ss on clicking Save and keep unpublished I see a session warning/info Session: The parsed time was invalid (value='2016-05-16 hh24:05:ss', format='Y-m-d H:i:s') I can manually clean the format or delete out all but the date and all is OK. Blog is 2.3.9 and PW is 2.7.3 If there is more I can tell you or you'd like me to try something then I'd be only too happy to. Thanks in advance for any pointers on if I can fix this somehow (I looked at settings of the publish_from field etc but it looks like template blog is overwriting them and when I check there there it looks like they're locked down (not that I would lightly go around editing such an area). Cheers, -Alan Edit: PS it looks like the Save and keep unpublished cleans the field to something like 2016-05-12 00:05:00 and so I guess the session warning is for my info and the sanitizing of the field chose some defaults from the 'bad' data. Hope that made sense :/

Hi Peter, here's the settings I use https://db.tt/hEmrTdLD. One gotchya just in case your test is a not fully up-to-date version of SCF.

Hi Peter, Yes I am using it with Horsts WireMail SMTP module and it does work, I've converted 5 or so sites over, all AOK. I'll grab a screenshot of the setup page and post it here in a sec... Before I do, one thing to check in an emails header is "mailed-by: pm.mtasv.net" - if I see that then I know it's come via Postmark.

No Steve, not seen before but it looks very nice. I'm very happy with Postmark and yesterday spent a while converting Textpattern, Perch and PW sites over to it, so I'll likely stay there now. But if they do something like MailChimp made Mandrill do then I will certainly check them out—thanks for the recommend!

I wrote to them (even though I knew it would make no difference) in order to note that for my use-case [send very few emails per month] the new price model was completely inappropriate; I used about 2% of the potential emails I had to pay for per month; 98% of my fee being effectively unused. The next month wash and repeat. I went from being a fan to a lost (low spend) client. VERY happy with http://postmarkapp.com/.

Thanks @justb3a if that kind offer to document was re my possible use case, most appreciated Right now I have sidestepped the requirement but if I find I need it and can't work it out I will reply here in case you have a chance to doc then PS: I am using latest production 2.7 PW and latest 2.7 ver of your module (I can't move to PW 3 as I am using @kongondo's fabulous blog module which I think is not fully ready for PW 3 (sorry if I am out of date on that assumption).

Hi @benbyf, I had the same situ until I spotted that I had not followed the instructions properly, maybe you did what I did—I copied the file `simple_contact_form.php` to a new template called `simple_membership_form.php` but then forgot to create a new corrosponding template in the PW admin. So I did that. That nearly fixed it but I guessed perhaps the plain template I had created was in some way not like the one that ships so I deleted the template I'd made in the PW Admin and instead used the Admin to make a copy of the template that ships and then changed it's name and told it to use the file `simple_membership_form.php` and it worked AOK. Good luck! I had to stop using the form for a second form as the second form needed radio options and I couldn't work out how to do that I might come back to ask if it turns out I can't do w/o the form

Fab kongondo, thanks!

Thanks kongondo re and I'll check if it auto installs and then follow up and ask a Q on github re the core, if I find anything helpful I'll post back here

Thanks for the suggestion, glad I've not missed something silly. Can I check—should I have installed FieldtypeComments prior to Blog or does Blog auto install this? BTW Blog is such a comprehensive and polished Module, it's almost doing it a disservice to call it a Module, it's more like a mini app; thank you.

Yes, I have code to reset passwords for users, send info to users etc and that works AOK to send emails on the same site. I hope I am remembering this correctly, but I think the sequence of events was: installed the blog test comment saw the comment listed in the blog control panel but no email dug around to see where one listed where an admin email ought to go (I should have done this 1st!) thought I didn't have the comments field type installed and so installed it (was its presence a pre-req' of installing the blog and I missed that step?) checked the field blog_comments and found it was the correct field type and listed a bunch of blank fields where I was able to list an admin email address etc did more comments, all worked AOK in all respects other than sending an email Does that help at all? Fair enough! And no problem with this since I've taken an alternate route and am using the FieldtypeSecureFile module to side-step that

ugg... sorry to follow this up with ano Q I've noticed that if I edit a users page e.g. Admin > Access > Users> Elvis Presley and use the Images field to add a bio photo, when visiting http://example.test/blog/authors/elvis-presley/ all is good except the image that got stored was put in a folder called /site/assets/files/-1041 i.e. the folder chosen when the image was uploaded is one that is prefixed with dash/minus. I assume this is what is stopping the image being shown. Really sorry if this is something I did somehow but any suggestions where I go to ensure users created stop having image fields that store their files in '-' prefixed folders? Thanks in advance for any pointers, cheers, -Alan Edit 1: Perhaps the answer is that I have $config->pagefileSecure = true; in config.php? Testing to see... Edit 2: Confirmed, removing the above allows blog profile images to be seen. Any pointers on how to have the benefits of $config->pagefileSecure (or some other mechanism for protecting files) while not breaking blog bio images? Thanks again for any clues Cheers, -Alan

Is there more I need to know/do in order to get comment notification working, right now I have a PW site that can send emails AOK but no email is sent when comments are submitted. I have edited the field blog_comments in the admin and listed an email address under Details > Notification > Admin notification email. If relevant, I submitted a test comment before I had added the email above. Since adding the email above I have retried several times and no emails sent yet. I've Googled quite hard but no luck, sorry if the answer is simple and I missed it :/ PW 2.7.3 Blog Module 2.3.7 Thanks in advance for any ideas! Cheers, -Alan

Just a comment about stating both a name and a title here. If you set both then it's up to you to ensure that the URL of the page is unique—heavy caveat, I think I am correct in stating this... Certainly I found an error on the 2nd page creation (with some super dumb test code that did not even try to create unique URLs for pages; so probably not unexpected!), but then I was looking at how to make pages unique etc when I found I was trying too hard... I noted the error I was getting and Wanze's comment that solved my problem here, short answer, don't set a name and PW does it all for you

I was using Soma's lovely example of how to create a page via the API and began AOK then started getting Fatal error: Exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'mynewpage_url3-1075' for key 'name_parent_id' (in /wire/core/Pages.php line 2103) #0 /wire/core/Pages.php(2103): PDOStatement->execute() #1 /wire/core/Pages.php(1161): Pages->executeQuery(Object(PDOStatement)) #2 /wire/core/Pages.php(1055): Pages->savePageQuery(Object(Page), Array) #3 [internal function]: Pages->___save(Object(Page), Array) #4 /index.php on line 248 Then I found Wanze's super comment Problem solved! Posted this just in case a Google search for that error helps someone else.

@JasonS The docs are almost all visible here.

Really looking forward to trying this, thank you so much gRegor, and for drawing my attention to the fact that the W3C had a spec on this, fab!

Thanks @Pierre-Luc for this, I use MAMP on a Mac and found the dependencies were present by default, and they are on my hosting also so I tried your module and it works exactly as I hoped; thank you! (and "Hi!" from just down the road (Ottawa )