Soma

I use those naming conventions also in certain places for image or file fields and I have no problems.

I'm not seeing through all this but have you seen this http://processwire.com/talk/topic/1421-twig/ ? Maybe something in there helpful? I'm not sure there's another method like you have now, but then I don't care about template engine anyway On a side note: "Instead of contaminating your template's and chunk's markup with php code, you would have the Twig templating syntax at hand." Should read: "Instead of using powerful ProcessWire template syntax code in your template's and chunk's markup, you would "contaminate" your templates with the Twig templating syntax." Sorry but just had to

Just set the value of the field like: $field->attr("value", "121-22"); or multiple I think: $field->attr("value", array("121-22"));

Only if you take HelperFieldLinks, FormSaveReminder, PageEditSoftLock too @adamspirit I'll make a pullrequest to add support for Fredi.

Then there comes Fredi and you can edit them from the front end. Just to make a little example. If you output those repeater on front-end you simply do: foreach($page->myrepeater as $rep){ echo "<div>"; echo "$page->title: $rep->title<br/>"; echo $user->isLoggedin() ? $fredi->setText("[edit repeater element]")->renderAll($rep) : ""; echo "</div>"; } Make a custom admin page that allows you to edit them. Endless possibilities.

I added a check at that place for and you might want to get the following module file and let me know if it's gone. But as said I don't understand, that when it gets that far there's should be a object. Can you tell what file or image field there is where it throws the notice, maybe I understand little more. But nothing dramatic. ChromePhpLogger.module

Ehrm.. I'm looking into this closer and now reading again your post, it's not an error but a only a notice. Further it's in a strange place where it cycles files/images field and I can't reproduce this and can't think of anything atm. Also it seems I get tricked by my own modules an PW. This actually works with cached pages?? Which means even if the page is cached and I'm not logged in it shows the details. Long time since I wrote the module but I think it's simply that the module loads the infos to output as PW even with cache on needs to know what page it's loading". Funny. I would have thought it wouldn't work with cache. Well then with ProCache it wouldn't work.

Thanks jonathan, I will add a check to exit on cached pages. Haven't tested so far with cache on, and if logged in there's no cache. Also I thought ChromePhpLogger only executes when logged in anyway so I'm a bit stumped. Edit: But remember now that I let it on to test with guest or other users. But with cached pages there's no things to debug/log

Does this happen for all modules or just the one you posted? I also experiences rare cases where the downloaded zip is corrupt and it isn't able to open it (it's where the message comes from. If it happens always, it looks like somethings wrong with your php and I have no idea what could be wrong. Have you tried doing it with a manual or different script to open a zip file?

You got the who and what but not the where. Access is defined per template and inherited. So simplest is to edit home template and define access for your new role there.

Only through JS.

Maybe I'm missing something but when I add a fieldset field to a repeater field it does not work, the _END isn't appended. But when using the repeater the fieldsets show, just not closing. Is this a bug or a feature?

I just went and added support for pagination. I pushed the update to the dev branch of the module you find here: https://github.com/somatonic/ModulesManager/tree/dev Still working out on the details for categories. Currently it just filters on a per page basis, so it possible there's a page not showing anything if category filter is set. Once you changed the limit in modules settings, you should hit refresh first on the ModulesManager screen to delete all cache files. It will create a cache file per page. So it all works now with unlimited modules but still need some work and I'm waiting for the JSON feed from modules.processwire.com to allow for more filtering.

I think we need additional filter param for filtering by category. This would help creating the category filtering in ModulesManager a lot.

@alexl Thank but this has nothing to do with ModulesManger rather than the http://modules.processwire.com/export-json/ Ryan has limited to 200 max. So Ryan needs to update the service to allow for max >200. Of course a limit makes sense and I'm not sure how to deal with the ever growing list of modules. We need to find a solution to keep the list short. - pagination (not sure how) - per kategorie listings only (at some point will maybe exceed 200 too) - not sure ... Currently the json file is downloaded and cached. Also I'm seeing now that Ryan includes the "readme" in the json array too, which makes it a whole (whole!) lot bigger and longer Maybe we can optimize this more to get a listing with only meta data, and a way to get more details on request. But not sure yet. edit: just seen that the feed support pagination already, but with that I would find a way to cache per page... anybody?

Thanks Ryan for looking into this. I can confirm that it works for me in php 5.3.1.

Minor update 1.0.3 to fix delete (move to trash) page button throwing the alert when form was modified before.

That sounds strange. And other modules work fine?

What did you do? That sound not like a problem we are aware of. What version of PW? Because the line isn't where this problem would appear. It sounds more like your PW install is corrupt, missing files or whatever. Try putting in a new wire folder.

We got a thread with this http://processwire.com/talk/topic/3601-field-label-language-problem/?p=42693