Martijn Geerts

I guess you don't POST the name submit. So $input->post->submit is not there, resulting in a false

WireMail is core and mails with the default PHP mail function, WireMailSmtp and WireMailSwiftMailer extends WireMail, when installed one of these will be used as mailer. WireMailBranding, is just a convenience Module that wraps markup around the HTML you want to send. Here wireMail function binds to the MailObject. (That is why wireMail() is a function call) https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/core/Functions.php#L797 Here's the WireMail class https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/core/WireMail.php I don't understand this one use what you need if it makes sense.

@tired_eyes, everything ends but ProcessWire just stepped in a new era and is not likely to go away soon. The 3.0 step will be a big transition but for building sites (writing templates) it's not going to change anything. I don't know any system that's more consistent and simple to use, yet so powerful. Say your PW journey ends over a year of 5 you've gained so much `ProcessWire` knowledge, you will realise then that you fully mastered the language PHP.

In ProcessWire we have Hanna Code and it uses almost the same syntax as in MODX except those are snippets and chunks in one. Hanna code runs from disk, while MODX snippets are eval()'t. (is that a good word ? ) You could also create a page with a footer template and just render that page in your template with $yourpage->render(). After a while you will discover more options to do things, just give your self the time .

Bug fix where the module didn't served the wrapper at all. Updated the first post.

[[!ProcessWire? &var=`Stable, fast, powerful, consistent and makes you smile.`]] And doesn't use silly snippets

My main concern to do it serverside is caching and it is always 1 step to late. I prefer JS solutions for conditional assets & markup.

Sorry bout that.

Thanks stepping in here Ryan!

Ok... so $oldPage = $this->pages->get($page->id); won't give you the old page? I have somewhere implemented that and it worked. (or I introduced a bug )

I had the presumption that Pages::saveReady hold the values from the to be saved page (runtime) and not the value out of the database.

To be fair, i've already set this module to be deleted 2 times, but somehow it won't delete. Better to go for other options like Kongondo's matrix field or use the Profields. There's big change that there will be Data loss when using this module as it relies heavily upon Javascript.

boh boh...

Still I think it's weird that you have a broken (not closed) meta tag. <meta name="description" content="Just Right Marquee Hire for Weddings, Parties and Events in Oxfordshire, Berkshire, Buckinghamshire, Hampshire, Wiltshire and Gloucestershire." <link rel="publisher" href="">

for me too.

When I see strange things I really can't explain I check if the file is corrupt. And second I use https://validator.w3.org/nu/?doc=http%3A%2F%2Fjustrightmarquees.co.uk%2F to see if there's a markup issue.

Your meta description is probably not encoded or whatever it breaks somehow.

Thanks @gebeer to correct it !

Please search google for this: processwire Error: Maximum function nesting level

I have to add that documentation at code level was always good, but lately, it's becoming even better.

He's using a page https://gist.github.com/jacmaes/6691946#file-form-php-L74 And it is saving the page (that creates folder) then adds the image and saves again. https://gist.github.com/jacmaes/6691946#file-form-php-L91

In which file have you placed that code?

Without looking much into this I do think the file input expect there to be a Page with a folder to store that image.

Also have to mention that using the $_SERVER[REQUEST_URI] is a bug in potential when using it on an url like this www.domain.com/segement/segment/?name=john.

// Array of segments $input->urlSegments // Url segments string $input->urlSegmentStr()