Pete

Using ProCache by any chance?

Just thought I'd jump in and say thanks Soma - wasn't aware it took strtotime keywords! Always learning

Shopify looks like it has a very extensive API - best of luck with the project

I liked fartscroll But in all seriousness, this site is very handy, thanks!

Updated this to v1.0.6. You can now add optional roles that can bypass maintenance mode (superuser will always bypass regardless of whether it's selected or not!). @ceberlin - this should help with your scenario

Pretty sure it's not a PW issue - I develop on my local SSD and upload to servers all the time, and vice versa - so would assume it's maybe a corrupt image like Wanze says.

Of course, you could just as easily have created a new template for slideshows called "slideshow" and in the page settings for each of those pages changed the template from "basic-page" to "slideshow" rather than doing conditional logic based on page names. Might be less confusing all round unless there was a specific reason you were doing it this way? More on templates here, specifically the third paragraph: http://processwire.com/api/templates/

Just a note to all MODx'ers - I think this is a nice way to transfer some snippets/chunks to ProcessWire as well if people want to go down that route and have some they used to use in body text. Obviously it's not quite the same thing (potentially more powerful depending on your needs), but anything that helps make a transition easier is good in my book Very useful, powerful module ryan!

Loved this - thanks for posting it as it applies to businesses of all sizes.

This is the module Antti refers to - very good work https://github.com/apeisa/ProcessUserExtended

Finally merged some updated from Teppo - thanks! Now includes multisite support: http://modules.processwire.com/modules/markup-sitemap-xml/

This module is now complete: http://processwire.com/talk/topic/3743-processemailtopage/ Thanks to Jason for allowing it to be released to the community

Hi all This module was sponsored by Jason as per this topic: http://processwire.com/talk/topic/3566-email-image-module-development/ It's quite similar to horst & ryan's EmailImage module, but supports multiple email addresses for sending emails to different parts of your site, also allowing you to select different templates. There is also a delimiter option whereby you can split up the email's content and have text appear in the body or sidebar etc. Here's a video to show you what I mean. The video may well be of interest to other module authors as I used some Ajax to push what can normally be done in the module config - hope you like it There was the temptation to build on the EmailImage module with this one, but I already had code for my Helpdesk module (work in progress) that parsed emails using Flourishlib and wanted to use that code instead for this one. EDIT: Also worth noting is that unlike the EmailImage module, this doesn't come with a pre-built gallery template for the front-end. This is intentional as you could pipe emails into any part of a site you like, so I couldn't make assumptions as to usage of the content. You can download it via the modules directory.

Or: <img src="<?php echo $pages->get("/site-settings/")->site_header_banner->first()->url ?>"> Just used first() as an alternative to eq(0), but depends on your preference of course.

And it's already got me wondering how easy it might be to build the presentations in ProcessWire and use this system... Hmmm....

Last update to core classes was 9 days ago: https://github.com/flourishlib Admittedly it was a while between that and previous updates, but since it still works then why not use it? I do.

It might not be a bad idea to mention it on the module page on the site at the start so folks writing their first module will read it though. I think modules in ProcessWire will attract those with relatively less coding knowledge because it looks fairly easy, so even just a short paragraph starting with "a note about scope..." might be an idea with a link for more info. Assuming people are starting their modules by reading that page first of course Could also have a comment in the Hello World module about it, but I agree that sooner or later you will have to draw the line or you could have more comments than code very quickly

Joss and I are a little behind Matthew then on page 1 We do have a rough idea of what will be in it but I think other projects have pulled us both away from PW for a while so I will touch base with Joss soon.

Thanks - that will help me when I've got my jQuery goodness sorted that adds new rows of fields.

I think that purely because it varies so wildly from individuals up to agencies, plus how complex the job is (a forum setup in one software is easier than another, similar with styling) you might have a hard time getting responses to this manviny. In my experience, no two jobs are ever the same, even if someone wants the same as a previous client

Hi folks I was just wondering what the best way to handle multiple key/value pairs in a module config would be? For example, in a few modules I will likely need to enter information in a text field and then select an associated page, but up to as many times as the administrator requires. The simplest way would be to use a textarea and go the CSV route and type the page paths manually, so: option1,/path/to/page/ option2,/path/to/another/page/ Whilst this way of doing things is fine, I wonder if there's another way (doesn't matter that it essentially gets saved as a CSV behind the scenes - it would just be nice to make the config simpler to use and remove the chance of typos in paths I'm going to have a crack at it with some jQuery as I've just had an idea, but if anyone has any other suggestions I'm all ears

Well I'm 50/50 over posting budget info ryan, but I admit it did make me respond quicker knowing someone was not expecting something for little money. Definitely worth mentioning if you're happy for the code to be submitted back to the community as that was quite appealing too, though obviously it doesn't suit all circumstances.

Kept editing my post so there might be more there than when you last read it

I'd be interested in taking this one on. Timeframe is more than enough, changes required to the module aren't that tricky either. I don't think you're wanting to do this, but you could assign a different email address to a different section of the site or something if you wanted to handle different blog categories, or else something could be done with category title as part of the email title like "Post title||categoryname" and split on the || Lots and lots of possibilities.

I wouldn't do any integration with other IPB apps though - just the core member/forum ones I think as I'm trying to cover the most common needs. Looking at Vanilla a few times the last few days, it has a very streamlined feature set for more basic needs and the API is good, so I might stand back from IPB and all its bells and whistles, work out the main things I want in my module working with Vanilla and then do the same feature set for IPB. That way there is the option to use either a neat, small forum package or a huge one.