apeisa

Maybe tagging current commit with pw 2.3 tag and update master with 2.4 and up compatible. No idea how world takes it (modules directory, current sites etc).

Teppo, I read both, but finding time to actually respond and react is another story. Going through exciting, but busy times both home and work. I'll get back to you at GitHub. Looks good, only thinking about using conditional autoload. We do have that now, wouldn't it be as simple as defining template!=admin in module info?

Of course I am. I'm pretty sure uservoice.com servers will be shaking on saturday.

<little offtopic> Actually the best bet is to buy 299$/€/£ laptop, 199$/€/£ Android and iPhone and look all the sites through those. I think that will represent the masses (not the designers with their high end monitors of course). </little offtopic>

Great idea. Maybe something Teppo could promote through pw weekly also?

Kongondo, unfortunately there is not that much examples for more complex fieldtypes.

It should be default, just saying

For some reason the install routine has failed to create the page, and uninstall fails to delete the page that doesn't exists. Not sure why it fails in first place, but there are probably lot that can be tweaked at the install routine (code is little old already).

Roope: might work. Other option would be having separate repo that contains all third party module translations. And then of course option to maintaining them all separately. Not sure which way I prefer.

Fokke, superb job with translations! Only tthing I was wondering was "perhe" at template edit, since we don't have children and parents. I couldn't come up with anything better though

Not sure I understand your logic. Why each of the churches need to translate all files themselves? Of course sharing and updating translations could be smoother, but it's not clearly as bad as you make it sound. The most important parts are done and well made: easy to translate and create language packs (both core and 3rd party modules). No need for any third party service, but updating translations through modules directory would be nice.

Hmm.. Does it create the page under /processwire/setup, but without process assigned? You can check this from pagetree.

I have some pending updates also, but eagerly waiting for Fokke's pull request What you guys think, should we translate everything? There are more and more places where you cannot tell which are "only for developers" and which are visible for editors too. Like Inputfield module names that are shown in Form Builder etc.

Very nice. Interested in hearing more about what you mean with job queue?

Very fast from Finland also!

Nik is back!

https://processwire.com/talk/topic/5083-possible-bug-page-fieldtype-with-custom-selector-to-find-selectable-pages-returns-error-while-saving-page/?p=50177 Martin, for your selector you are mixing the either-or selecting and the @ selecting, when you probably just want to use the latter. Also I don't really understand the [value=stp] part of it? Your selector "template=address_abo, (@adrdb_multi.adrdb_location.id=[value=stp], @adrdb_multi.anzahl>0)" actually say: Find all pages with template address_abo (so it finds all address_abo pages, no matter what)OR all pages that has adrdb_multi.adrdb_location.id=[value=stp] AND adrdb_multi_anzahl>0 on same adrdb_multi page. What you are probably looking for is something like this: template=address_abo, @adrdb_multi.adrdb_location=[value=stp], @adrdb_multi.anzahl>0

When we have first international pw meetup, I reserve my seat next to Joss.

There is now setting for this in latest dev.

Pwired, instead of http:// the Google fonts should be loaded just with //, then it would use http/https according to the current page. That is of course quick change and pretty much site specific setting. And welcome to the forums vegardw!

I love the site, best one there is and because of the content and high quality commenting that sometimes happen. I haven't been annoyed by the ads, but I kind of like ads anyway (even on tv).

I have figured that out! But it takes 9 months, and what you get is something small (but cute!) that take years and years to evolve into coder.

Reno, to be honest, I have hard time finding time extending this. So if you tackle wildcards etc without complicating the basic usage, feel free to hijack ownership of this module. And now I realize it was Mike doing the promises... Same goes for both of you. Don't count on me

By id, or usually using the object ($modules->get("ProcessHome")).

Sorry for poor communications from my part. New shop module is currently in closed beta testing. I am pretty busy at the moment (both work and personal), so there is not too much focus on this. For the pricing I am thinking something like 50€ - 99€ for single site license. Also currently (slowly) building full featured shop profile, that would be single purchase and free to use parts or fully as many times as wanted (single site license required for all new shops though).