adrian

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

What version of PW are you running? There were some changes made to fix a bug with 5.6 just before PW 2.5 was released, so if you are running PW 2.4, you should upgrade. Otherwise, let us know and we'll look further. EDIT: Sorry - Missed that you mentioned you were using PW 2.5 already!

I would probably go with JSON, but CSV could probably work too. HannaCode has an export/import function that you could take a look at. Another suggestion - you could have the ability to add new element declarations - most simply maybe just one per line in a textarea field like so: #element1ID : #990000; margin-top:30px; #element2ID : #009900; padding-left:10px;

I can't seem to reproduce here trying from the Children tab - sorry! But I figured out the publish problem - I was testing on an install with a not configured field. Publish works fine once that field is properly sorted.

I love this - I have been wanting easy skinning (rather than theming) for PW for a long time. One thing missing is the ability to color the entire title bar in AdminThemeReno - the menu icon and search box is a different class. Also I don't think it is currently possible to edit the sidebar colors? Only other thing is a typo - you have breadcrumbs spelled wrong. And, there are two entries for 6. Color Set 2 Awesome!!! PS You need to add a way to export/import settings so we can easily share

Interesting - I am not seeing that behavior, although I did see something like it with the API, but was fixed here: https://github.com/ryancramerdesign/ProcessWire/issues/425 What I am seeing is that I can't Publish the page when using the Name Format for Children option. Doesn't matter how many times I save it, unless I uncheck "UnPublished" - then it will publish. Unless someone else chimes in shortly with any hints, I would recommend a Github issue for Ryan and point him to this thread.

Sure, you can do something like this in your selector for date/time, which would return all results after the current time. find("your_date_time_field>".time()); For repeaters you want something like: find("title|my_repeater.my_field~=$q"); Hope the helps get you going.

Not really sure if this helps or not, but it seems like you have a field that doesn't have a fulltext index defined (stating the obvious I know), but if you can separate your search into two parts - one for fields that are working using ~= or *= and then problem field using %= and then appending the results of one search to the other, you might be ok. I think to start it would be good to figure out which is the problem field. Can you try listing the fields manually and work that out?

Check out PageTableExtended - works great for sortable content blocks.

Try this in your php.ini xdebug.max_nesting_level = 200 That should take care of the nesting error. The forged request should go away with a browser reload.

@Rob - going back to your original request - this is pretty much exactly the reason I built Batch Child Editor. It might suit your purposes better than a generic modal edit button.

Have you checked the permission on the templates that are allowed as children of the template assigned to the page that you are expecting a new button on? So the parent template must have Add Children and the child template must have Edit Pages and Create Pages for the author role.

Hey Ivan, Just testing here to confirm and the url segments are not being included in $page->url for me. Not very helpful I know - maybe someone else will have an idea why you are getting different behavior.

I handle this exact scenario with a combination a PageTableExtended for block content control and make one of those blocks have a FieldtypeJson field. This may not be for the average user since it initially requires pasting in CSV data, but once in, it is a nicely editable table and really easy for you to output formatted table exactly how you want. If your users are already trained up with Markdown then it may not be too much of a stretch.

Fixed in dev: https://github.com/ryancramerdesign/ProcessWire/commit/63692bdda65090032d4d5a0c29475263ea707bf7

Here's a modified version of Ryan's code that works: http://jsfiddle.net/29zwjbgs/

There is nothing really wrong, just a case of not very explanatory notices. Go to the edit page for the field and save it again. You might need to save it twice to get the message to go away. Some discussion about it: https://github.com/ryancramerdesign/ProcessWire/issues/582 https://github.com/ryancramerdesign/ProcessWire/commit/c1dd1b37e529eff4e5219d1b790275fe71771936

Thanks Martijn, I haven't had a chance to test yet, but I am sure you've done a great job!

Hi Thomas, Sorry to hear you are having a bad day Here are some thoughts on why you might be having issues with each of those approaches. My module - firstly this was never really finalized for general use (and hence not in the modules directory). I have made some changes to it that haven't been pushed to Github, so maybe there is something there, but I have also stopped allowing insertion of images into Texatarea fields on new sites anyways. I always hated the potential side effects and now with PageTable blocks there is a decent alternative that allows for flexibility without the problems - sorry getting OT now. It also uses the description field that is available when the image is uploaded, and not the one when inserting the image into the textarea, so is it possible that the main description field is empty? With teppo's module, did you remember to add it as a formatter for the textarea field? Edit the field - Details tab > Textformatters With Ryan's approach - that code was written for his Foundation profile and makes use of: $("#bodycopy p img[alt]").each(function() { Is your content inside an element with an ID of bodycopy? Hope that helps a bit.

Hey Peter, To avoid confusion, you should change the status of Admin > Pages > Image Crop to "hidden" so it doesn't show in the Pages submenu. I have reminded Antti about this (https://github.com/apeisa/Thumbnails/issues/23) so hopefully it will be fixed in Thumbnails shortly. Cheers!

Hi Dan, Sorry I don't have time to help at the moment, but just wanted to quickly drop you a line to let you know that there is some raw javascript appearing at the bottom of all pages on your website. Good luck finding some help.