apeisa

Are you running 2.1 but not the latest commit? addUser() was added to 2.1 about week ago: http://processwire.com/talk/index.php/topic,509.0.html

Yep - the more I think of it, the more likely I will build this with just templates & pages. Our upcoming default site profile will at least have image carousels and taxonomy managed under /tools/ tab, so it would be just wise to use that same natural "pw-way" here with polls too. I am waiting for a perfect moment to dive into fieldtypes, since those are still little bit mysterious for me. But it seems that this is not that moment ,)

Not need actually, Soma got the similar effect working in his Teflon theme by using that form element. Clever Not sure if I finish this work, since there are so many great themes around currently. Positive problem though

Finally got time to install and test this. Really nice theme Soma! Nice looking and has some cool new ideas also. Only few minor issues: Dropdowns are great but too slow: I like that they slideUp slowly, but showing them should be instant or at least super fast Contrast is pretty weak in dropdowns and also in breadcrumb and profile / logout links

Yep, I had the same problem and it starts from here: http://processwire.com/talk/index.php/topic,33.msg2820.html#msg2820 In my case it was different .htaccess file that caused problems. It seems that you have had little fight with .htaccess, but it might be that there is still some problems...

With this I completely agree.

I think they got added in the order that which uploads fastest. All files start at the same time (there is some max limit there though, probably browser sets it). So adding this kind of functionality would mean that we would need to upload those one by one (first file needs to be uploaded before we can start sending second etc...), which would make the whole thing slower. Considering ups and downs, I don't see enough reasons in trying to get uploads ordering by name. Better option might be simple module that would require click and it would sort files automatically and save the page (or just the files field). Same goes to description issue. I think it is minor issue and amount of work for it pretty high. Not saying that I wouldn't like those features, but I consider them as pretty expensive "I wouldn't mind to have" features. I see this one blurring the lines of what requires clicking the save button and what doesn't (and to be honest, ajax uploads does too - could be good idea to have notification about that?)

Good that you got it working, but there might be better methods than hacking the core file. Ryan, is it possible to overwrite core modules by using /site/modules/ folder? I think that could be nice & clean solution in those situations, where simple core hack would help.

Thanks for the example Adam. The UI is the most important thing here: It needs to be simple and easy solution. I don't want those values be editable (or at least behind setting) and it should be error free: no way to input it wrong. In templates usage should be something like this: <?php foreach($p->poll as $poll) { echo "{$poll->question} voted {$poll->value} times"; } The biggest reason why I don't like using pages & templates here is that it would be cumbersome to manage. You would need to have /polls/ page where you add all your polls. Then you would need to have page field where you choose what polls you want to show on page you are editing. I like it more straightforward: you just add "poll" field to templates where you allow polls and you can use this field to create polls on the fly. But now that I wrote that down I realize few mistakes in my thinking. There wouldn't be poll archive. Also polls created this way would need checkbox (active/unactive)... plus it would allow only one poll per page. Also that wouldn't allow things like "show latest poll" etc. So I might go back to what Ryan originally suggested (using pages and templates). That means though that I don't get my hands dirty with fieldtypes yet...

Why do you want to have those zeros? Do you need same datefield to support "a year" and "a specific date"?

I will build the full scale "poll" module soon, and started again thinking about building that ValueKey fieldtype / inputfield. Although I think that it could be named simply as FieldtypeList. Idea is to have repeatable text fields, that can have additional value also. UI could be very similar to what Almonk posted earlier: http://cl.ly/2Z2O2c31230X36173j3v What would be best (=simplest) way to build this? I am thinking between FieldtypeMulti or regular Fieldtype and saving values & keys as JSON and the latter feels like simpler solution here - although not sure how well it scales when I need to add things like sorting etc.

From mobile, but this could work: $cover->add("url_to_image") Edit: forget me, seems you are using add already.

