apeisa

Soma: glad you got it working. I'm in process to integrate this design by Almonk with my clean admin. I really liked how those wire tabs ("Content, Settings etc..") are out of the content container. Well.. that part seems to be hardest to implement in current markup. In admin template there is just <?php echo $content?> which outputs everything under breadcrumb and title. Is there any easy way to add container for InputfieldWrappers, without having ul#PageEditTabs inside that? Now there isn't any kind of container, so I ended up messing with .InputfieldWrapper and that caused problems on more complex pages where there are nested wrappers etc.. Of course I could add container myself by JS, but I think few extra divs wouldn't hurt in giving admin more design possibilities.

Few minor additions to AdminBarNew (I will soon switch that as a master and leave 2.0 adminbar as a legacy branch): Only show add page button when adding pages is allowed (thanks Soma!) Show lock icon with description text when editing is not allowed or page is locked - instead of hiding the bar totally Added js files to bottom instead of head - will work even if you load your jQuery at bottom (and you might wanna do that for performance reasons)

In few days we have 3500 posts, so pretty amazing activity growth here. Thanks for all new and old members!

landitus: welcome to the forums. I had similar problem earlier and Ryan provided quick tip to fix that problem: http://processwire.com/talk/index.php/topic,159.msg1003.html#msg1003

That page is for developers only (or at least that is how I see it, no "regular editor" should have access there) so I have no problems with the current design: Ctrl + F is all you need. In this particular case that someone creates site and forgets password right away.. well, it is pretty simple to create new password through API.

Actually I think github issues list is pretty perfect changelog (that is where I found those changes) - Ryan has very good and detailed commit messages. Maybe if you could add some prefixes it would be more quick to browse: "Feature: added possibility to add template image" "Bug fix: no more errors when editing templates." "Major: users are now pages" And probably should be like if there are any changes in commit that can break things, it should be in own branch and major version lift: 2.3, 2.4 etc...

Good catch again! Removing the line 180 should fix this: (EDIT: from file InputfieldFile.js) remove: xhr.setRequestHeader("Content-Type", "multipart/form-data"); Not sure if we should set something else as Content-Type header, but just by removing that everything works fine on my localhost (win7). I had the same warning in my apache error.log, but now nothing.

Iain: I moved this to general support. Can you post the exact code snippet you are trying to add? It would help others to test what is happening.

InputfieldFile.js on line 216 replace this event listener: filesUpload.addEventListener("change", function () { traverseFiles(this.files); }, false); with this: filesUpload.addEventListener("change", function (evt) { traverseFiles(this.files); evt.preventDefault(); evt.stopPropagation(); this.value = ''; }, false); Should be safe fix, but it would be great if you guys can test and report that it works for you too and doesn't break anything.

Thanks guys, I'll take a look at it. I replicated it too and it is a quick fix.

That is strange and shouldn't happen. Is it both - Chrome and FF?

Great news. I think there are many small improvements also, like changes in admin from folding ui to tabbed layout (much cleaner), better admin search, lock icons in pagelist and gear icons in modules list, using latest jQuery in admin, new clone() function, better template caching... not sure if each of these are worth mentioning, but shows all the nice details that have been baked into P21.

IE10 will support File API. I have said it before (not sure where I read it), but at least now it is official (from IEBlog): Lot's of great stuff. Now it feels great to be a web developer, good times ahead

Hmm. That is strange. Probably not spam bots and more likely something like these: https://www.mturk.com/mturk/welcome Paid black hat seo.

Not sure yet. After playing a while with Aloha the floating bar starts to annoy a little. The more I use the more I wish it wouldn't float. It's true that you can lock the aloha position, but you would do that always depending on the placement. "Always on top" feels more solid and it is what we (and our clients) have used to. Word doesn't have anything floating around. This is just a gut feeling, but Mercury also feels like better coded, and better documented (not much, but there is nice annotated source: http://jejacks0n.github.com/mercury/annotated_source/mercury.html) it has cleaner licencing and uses only jQuery (where aloha uses jQuery & ExtJS). So far it feels like Mercury would be better, but it is more just a feeling than anything. I really need to dive deeper to know which one suits better.

Yes, sounds very straightforward. Thanks for your help here. Will implement this in month or two, before Christmas anyway.

Ryan, this is great! Thanks for your reply and the commit. Hopely Seba will register into forums soon enough. If not, then I will post his code here and take all the respect from his work

It does work. Not the whole page is editable, only left sidebar and bottom at the middle column. Editable areas have blue outlines.

Looks great! Does it (or will it) support API usage also? Like creating links like "download this press release as pdf" in templates? I will take a closer look right after I got time.

My co-worker is getting hands dirty with pw module development. He is planning to create Ajax-inputfield first. I don't remember if search can return json yet? If not, do you think that is big change to make?

I haven't tried it yet. What I was thinking that might cause problems is that http / https -setting. But sounds like a good solution just to ignore that and use own script to determine what domain to use. Currently we use https:// every time user is logged in (or in a login page). I will let you know how it goes. We are not yet sure what to use as a domain name here. Are you ok with domain name like pwire.fi? We don't want to use our company name there, since there would be two organisations in url, like https://clientname-fi.avoine.fi

Actually those members aren't on members list at all: http://processwire.com/talk/index.php?action=mlist;sort=registered;start=0;desc (only on that infobox on front site). Probably caught in some kind of filter or something?

Yep, there was one spam bot, which I banned. Will look into users issue. Has something like this happened before Ryan?

We host all our customers sites, and in our current cms we use different domain for https:// access. That is because that way we don't have to order and manage certificates for each of our sites. If the site is http://www.example.com then our secure address for that site would be https://example-com.cms.fi. This has worked great on our old cms (only "negative" thing is that sometimes those *.cms.fi addresses get copied, but they always work of course). Now I am thinking of doing similar thing with pw. How should I approach this? Any clues or has anyone done anything similar?

Well, this is interesting: http://jejacks0n.github.com/mercury/