apeisa

That would be great. Also same for YouTube-videos would be great!

jploch: don't be afraid of the current module, it is very easy to implement. If you know how to build product catalog (well, with three products you don't need even that), then it is pretty much plug and play. What payment methods you are looking for?

That $p->snapshot() stuff is supercool! It would be trivial to create "timeback machine" for frontend...

I think that only three last ones are things that are not easily doable just by using some very basic ProcessWire methods (pages, fields etc) and with my Shop module. I myself don't see that much benefit building "out of the box" eCommerce solution. There are multiple solution for that, hosted saas, open source, commercial... What I would be happy to see is more low level "building blocks" that can be used in any PW site to power different kind of eCommerce need. At least that is how I intended when I build the shop module: it should be easy to implement to any PW site.

I use feedbin.me (I love it, much better than google reader was). It actually didn't recognize somas feed at all, but that seems to be a network issue: https://github.com/feedbin/support/issues/413

Try <?php on top of the file.

Modules ain't magic. They are actually very simple (Ie. I haven't build single module/plugin for any other software ever).

Xeto, thanks for your comments. I am not planning to add "middle managers" - ie "group admins", that can manage users inside their group. Though that would be nice addon for this module. Other than that feature - this seems to be pretty much what you need. There is some green light to get circular references working in PW: https://github.com/ryancramerdesign/ProcessWire/pull/258#issuecomment-30052142

check and resave field settings.

it's better now!

looks nice, but is kind of unusable on my android. zooming doesn't work and menu breaks.

when you set the language for guest, it changes it for all visitors that have haven't logged in. I am pretty sure that what arjen and fokke said is what you are looking for.

What I think is most promising is using CKeditor widgets for image positioning, galleries, videos, text-columns, content highlights etc... and then just regular pages and repeaters for everything else (like featured products, carousels etc). Probably the ultimate solution would be something that ties hanna codes with CKeditor widgets. For me using repeaters and field dependencies here feel little hackish - both UI and backend wise.

only by creating multiple fields for cities. like cities_in_france, cities_in_finland etc and show/hide them based on country selection.

You could definitely use PW to build Facebook (feature wise). There is absolutely no reason to worry about being biggest and most active website of all, before you haven't written a line of code for the project. I have build websites for over 15 years (8 of them professionally) and there have been very few scalability issues. But oh boy I have worried. The very same question that epreston asked: does it scale? After these 15 years I am pretty sure it is much harder to build service that will be so popular that actually needs to be scaled - than the actual scaling.

I see that as an edge case. I would prefer serving default lang as a default. Serving all languages as a one might be preferable in some cases, but then why not use some switch there &allLang=1

I think the latter would be preferred method to go (language specified in the request, otherwise default returned).

I like the idea of CKeditor widgets (especially combined with advanced content filters that CKeditor already has): http://ckeditor.com/demo#widgets

I have used a lot of time with this issue. The bigger and more complex sites we build, the more "ad hoc" UA is needed. Defining access on "who can access/edit news" is not relevant when your site has 20 news archives for different groups. Or when you want to create new "workgroup" and choose who can access that. Of course all these can be build custom, but it is lots of work and PW doesn't provide anything as a base for that. I have module baking that solves this very issue. It has basic functionality already made and it for most parts bypass the template based UA totally. This is by intention very simple at this first stage: just view and edit rights and user that belong to groups (one user can belong to many groups). Not sure about the licensing yet, I might release this as a commercial module, but also happy to transform it to a open source project for community (if you guys feel this is promising). Ryan has seen the code and we did hit one core problem: circular reference. My module requires page field that many times references itself. This creates problems in certain situations: actually only when page is saved but no changes is made. It is not ready yet, but the basic functionality should be there. I have build this few times already and always from different angle. I believe this is the most simple one (see the find hook that has been the problem in those previous modules). Anyways, I know at least Teppo and Nik have been interested in this, so here we go: https://github.com/apeisa/UserGroups/

I love the new feature of "Locked" fields. Though currently checkboxes have their value as "1". Should that be "Yes/No" instead? And of course it should be translatable.

Amen.. oh, I mean Arial.

try setting the filename without full path.

Just noticed that if you copypaste youtube url from Chrome (Win7) addressbar into CKeditor, it will be transformed into <a> tag and therefor embedding doesn't work. I don't know how CKeditor does that, since if you copypaste it from another source (like text editor), it will not be transformed into a link. Possible solution could be allowing links also transformed into a embed. What do you think?

It supports multiple content types, meaning that you could choose multiple templates for repeater. That is powerful feature in some cases.

Take the ->eq(0) away, you have single image, not array.