diogo

http://irclog.whitequark.org/ruby-lang/2011-11-29 this helps?

This looks like a wordpress forum with all those the_variables

never saw that thread! Or at least I don't remember... Of course it would be great to have all that functionality coming from a ready file, instead of having to make a server call

I love this module Soma!! Everything seems to be working perfectly Maybe you should refer on the instructions that the module needs libcurl to work. I tested this on my localhost, and got an error because it wasn't installed. it does say it... sorry, should read things carefully before posting stupid things...

Soma's module manager wasn't able to get the file from the forum thread of my module http://processwire.com/talk/topic/1182-module-image-tags/. Meanwhile, I created a github page and all works now. I noticed that when I opened the link in the browser from the module manager, I was asked to login to get to the file. So, that's where the problem lives. The files from the forum are not opened to everyone, so they shouldn't be used on the modules pages as the download link. My mistake, but maybe there should be a reference to this on the "download url" field description.

Had this idea, but can't start working on it since I will go on vacations in some days. So, I just decided to throw it on the air and see if anyone will catch it Ok, the idea is to create a dynamic js file (or files) that would hold all usefull but not sensible data from a pw install. The files could hold, not only, some config info like: url, images folder, styles folder, etc, but also some pages variables. Here is the plan: (very embrionary) Config variables: This one is easy. All no sensible info from the config file could go there. Page data: Each page object could hold the url of the page. This would make it easy for a method to find the right object for each page. This page data could hold some chosen fields, the template, the children, the parent, etc... Page data could be added to the file on page save. Control: There has to be a way of filtering the data that goes on the file. This could be done on a page by page basis, on a template basis, and on a field basis. I guess a checkbox on each of those should do the job. Methods: And why not mimic some PW methods also? Maybe even creating a jquery plugin. Would be nice for sure What do you think? Any major downside of doing something like this?

I updated my modules and modules page according to those rules. Hope it helps.

I came late to this, but it's a great idea! Thanks Soma, Will try it right away! EDIT: on linux i will have to change all the combinations, Same problem as in windows of course...

Just submitted the pt-PT language pack and the Image Tags module. Everything worked well, they are just waiting for Ryan's approval.

Adam, is there anything new on this? Just referenced this thread on the other module page (no URL because it still has to be approved by Ryan) http://modules.processwire.com/modules/textformatter-image-tags/

+1 for Sublime I thought the name might be a bit too daring... but after using it for some time, i know it's not

I think there will be a vim storm coming from Ryan

Yep, that's what I did. Of course it works, there's no reason not to. And it took one minute to create, also true But I'm looking at it from the newcomer view... If I work with PW for some time already, and got pretty used to it's way of doing things. I can imagine that this should feel very strange to someone that has the need for something like this on the first project.

I stumbled on this only now. Never had to create radios or dropdowns in PW before I want to create a simple m/f choice with a radio button. How should I do it? Create two pages, one "masculine" and one "feminine" under a parent "sex"? It feels so overkill to me, even after being used to the PW way. I wonder if it wouldn't make more sense to have those two simple fields in the core.

This can be made automatic in the cache options.

Can't you allow the search for three letter words excluding "and"?

Downside to this is that, when there is a paid package (support, or some kind of pro version) people tend to think that the free version is somehow incomplete.

This is nice What happens if you create a new page with the same name of the one that was changed? It stops redirecting, I hope...

De nada

You also have to iterate the pages inside the page field foreach($page->banners as $banner) { foreach($banner->pagefield as $p) { echo $p->title; } }

Ah!!! Ok, i did a print_r on $fields->pagefield->data, and got this: Array ( [derefAsPage] => 0 [parent_id] => 1044 [labelFieldName] => title [inputfield] => InputfieldPageListSelectMultiple [size] => 10 [required] => 1 ) So, you can get the parent id like this: $fields->pagefield->data['parent_id'] And the children like this: $parentId= $fields->pagefield->data['parent_id']; $children= $pages->get($parentId)->children; edit: this feels a bit hackish. I wonder if there's a simpler way to do this in PW...

This happens because the page field is retrieving an array of pages, and not the page itself. You can solve it by choosing "single page" on the field setting, or by iterating through the result with a foreach(), or by choosing the first element on the array $page->pagefield->first()->children

I didn't know this. Thanks Pete!

There is a e-commerce module being developed by Apeisa. You can follow it here http://processwire.com/talk/topic/550-e-commerce-with-processwire/