apeisa

Never seen anything like that. Have you tried reinstalling? Also transfer files again (or better, unarchive on server) before installing.

Steve have build some excellent modules for admin security: http://modules.processwire.com/modules/auth2-factor-ppp/ and http://modules.processwire.com/modules/session-login-alarm/

It is actually pretty simple. History API and recent browsers - nice thing is that fallback is very clean (normal links and url).

Nice work! I really like the deluca.ca site. I will definitely try the Spex on my next project. There seems to be more and more high quality agencies finding PW and using as their preferred CMS. I think we should have official or unofficial listing of all agencies and/or freelancer somewhere!?

I love those photos. And while they are big and sharp - they load very quickly! Nice work!

No need to be sorry. That is often made mistake (that still confuses me after 3 years). In my opinion it is bad design decision - probably only one there is in PW Simple and harmless setting that can break your site. Not something I wish changed now, but I think it would be cleaner to always return array. Or maybe $page->images->url return url of the first image even if an array?

Yeah, I think Sir Trevor is closest what I have seen from open source world as a RTE re-imagined. Looks very promising at least!

I guess PW removes it if it can. If the file exists, PW will throw a warning each time you log in (as a superuser at least).

Hmm.. not sure where it comes. Probably getThumb inits inputfieldImage which then populates that fancyscript. I took a quick look and couldn't figure out where it comes actually. As a quick fix you could remove that script before looping your scripts (not a clean solution in a long run, I agree). Anyone else has a clue how to prevent fancymodal here?

I suggest trying from foundation profile. it is very quick to change layout. Also it teaches you some more advanced usage of pw site building. Default is the most simple starting point though, so if you are new in web development in general, then it is best way to go.

I assume you have page field called "subjects" on your student template. Then the selector would be this: $studentsStudyingThisSubject = $pages->find("template=student, subjects=$page"); Above code works if you have that code in your subject_template. Then the $page object will have the subject you are looking for. Hope this helps.

Beluga: yes, that is what I tried to say (my argumentation was little weak). SASS is strong player already and has clear benefits. Also not showstopper for anyone who doesn't use or know it.

Datetime inputfield's time widget seems to be broken on latest admin theme dev? I am only able to select 00 or 23 for hour and 00 or 59 for minute.

I feel the same way. Many times these features are "required features from cms" when organisations are buying a new site. Then afterwards many of them actually never use these features. It's also countless time I have build many kinds of content aggregators, where "we really need to filter/sensor/schedule content". I say them that I believe you never use these features, are you sure you want to buy custom development here. They always want and after a year when I check the site they have never used these features. I guess it is mostly for "feeling for control". Also these things create a fabulous demo. What comes to other way around: retrieving history, restoring removed pages etc. These are rarely used things too, but they actually make updating feel more secure and when build well - they lighten the support burden.

I understand that there is lots of discussion about admin themes currently - since the default is getting lots of improvements. As always when things change it will get mixed reactions: some people doesn't want any change at all, others are very happy and some are thinking that much more should be changed. What Felix is saying is pretty much total revamp of how ProcessWire admin theme is build regarding it's front end development. That kind of change is huge amount of work - and not something that most PW users are excepting. Soma is already feeling pain since one core css class name has changed Also admin theme revamp is not on roadmap: http://processwire.com/about/roadmap/ and that is the place where we look on "what's coming next". That is also risky business in the regard, that front end is moving so fast currently. I agree with slkwrm, that many of the buzzwords floating around currently might not be around in next 2-5 years. So committing for something like SASS should be proven to last (there is lots of users, software, tutorials etc to support it). I don't think I have had any serious problems with html,css or javascript clashes when building PW modules - and I have build quite a many already. So in my opinion there is no real need for total revamp at all. At least not yet. The reasons why I really enjoy this discussion and think this is very important: it helps everyone to see what could be possible and what it would require to things like that. I also feel that I am learning a lot just by following the discussion. This discussion also helps to get better picture for coming years - especially when we start actually feeling more pain points in current architecture regarding admin theme. PW api and architecture is so modular. that there is nothing - and I really mean nothing - that would prevent building totally custom admin theme that shows off these techniques. I would be thrilled to see something like that. Revamping the current default admin would mean tons of work for most of us (who have lots of sites and/or modules to maintain) without really taking PW forward to direction that really helps us (see the roadmap). I hope that discussion continues in same tone and also would be superb to see some working drafts how those would function. People are rarely excited to learn new ahnd change their current tools. methologies or techonogies on their core business (it is just too time consuming and risky), but when benefits are great enough and shown in action - people will take a leap in quite a speed.

This is good discussion in my opinion. I agree with both, Felix and slkwrm. It is very important to keep things up to date and use best practices. As Ryan has many times stated, he is more "in home" with PHP than front end stack. But in the other hand using too many "cutting edge" methods/libraries/etc is dangerous too: it always makes steeper curve to learn and start using. Anyways: I am really enjoying this discussion and the constructive tone that Felix is leading here!

our staff has been very excited about new theme too. I think great improvements all around.

How about now guys? In my tests this works great now on FF, Chrome (older ones too), Safari and IE9+. Tom: I believe that your JS-issue is also fixed by this update. Also implemented the overflow: hidden, thanks for that - it works great. Marty: Should work, but those image positions and repeater stuff still missing from AjaxSave method in PW core. I will start looking for that next (probably something that is relatively easy to support, but not sure yet and needs to be committed into core too).

Oh, sorry Marty. Didn't take a look at that one yet. It is somethig that needs to be supported by AjaxSave method in PW core. And thanks for testing!

the way modal closes is bit experimental. it does Ajax request to its own URL and then replaces body content. so all elements will be fresh ones. that us probably problem with js freeze. can you provide an URL for me to test that js case? thanks for testing tom!

Ok, I think I nailed both of those bugs. In my tests this new ajaxified Fredi (available from dev branch) works great on FF, Chrome and Safari. Should work on IE10 too, but will test other IE:s later.

Here is very well articulated article about this very same issue. Recommended reading for everyone: http://www.markboulton.co.uk/journal/wysiwtfftwomg (WYSIWTFFTWOMG! - Mark Boulton).

Oh, I am not sure which is best. But I think that in Ryan's theme the breadcrumb is styled and positioned in a way that it is very clear and visible. Also one thing to remember is that title is first editable field on page, so therefore also on very visible spot.

I agree mostly. But "edit page" page is also very intentional. What I mean is that you have clicked "edit" in certain place before getting into that page. So you should have very strong sense about where you are. You don't get to that page from search engine for example.

That theme looks absolutely fantastic Adam! I love the traffic lights idea! Reaction and activity to take PW admin to next level tells something about how keen people are for PW. Can't wait to start testing this one Adam.