Pete

Just finished some more stuff for the ProcessWire site which I'm about to send to ryan for his perusal before it gets uploaded, possibly early next week. Just a bit of forum/site integration that looks quite nice, but the code is a bit sloppy so I'll not upload it until it's been checked over I'll be working on the Twitter module again in about 20 minutes and hopefully it won't take me long to complete - maybe an hour or two. I should warn you that my self-imposed deadlines usually suck though, sorry

I know what you mean - many times I've looked for a complicated solution where a simpler one would do in ProcessWire.

Thanks ryan, I'll have a look at that when (if) I get some free time

Nice - I like these setups because it's obviously far less updating to deal with in terms of the core code, and they are indeed mostly on the same server in my case as well. Thanks guys

Hi Nico Sorry for the slight delay with this. I said a couple of hours, but it's now been several days (forum upgrade being my main distraction). If you can hold on a bit longer, I will be looking at this again on Saturday definitely, but this week is a bit hectic at work for me to looko into it sooner unfortunately.

I'm intrigued by this - can you go into more detail? It sounds great, but I can't quite visualise how it works from a domain name point of view or a technical point of view.

Ah, that'd be how I missed it - thanks

Sadly I've just done this and can't remember how to get it back again

That must be a bug in the skin I think (not one I've made ). I could fix it probably. I would have thought the option to hide it was controlled by a cookie but obviously not... No worries. I used to keep switching to the full skin on my iPhone, but I'm getting quite used to the mobile skin as it's a lot faster on a limited connection

If I remember correctly, you can also change that limit - I think on one site I've got it set at 25 before it paginates.

I like it - I think I had the necessary steps in my head, just not the necessary coding skills (regex makes my brain hurt every time I have to tackle it). This script, with a few modifications, could probably be used to redirect most old urls to new urls on most forums, so it's definitely useful and thanks for posting ryan

Definitely like the earthy feel, and the nice rollovers. Good stuff!

Good shout - in fact it will mean anything on Github that links back doesn't work, but I think ryan may have a plan involving .htaccess for this (but changing the links would be helpful too). Unless another moderator beats me to it I might see if I can do a search for links and update them tonight.

Hehe, with great power comes great responsibility

You're not going mad - there was a final step I forgot to complete last night. I realised what it was at midnight, but it was a bit late by then. Welcome to the forums by the way They should all be visible and working now - fixed them about an hour ago.

Well spotted - there's another setting I need to change that I forgot about. Don't worry though, whilst your post counts won't increase til I sort it there is a recount button so it'll be showing correctly sometime tomorrow.

There is already a mobile theme if you check it out on your phone. I think there's also an app that links into this software to make the mobile experience slightly faster, but I might need ot alter some settings before we look at that. I've already got a list of style issues and hope to squash them by this time tomorrow, so if you spot any more after then that look really odd then please do let me know. EDIT: I've just fallen in love with the quote feature - try clicking quote on a few posts and watch it do all the hard work in the reply box. I've used this software before, just not updated the other site I use it on to this version so a lot of this is new to me too

There isn't currently a hook, but I was going to write one (for Twitter at least) and use Tijs Verkoyen's Twitter oAuth class that I've used for other stuff before: http://classes.verkoyen.eu/twitter_oauth You will need a hidden custom field in which to store the twitter status ID (and Facebook's equivalent, but I can't help you there as I inly know about Twitter in terms of the above class). For such a module, the steps I would take in the code are: Add hook after page save Check to see whether page status is published Check the hidden twitter status field - this stores the unique ID of the tweet If it's empty, add a tweet If it's not empty, do nothing Similarly, you might want to automatically delete a tweet if a page is deleted, otherwise you will have issues with tweets linking back to non-existent pages. Personally I would make this a configuration setting in the module so you can decide what to do for your particular scenario. The steps when a page is deleted (and I would say deleted from the trash - not just moved to the trash - just in case it's an error) are: Add hook after page save Check to see whether page has been deleted Check the hidden twitter status field - this stores the unique ID of the tweet If it's empty, do nothing If it's not empty, delete the tweet If you don't mind waiting a few hours, I need to build this module anyway so I might just do it this afternoon. Then you could use it as a basis for a separate Facebook version if you like?

It's actually: $page->httpUrl and that gives you the full URL to a given page, with http prefix.

No problem My first thought was making it something you can set per-template in the template settings, but that sounded too difficult and you would have to write some code when editing a template to check it has a cropimage field and then have a setting just for that. It also seemed too detached from the field itself. My second thought was to define it per cropimage field as it would be a bit more intuitive editing it there, but I don't like creating duplicates of the Images field just for things like this where you'll only ever define different settings once or twice in a website's lifetime I think. Which brings us back to the module configuration itself - seems to be the most sensible place and certainly the easier option to code!

Antti - just wanted to say I've (finally) just started using this module and it's amazing! Great work! The only suggestion I have is that it would be nice to have a way to make the configurations for thumbnails somehow able to link to certain templates, for example if I want a specific thumbnail size for news article images then I'm unlikely to want that thumbnail option anywhere other than when I'm creating a news article. I know, it's not straightforward, but rather than make it too technical, I thought maybe this could still be specified in the same place, but add extra parameters on the end if you want it only available to specific templates: thumbnail,100,100 portrait,100,150 largethumb,200,200 newsthumb,250,180,news_home,news_article In the above example, the first three thumb settings would be available to all cropimage fields, and the newsthumb would only be available to the news_home and news_article templates. Something like that anyway, and it's just a thought (although it might be worth somehow being able to specify fields as well as templates?).

I keep forgetting about Chrome Frame - thanks for reminding me as I can think of one site where I could offer that as an option other than telling users to simply upgrade.

That's what's always bugged me - one site had about 5% IE6 usage a few years back but I had to still make the site work in IE6 because 5% of 200,000 is still worth catering to Hopefully most system admins will not know about the automatic update program. I'm a system admin at work, but we only use the latest software anyway

Cheers ryan Forgot I had a Github account for a sec there. Added, updated the link in the first thread and added it to the growing modules spreadsheet on Google Docs Yup - I'll probably make the time configurable at some point in the future as it seems like an easy interim update before doing anything more complicated.

Very good point - I'd completely forgotten about that! One of the forum applications I use has this though I'm quite far behind on the versions. I believe they had one for forums, one for posts, one for calendars etc. It would have made more sense for them to split up posts by forum though as it gets a bit silly if it tries to put a million posts in one file (I don't have that problem fortunately ). So thinking about this a bit more, it would make sense to have some template settings for this module too in a future version and specify cache times and re-index periods for all pages there. It could then create separate sitemaps on a per-template basis as you say. I think that would cover most eventualities there. My only gripe would be that caching per-template wouldn't help if you were running a large blog/news site as one main template would apply to most of the content. Perhaps splitting it per year, or simply having it split the sitemap at X thousand pages if you have a huge amount of articles? I think per-year sitemaps for larger article sections would be best thinking about it. Presumably if a page from 2009 is modified and then ends up in the 2012 sitemap it's not a big issue - Google will be told in 2012 sitemap to index it again and it's not like you're going to modify old articles particularly often so I wouldn't see a need in cleaning up the 2009 cached sitemap in this case. It does look like you can easily have a master sitemap linking to sub-sitemaps though so that part is pretty straightforward at least (and it looks like 50,00 pages per sitemap is the maximum allowed): http://googlewebmastercentral.blogspot.com/2006/10/multiple-sitemaps-in-same-directory.html Anyway, this is one for when I next get a few free hours