Just updated branches that master is now for 2.1 and AB20 is for 2.0. AdminBarNew is no longer. So if you cloned this from github, you probably want to do something like this: git checkout master git pull origin master (or just remove whole folder and clone it again) If you have downloaded and unzipped, then just download again, but now from master branch.

Damn you Alistair This is even better looking theme than the one before (that I am porting to clean admin). And not just the looks, I really like how this one feels to use! EDIT: I think that pw admin would really benefit from simple dropdown navigation. One click access from anywhere to templates, fields, users, permissions and roles. Setup and access pages are really just container pages without any content or function, so easy way to skip those would mean faster site building and maintaining.

Awesome stuff Ryan. You are treating us too well!

It would be very nice to know how often our clients save their pages. I think that it is pretty rare operation on many sites (not even every day), and some sites edit/add content few times in hour. I think that many times even on actively edited sites the "wipe whole cache" could be very good solution (knowing the fact that wiping the whole cache is "cheap" operation - and doing this only on templates that gets pulled through API - usually something like news, events etc). Don't know how much overhead it gives to then always write cache files over and over again on big sites (over thousand pages)? Or is it always cheaper way than letting pw to query db? (of course this depends also how popular the site is - if pages get very few views then we can forget whole caching )

Had to check this before going to sleep. Issue seems to be pretty simple and in css. These are in default template, main.css: body.modal #masthead { display: none; } ... body.modal #footer { display: none; } ... body.modal #bgtitle { display: none; } At least bootstrap theme keeps .modal in body tag, so it should resolve with simply adding those lines into css.

Same issue when using adminbar - for some (probably very simple) reason these themes don't respect the &modal=1 get variable. Now heading to bed so will check into this later.

Now I actually can reproduce (I had slightly modified clean admin myself - there wasn't this issue) - I downloaded Almonks superb Bootstrap theme and it did have this (so probably current public rev. of clean admin have it also).

Soma, I can't reproduce this issue, might be some other module causing problems? Try to disable AdminBar and other autoload modules.

Thanks Pete for your kind words and virtual beer Can't take all the credit, since Ryan committed whole lot coding and great additions for this. I have had few opportunities to demo this and it is so cool feature to show (especially when using on live server and not in localhost - when you can actually see those progress bars ).

Good to know, thanks Soma. For everyone else who might download the AdminBarNew: if you want others than superuser to see AdminBar, then you need to a) uninstall + install Adminbar or b) add new permission "adminbar" and give it those roles that you want to see adminbar. Installing adminbar does add that role automatically for you. There is one annoying issue left in IE: it throws "Load jQuery first" alert when you have tinyMCE fields in your template and you close the edit view (using slide/modal). Working on this...

The most epic thread award for you Pete! Back to topic: it is always relief to understand why something happened - no matter how silly the reason is.

Only commented line is this in Page.php: /** REMOVED public function roles() {} public function addRole($role) {} public function addsRole($role) {} public function hasRole($role) {} public function removeRole($role) {} public function removesRole($role) {} */ My co-worker was testing the API and $user->addRole($role) didn't work and that was what he found - so it cannot be working since the whole function is missing. This is what docs currently have: $u = new User(); $u->name = "gonzo"; $u->pass = "BamBam!"; $u->addRole("guest"); $u->save(); So this fails also at the moment (not tested though). Also removeRole shortcut that docs mention is missing. These aren't critical issues (all the functionality is there, but docs and code is not in sync at the moment) . We were quickly testing this in bootstrapped API so that is why our output was ID. Using page field it is easy and trivial to set label to be name field. I agree that probably no reason to add title on role and user templates by default.

Ryan, thanks for your answer and fix. That all makes sense. Those $users, $permissions and $roles were exactly what we were playing with. My co-worker has some kind of magical php-shell where he bootstraps pw and these issues came there (also addRoles() stuff I posted, but that was probably just misunderstanding from our behalf (probably thinking in 2.0 way...), will check it again tomorrow). I will post about that shell more too soon, it is very interesting stuff.