adrian

$image = $page->images->get("name=picture.jpg");

I know nothing about the multisite module, but that first error suggests that the subdomains field in the module's config settings hasn't been filled out.

$modules->uninstall("ModuleClassName");

I haven't been following this thoroughly, but does this help? Soma suggested this to me for something a while back and it works well enough. // generate pager navigation using dummy array $dummies = $pages->find("template=basic-page, limit=10"); echo $dummies->renderPager();

Hey Joss, I thought you might appreciate this: http://www.dancingbearmusicfest.com/ And here is a photo of the "Dancing Bear", white patch, right in the middle of the Stawamus Chief: http://3.bp.blogspot.com/-BGfk41qTmrw/TmlOZo2bq_I/AAAAAAAAAB0/AuWMKVgn8H4/s1600/Chief.jpg

Hey Joss, Have you tried WireMail with horst's or teppo's plugins to make use of SMTP, instead of mail?

Glad it worked for you and that you sorted out the row width stuff. I haven't played with sortable callbacks for a while, but I think this is what you are looking for: http://api.jqueryui.com/sortable/#event-update

The 100 versions are for the admin - if you have "display thumbnails in page editor" checked on the Images field Input tab.

Or give up on RTE fields for images completely and use PageTableExtended for a content block type approach I have actually been removing the images plugin from CkEditor so that users can't be tempted I know that maybe sometimes this will be overkill to set up, but it is nice having complete control of how things will look. For simple sites, I bet ImageInterceptor will be very useful.

Apparently I like both sides of this argument What about doing this to the classname? strtolower(preg_replace('/([a-z])([A-Z])/', '$1_$2', $this->className()));

Hi Mike, Off the top of my head: http://modules.processwire.com/modules/batch-child-editor/ And the 2.5 core PageTable fieldtype. $table = $this->modules->get('MarkupAdminDataTable'); $table->setSortable(true); function TableSortable($table) { if(!$table.is("tbody")) $table = $table.find("tbody"); $table.sortable({ axis: 'y', handle: '.InputfieldChildTableRowSortHandle' }); }

Any chance it started happening after an upgrade to 2.5.1? There's a new setting for replacing existing files - not really sure, but might be worth a look.

Try it without the spaces before and after the pipe ( | ) character.

No problem at all - thanks for all the input and ideas!

Thanks again! I just spent some time revisiting this a bit. It's a bit more complicated that just removing trailing, commas, spaces, tabs etc because it is possible that these might be intentional if someone wants an empty value for the last field on the row. I have implemented a bunch of extra checks to make sure fields/pages etc can't be created without a name, so you shouldn't ever get the unnamed field issue anymore. I have also tried to make sure that the first row has no leading or trailing misc stuff so that the fields get properly created. But with the subsequent rows I allow trailing commas with nothing afterwards in case it is meant to be blank. I just tested with this mess and it looks to be fine: , ,Title, Number of Beds>Integer, Number of People>Integer, Kitchen Facilities>Text ,Single, 1, 1, Fridge Only, Double, 2, 2, Fridge Only Suite, 3, 6, Full Kitchen , Would you mind trying again at your end to see if I have still missed something? Thanks Adrian

Ryan is working on a very comprehensive changelog for 2.5 which will be published on the blog hopefully sometime next week when 2.5 becomes official. The current soft release of 2.5 will be superseded by 2.5.2 as the official stable version.

Hi seedle, Firstly, 2.5 is the current stable version so you should grab that instead. As for page/pages: http://processwire.com/api/variables/page/ http://processwire.com/api/variables/pages/ I am not really sure what information you need, but to clarify, wire('page') is effectively the same as $page, but due to PHP variable scope $page is not available inside your own functions, inside PW modules, or on a script that is bootstrapped to PW. That is when you need to use wire('page'). Same goes for all the PW variables: wire('input'), wire('sanitizer'), wire('user') etc. If you are wondering what $page and $pages are actually for. Basically, $page gives you access to all the fields on the currently viewed page on your site, eg: $page->body $pages gives you access to all pages on your site - you can query the pages you want using selectors, which are Processwire's version of database queries. It sounds like you might benefit from reading through some of the new tutorials: http://processwire.com/docs/tutorials/ and of course the cheatsheet: http://cheatsheet.processwire.com/ Hope that helps!

Thanks again Steve - great 2¢ suggestion I have set it up using your second option and I think it works great. I have also added a fix for the blank fields / extra commas issue. Please let me know if you find any problems with it.

After you have, convinced everyone that PW > WP (presumably that will be the outcome ), what about adding one more video showing how easy it can be to migrate WP content to PW using MigratorWordpress? Maybe Nico or I could help with that?

Yeah, that would be the problem I'll sort out a fix for that sometime later today when I get a spare minute. Thanks for discovering the issue. As you use it more, also please feel free to send through any other suggestions for improvements. I have to admit I am really enjoying the changes to suggested - it does make things cleaner!

Hey Steve, Sorry about that - I am assuming you are using Option 2 to create the selectable child pages. I am guessing there is a problem with my parsing of the comma separated field names / line breaks. I went for a very rudimentary approach instead of str_getcsv Can you send me the text you are using to create your pages so I can try to duplicate?

This sounds like a great idea - I am very intrigued by the enhancements you have added and would enjoy having them, but I honestly don't think I would ever install it because I like having access to the latest improvements to the core modules, rather than waiting for these to propagate to third party modules. I would love to see a way to extend themes, rather than needing full replacements. Maybe we need to propose something along those lines to Ryan? From what I understand Reno is an extension of the default theme, because you can't use Reno without default also installed, but maybe the process can be refined to make it easy to extend with some minimal code.

Take a look at Martijn's extended version: http://modules.processwire.com/modules/markup-rssenhanced/ I think that does what you are looking for.

Do you want to generate an RSS feed, or parse an external one and render it on your site? I think maybe you want the latter, in which case, take a look at this module: http://modules.processwire.com/modules/rss-feed-loader/

Hey Martijn, A little typo for you. The module shows up as: Fieldtype Json https://github.com/Da-Fecto/FieldtypeJson/blob/master/FieldtypeJson.module#L28