apeisa

do they change if you do one change to some field that is not inside repeater? ie change title on same save than you edit repeater data.

we had this issue after new admin theme. I guess it was css, since hard refresh on browser fixed it.

That is way too advanced for most people, who are used to copy the address from address bar. I was wondering why not use history api to keep address bar on topic or at least update the hashtag (since the site seems to support both already)?

That's good! When I browse the site (with js enabled) and find something interesting - how do I share it?

Very beautiful and functions very well! Also superb implementation for mobile also (I was very surprised when viewed it with desktop after using mobile version). What I see as a drawback is that site has too much content for single page website. Lot's of big sections, that are not linkable.

what about sublimevideo?

pwired: social media shares are carried from round to round. edit: ah, you meant that pw mention. nice!

Haha Similar experience from here: my six year old son recently asked his mom "did you know that dad has a friend called Ryan, who lives in USA?"

Hi scuba and welcome to PW! Can you describe more briefly what kind of functionality you are looking for? As always, there are probably multiple ways of solving that with PW, but we can definitely help you on how to solve the problem. Usually you can't go wrong when using just pages and fields, but there are of course alternatives, like using repeaters or building a custom fieldtype.

Twitter votes for ProcessWire (over 50): https://twitter.com/search?q=i%20just%20voted%20for%20processwire&src=typd&f=realtime Twitter votes for Ametys (4): https://twitter.com/search?q=i%20just%20voted%20for%20ametys&src=typd&f=realtime Just sayin..

Same as adrian. You guys have refreshed cache and hitted "check for new modules"?

This is cool idea and hopefully it will be successful! Does it minimize images right after uploading or when first viewed? If the latter, does it do it on background and serve original image for first viewer - or does it make roundtrip to minimize.pw servers first?

Classic to the win!

It seems I will be having lonely party here

Joss, it's pretty much like that. Also the topic of the discussion is you. On a sidenote, Nik and Teppo are on fire with the module. My job seems to be pressing those green merge buttons on github. I like it this way

no, not at the moment. But having wild cards would be great feature to have.

sessionFingerprint is a great security feature - if your connection works with it enabled, I really suggest keeping it installed.

Ryan, I don't see need for it, at least not because of this module. Solution we have now should work as good as the earlier (I am bit disappointed that I didn't invented that, since it isn't codin magic, but plain old selectors...).

Might be dynamic IP, try setting $config->sessionFingerprint = false; https://github.com/ryancramerdesign/ProcessWire/blob/master/site-default/config.php#L50

Joss, that looks like "the ultimate solution". I think we are aiming for something little bit more simpler, but altogether flexible system. I am thinking whether we should have groups inside a group (sometimes these are a real lifesaver, but they also make things more complex for many)? Also thinking about "group admin", that could create new users into the group(s) they manage (also manage users, if they are admin on each group where user belongs).

Nik figured nice and simple workaround here: https://github.com/apeisa/UserGroups/commit/46161510

nope, still counting on you with that one. Since it fails only on certain situations, I am pretty confident we do find some workaround. Pete, should work already. Look that you have both modules installed. Not sure how it went, but it might be that you need to add the created fields to templates manually... (not at computer right now)

well, it ain't that serious They seem to get nice amount of tweets and links which is probably only thing that matters.

Gotta say that latest iteration looks, feels and works great! Also I love the themes as a modules thing.

PW has very flexible UA management. Most of the sites can get the exact needs fulfilled after little clicking. But when you need to scale it in horizontal way: ie. adding ten different news sections, each with same templates but managed by different group of people, PW doesn't make it too easy (since UA is tied to templates). Also roles&permissions&template access is a combination, that at least we cannot leave to our clients (it's way too complicated for your average editor) - it means that UA management have to be done by us. This is fine on small scale, but some of our sites are pretty heavy on UA: biggest site has over 800 user groups and many times we do have something like 50 000 users importet (these sites are not build on pw today, but hopefully they will be). So we need to have simpler UA that our clients understands and can use on daily basis. That will also mean less granular control, but easier to manage. Lucky for us, PW has hook system in place, that is flexible enough to allow hooking to UA also. Few months ago I started building module to add two features for PW: -user groups (user can belong to more than one group) -page based permissions based on groups (so you can say: this page and it's children can be edited by groups A + B and viewed by groups A + B + C I first thought that I should release this as a paid module, but after showing this current early version to Nik and Teppo (I knew they had similar needs) and when they showed interest in development I wanted to make this a community project (this is gonna be thousand times better than just me building it alone). So lot's of progress is coming and of course everyone is invited to collaborate. Be it ideas, comments, testing, use cases etc.