Leaderboard

I have been waiting this day too long, custom tailored avatar from WillyC! And then he makes two... but wait. That second one is real and something my wife posted on Facebook just few days ago..?

i.find more newer fotos.for u avator

I might have something baking regarding user groups and simplified access management.

Hello there, In my long slow way of discovering coding, I ended up realizing I needed something like... the Pages Web Service. I installed it, tried it and thought.... Woa! How can Ryan do so much... It seems perfect for my needs right now! I was stcuk and now I can go forward again. So I'll keep on exploring and trying to do my stuff. But on my way, I wanted to stop and say THANKS to Ryan for his work and the way he's sharing it... I sometimes ask for help, this time, no answer needed ;-)

nice to hear. Mine will be pretty simple: introduces groups, you can tie members directly into groups or tie role into group (and all users with tied role will belong to group). Then page based access for groups viewing and/or editing page branches.

Let's just wait that WillyC makes one for you ok pwired here avoter for u i make beter one later

Drupal is still a quicker path to a community-generated content site. It can all be built in ProcessWire, but Drupal is well suited to this from the get-go. It's not just user relationships, but the fact that it's a markup generating system… not much separates the editing side from the presentation side (this is also a point of frustration for some). Most other things I would say ProcessWire is better suited for (yes I'm a little biased). But it ultimately comes down to what system a webdev has the most expertise in, and Drupal is one of those that you can accomplish quite a lot in when you know it well. That's if you are willing to accept other aspects of the system–it's a fundamentally different approach [from ProcessWire] that works well for some and not others. Mary–I've always liked the fact that you know so many systems well, and stay up-to-speed with them. You've got a very good perspective about the CMS landscape. I'm glad ProcessWire is one of the systems you like working with. Btw, when you are trying to solve a particular user/role/permission scenario, please post it and we can help to figure it out. It's all possible in ProcessWire, but some more complex scenarios are solved programmatically with hooks (but it's a lot easier than it sounds).

A responsive and minimalist photographer portfolio. http://mikael.siirila.net/ (and if you like the photos, follow me at http://www.facebook.com/mikaelsiirila/) -- Mikael

Dresscode?

I think our modules will be friends <3

Making a multilingual site with an extranet, very snappy with Processwire. http://www.goer.fi/ design by Nordenswan & Siirilä http://www.nordenswansiirila.fi/ -- Mikael

Aah. Sounds nice. Mine doesn't really do the access management per se, at least not in that sense. It just simplifies the task of creating users, assigning roles, etc and sort of provides a directory of users in one nice interface, that can be applied to different scenarios.

Well.. My photo was about 10 years old already, so changed to more recent one. I try to grow beard too, but for some reason my beard has been pretty same since teenage... promising start, but nothing to be proud at this age.

Font Awesome Page Label (almost stable version) Yet another PageListLabel module, why? Font Awesome is really awesome, hundreds of high quality icons, ready to use. (Don't we all know how cool icon fonts are.) I wished to use icons in conjunction with the other PageList modules out there. (Page List Better Labels, Page List Image Label & Page List Show Page Id ) I wanted the possibility to style the icons individually with CSS. Showing icons triggered bij template name, but can be overruled bij Page ID. (Trash Page, 404 Page not found etc.) I wanted a better file or folder indication in the PageList tree. Download: github modules directory

Or a normal hair

i just did what u said, i dropped the module, now from admin panel i just enter the url for youtube movie and then i do this : <?php $videoFolder = $pages->find('parent=1051, limit=3'); $out =""; foreach($videoFolder as $videoItem){ $vidUrl = $videoItem->video; parse_str( parse_url( $vidUrl, PHP_URL_QUERY ), $my_array_of_vars ); $imgUrl = $my_array_of_vars['v']; $search = '/youtube\.com\/watch\?v=([a-zA-Z0-9]+)/smi'; $replace = "youtube.com/embed/$1?autoplay=1"; $vidUrl = preg_replace($search,$replace,$vidUrl); $out .= "<div>"; $out .= "<a class='fancybox' data-fancybox-type='iframe' href='{$vidUrl}'><img src='http://img.youtube.com/vi/{$imgUrl}/0.jpg' alt='{$videoItem->title}' /></a>"; $out .= "<div class='name'><a href='{$vidUrl}'>{$fotoItem->title}</a></div>"; $out .= "</div> "; } echo $out; ?> And thats it i got my video working Ty alot Adrian u ware most helpful

Actually, the simple extranet was a last minute request by the client. Before jumping ship to Processwire I might have said no but with Processwire I could just tie Processwire user accounts to a template which has the exact same layout as the site. I could add an extranet with just an hour of extra work. Now the choir members can login and download notes, mp3's and check programs. Simple but effective.

I agree with Matthew about reusing code from different projects. I think user/membership models could be a really interesting module for PW as it comes up quite a lot and I know for a fact it's possible in Processwire, perhaps a good one for this community funding idea?

Greetings, Ryan, that is very generous of you! Your attitude is one of the many reasons ProcessWire's reputation is growing. Even though this is your system, you offer honest answers that are the best for devs and not just markting hype. OK, with that said... I have been doing more with user roles in ProcessWire and ProcessWire is definitely capable of doing anything we want. I have used Drupal and Joomla, and even though both of those systems may have "community" elements built in, the struggle to theme and override all of their design and function assumptions is far more time consuming than setting up user roles in ProcessWire. Also, after you do a few user roles in ProcessWire, you get the system and future ones are easier. * My opinion is, take the couple of extra steps to set up your user system in ProcessWire. It may take a bit more time up front, but will be better longer term. Post on the forum for specific cases and people will share the code. Thanks, Matthew * Another example of the ProcessWire "framework" concept. User roles in ProcessWire are more like doing roles in a framework than in most CMSs. This probably deserves its own separate discussion (http://processwire.com/talk/topic/2676-configuring-template-path/#entry43228).

Are you sure about that? I think it is very rare for any js to actually be required in head (and css definitely not required). So I would probably inject that JS just in processPayment() method of your module. Something like this: $out = "<script>alert("hello there, this js need to be before the actual payment form")</script>"; $out .= "<form name='processOrSomething'>...</form>";

Usually this is a good and simple method: In a autoload module you hook into the processInput of InputfieldTextarea. public function init(){ $this->addHookAfter("InputfieldTextarea::processInput", $this, "validateText"); } public function validateText($event){ $field = $event->object; if($field->name == "body"){ $page = $this->modules->ProcessPageEdit->getPage(); $oldValue = $page->get("$field->name"); $newValue = $field->value; echo "old value: " . $oldValue; echo "new value: " . $newValue; if($newValue !== $oldValue){ $field->value = $oldValue; $field->error("Go away!"); } } } For a error message you simply add error("text") to the field. It will get showed after saving. What this examples also shows nicely is how to get the old value and new value. The code may slightly varies for different type of fields but the principle is always the same. There's also a method to hook into Pages::saveReady() but I'm not sure what the advanced really are atm.

hmm, no one replied to the question there... so I post it here. Some possible translation updates: /wire/templates-admin/default.php (for complete main menu and heading translations) /* * Dynamic phrases that we want to be automatically translated * * These are in a comment so that they register with the parser, in place of the dynamic __() function calls with page titles. * * __("Pages"); * __("Setup"); * __("Modules"); * __("Access"); * __("Admin"); * __("Languages"); // add * __("Users"); // add * __("Roles"); // add * __("Permissions"); // add * */ /wire/modules/LanguageSupport/ProcessLanguage.module (translatable 'Edit' and 'Translate new File' link) $lastMod = date($this->config->dateFormat, filemtime($pagefile->filename)); $edit = __('Edit', __FILE__); // add $out = "<div class='InputfieldFileLanguageInfo'>" . "<ul class='actions'>" . "<li><a href='{$translationUrl}edit/?language_id={$page->id}&textdomain=$textdomain'>$edit</a></li>" . // change "</ul>" . "<p><span class='InputfieldFileLanguageFilename'>/$file —</span> <span class='notes'>$message</span></p>" . "</div>"; $translationUrl = $this->translationUrl(); $page = $event->arguments[0]->get('page'); $translate = __('Translate New File', __FILE__); // add $out = "<ul class='actions LanguageFilesActions'>" . "<li><a href='{$translationUrl}add/?language_id={$page->id}'>$translate</a></li>" . // change "</ul>";

I never had this problem myself, but HTML5 Mobile Boilerplates .htaccess has some rules for this: # Prevent some of the mobile network providers from modifying the content of # your site: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.5. <IfModule mod_headers.c> Header set Cache-Control "no-transform" </IfModule> # Prevent mobile transcoding <FilesMatch "\.(php|cgi|pl)$"> <IfModule mod_headers.c> Header append Cache-Control "no-transform" Header append Vary "User-Agent, Accept" </IfModule> </FilesMatch>

Your're looking at the page tree of ProcessWire. It represents the structure you also see on the page itself. As you mentioned, the first Page (/) with the house icon is the start site. You can't delete this page, because everything within PW is a child of this (even the admin pages itself). In the default installation, this page has the template "home". You could change this but you don't have to (and also it will cause trouble with permissions...). In the PW admin, go to Setup->Templates to change the fields of the home template. Open Setup->Fields to edit or add new fields you want to use in the home template. We can find the template file for home under the template directory in the PW installation path: /site/templates/home.php . Open it and you will see the markup for the start page. As in the tutorials, you can change everything here and build your own customized start page. Basically, you just overwrite the default home template with your own fields and templatefile. You could try to just download the blank profile and instead of installing a fresh PW, just replace the content of the site/templates folder. After that, you can delete all example pages from the admin and customize the home template.

I've been working with Drupal since v5 all the way to the current version. I find it quite a powerful beast, and I can honestly say I enjoy working with it for the most part. My biggest pet peeve with Drupal is how complex the themeing is, and what a tangled mess it spits out. This is supposed to change with Drupal 8, so time will tell. The other thing is that for how flexible it can be, it can conversely be very inflexible, and the more complexity you need the more modules you have to use. The more I learn Processwire the more I believe that you can accomplish pretty much anything with it without getting too much complexity involved. Since I'm still learning PW I still find myself reaching for Drupal particularly for projects that need complex user relationships and roles and permission settings. Drupal excels at this. I am sure Processwire does too, but I'm not there yet. I guess the other thing I love about Drupal is it has inbuilt multiblog and forum, so it's the logical choice for me for certain projects where a client wants these things and has a limited budget. Because I know Drupal well I can hammer out a Drupal project with these things quickly (as long as someone else does the themeing... LOL)

PW Images Manager (beta) Just a weird little screencast trying to show how it works. (out of date a little, tags now use a textfield for easy copy/paste) This module allows you to manage images from one central repository. You create a root page "/images/" where you can then add categories and images as pages. From there the new admin page created "ImagesManager" will show categories and images added in a ajax data table, from where you can see and search/filter all images, upload and create new categories and edit images too. Every image will also show an image tag generated to copy into a textarea. This tag looks like this: {image=/path/to/image/imagename/, width=200}The width=100 is the thumbnail size used to output the image.You can also have additional segment to contain classes: {image=/path/to/image/imagename/, width=100, class=align_left}Or you can enter the id directly: {image=1033, width=100}Once inserted into a textarea field it will get parsed when saved and loaded automaticly. It will store an abstract id tag in Database and convert it back to the image HTML tag. So after first save you'll see the image inserted in a Wysiwyg and be able to resize and place it as usual. Once it's inserted somewhere Images Manager will show a search link with the pages containing the image (you can configure the fields int the module setting). You can change the image or move it to a different category, it will still work and show the correct image. This also works with multi-language fields.You can still also use the regular insert image dialog in TinyMCE and chose image from those pages. And it will start keeping track of those as well (they're the same after all). You can use those central images pages also with page fields to reference them single or even whole categories, search them with API and do what you like. Images Manager will also parse the page render on front-end and replace any found image tags with the HTML code. It will also look for a description on the image and output it as alt tag. If you want to have multi-language description you can add a `image_description` TextLanguage field to the image page template and have images parser use them. Along with this module, you can also install the `PageListImageLabel` module to add thumbnails to the image pages in the tree. To get it working you need to have the basic setup: 1. Create new `image` field with input setting to 1 max image 2. Create new `image` template and add `title` and the `image` field created before 3. Create a 'image-category' template with only title and allow the `image` template and `image-category` as child pages under family settings. 4. Create a `image-root` template with only the title field for the root of the images tree. Allow only `image-category` as child page under family settings. 5. Create the root page with the `image-root` under the home page as "/images/" 6. Done. The structure of the image repository looks like this /images/ /cagetory1/ /imagesxy/ /category2/ /image2/ /image3/ Now you can use the ImagesManager to add categories and images. But you can also still use the page tree to add new stuff as usual. The root path, template names and fields are configurable in the module settings. How to install the module: - Download the contents of this repository and put the folder renamed as "ImagesManager" into your site/modules/ folder - Login in to ProcessWire and got to Modules page and click "Check for new modules". You should see a note that the two new module were found. Install the "ImagesManager" module. - A new admin page "ImagesManager" should appear in the top menu. - You may configure the option on the module screen to suit your needs. Download at github https://github.com/somatonic/ImagesManager Thanks and enjoy.

The Organization of American Historians just converted its website to Processwire: http://www.oah.org/ Founded in 1907 and with its headquarters located in Bloomington, Indiana, the OAH is the largest professional society dedicated to the teaching and study of American history. — Michael Regoli, OAH

Get yourself a free account at SendGrid and use some of their PHP code

And if already in a template: Write the ID of the field on paper / txt and remove it from: fieldgroups_field

Looking forward to this!

Add an umbrella to it and you have your avatar dress code Something like John Steed.

@pwired: Oh, man.. your hair looks nice...... NOT...

Really should have tested with more dimensions, removeVariations() did the trick. Good to know for future use, thank you very much

Glad you got it working. The $videoItem->video makes me think you are storing the URL for the video in a dedicated field? If that's the case, you shouldn't need to do that preg_replace. You already have the id from $my_array_of_vars['v'] so you should be able to just build the embed version directly from that.

Hi vxda, Assume you are using youtube: http://stackoverflow.com/questions/2068344/how-to-get-thumbnail-of-youtube-video-link-using-youtube-api And here is some code for both youtube and vimeo: http://darcyclarke.me/development/get-image-for-youtube-or-vimeo-videos-from-url/

That's make two of us then...though mine is a fun project, a learning platform... I'm sure yours will be much better

Then it's even more impressive. Thought I had read all the topics & posts

vxda glad you figured it out. It's always good to check if there's images, you could also use count(), and maybe also not output the image if there's no image. So you could also do ... $out .= "<li><div><a href='{$newsitem->url}'>"; if ($newsitem->images->count()) { $out .= "<img src='{$newsitem->images->first->size(313,177)->url}'/>"; } $out .= "{$newsitem->title}"; ...

For those working with pagination and several urlSegments. This seems to be pretty bulletproof: $currentUrl = $page->url.$input->urlSegmentsStr."/"; $pagination = $results->renderPager(array('baseUrl' => $currentUrl));

If the module needs JS/CSS in the frontend (e.g. in templates), I don't see any solution other than let the dev add those scripts himself or using the Page::render hook, assuming that the module is autoload. Why? Because the module creator can't know your template structure. There are lots of different approaches, using a head.inc file is just one of them. Adding the scripts/styles to the config arrays will only work if those arrays are used to output the scripts in the templates. This is because Pw does not force you how to generate the markup, it's pure freedom

Thank you all for your replies... Unfortunately i don't have direct access to the server... But i found another solution... i am buying a unix hosting with a decent provider... Why? Because honestly pw is the best cms i ever worked with till now, i am a cms expert ... I am not dropping pw for stupid iis ... Long live Process wire

I personally think that the way that the current ProcessWire admin functions is exactly how it should continue to function, I'm not a fan of the always available page tree (or any kinda of extra clutter really), I've rarely had a client I was confident could understand/effectively utilize such a feature anyway. I get fewer calls about "CMS confusion" with processwire than I ever have before with ANY platform (yes, even WordPress). Though developing a new admin theme that may make itself more conducive to the addition of such major features would be great, if doable?(I'm not master programmer so I have no idea) I really think this simplicity is key in a default shipping product. Also making the default theme clean/minimal would also potentially make small visual changes easier for developers. My concerns about the theme don't come from a function stand point as I think some of the ideas floating around in these forums serve more to solve developer issues than client issues, and in the end our primary concern, particularly for the default theme, needs to be client experience. My concern is that honestly I was one of these superficial types that overlooked PW because the admin wasn't "cool" or "slick" enough for my tastes. There was probably a 3-4 month period between when I first discovered PW and watched the intro video to when I ended up back here out of my continued search for a "custom post type/custom content" CMS. This second time I took a peek around in the forums to realize that PW supported admin themes, I was in. Between Futura Remix and at the time a preview post for Ergo I knew I could be happy with the look of PW. But obviously not perfectly happy as I was still motivated to go on to make a few of my own (one particular motivator was the use of Jquery ui and its awful awful icons). And frankly in general jqueryui is a bit ugly and very dated looking (though I can understand the concern of moving away from it, seeing as how much code would need to be rewritten). The point before being that there is a very real risk of loosing out on new users because of this (just look at the CMS "Craft" which recently got tons of attention in a bunch of webdev blogs and yet has no single feature that processwire doesn't except it has a gorgeous admin interface, AND you have to PAY for almost all the other good features!). I think one thing that happens is people can't so quickly understand how amazing, flexible, straightforward, powerful and generally beneficial the PW API is, but what they can understand immediately, is whether or not the CMS admin panel is cool, clean, slick, simple, sexy.... whatever. And I think PW falls short here, its not terrible, but its nothing exciting. There are certainly plenty of CMS' to draw inspiration from though: Symphony CMS, Kirby admin panel plugin, Craft, Statamic, Anchor CMS... I'm sure there are more. I think the most effective place to put effort for now it a simplified cleaner rewrite that better supports 3rd party admin themes, no more specificity battles (there should be no need for the use of "!important" in the default theme, or at least very little). This combined with the ability to have "Admin Theme settings" and a per user admin theme selection could really fix most of the concerns floating around (at least I think so...). I really think something that takes the colors from the new processwire.com and a bit of inspiration maybe from others could really nail it. Oh and, I really think switching to an icon font would be smart..... and ditching jqueryui.... I'll stop here... phew.

To be honest I use the default theme, not because I dislike the others, but mainly because it's the default. There are two main reasons for this: one is that it represents PW (in a "corporate identity" way), the second is because I trust it will break less then the others with PW updates. As much as I like to try, and to see that there are nice themes being designed for PW, unless one is much better, I will stick with the default. This is one of the reasons I would prefer to see the default theme evolving, than a proliferation of alternative themes, and that's also why I'm happy that Philipp started this (being is ideas used or not). That said, I do agree that the admin should be more appealing to newcomers and easily tweakable to have different appearances by changing colors and typography (business (Nico's colors are a great example), fun, serious, etc). I even think that the default install could offer 4 or five alternatives, besides of those that would be shared by users, I'm talking maybe a small json file that could be imported by the system to change it's appearence (a bit like Philipp's color changes, but maybe more profound). What I'm talking here are not different themes, but variations of the same (default) theme. IMO the possibility to easily make these kind of changes, would allow us to maintain the recognizable PW colors on the default appearance of the default theme. This is for me an important point: the PW corporate feeling should be kept. I also want to remind Reno's small tweaks for the edit page. I think they work great: http://processwire.com/talk/topic/2002-repeating-events-multiple-datestimes-for-datepicker/?p=18862 This post went too long. I'm sure it's a mess...

This design direction is really looking good. It's as good of a replacement for the default admin theme that I've seen, and I think it could be a good direction for us. I agree with Antti, that I liked the reduction of the borders from the latest version. I did kind of prefer the icons in the page list actions, though am thinking it might be good to just have 3 configurable options there: text only, icons+text, or icons only. I think that the screenshots do demonstrate that a sidebar page-list is workable with condensed indents–it actually looks pretty great. But I'm not convinced it's workable on the technical side–I think we'd have to go with frames in order to avoid having to re-render that page-list on every edit. And even then, we run into issues, like when and how to refresh it automatically (like when a title is change for instance). Though I'm sure it's all solvable one way or another, and I think we should give it a chance and see where it takes us. Other elements that I think would be useful would be things that Soma has already done with his Teflon theme. One example I can think of is the drop downs that let you go straight to a template or field. I know the concepts shown here don't get down to that level of granularity yet, so just mentioning things I've liked. I know some people like the current minimal admin theme, and I am one of them (I can't seem to use anything else for more than a few minutes). But the default admin theme has to be one that markets us well, and apparently the current one does not have the broad appeal it needs to have. If there's one thing that comes up more than any other when people are checking out ProcessWire for the first time, it's a general aversion to the admin theme. This has been the case since the beginning. I don't understand it, but I think the current admin theme is the only thing preventing wider adoption of ProcessWire. There's a large segment of users out there that judge a product on how it appears to their subjective design sense, and they don't bother looking further if the admin look doesn't excite them. So what we need is something that draws people in rather than halts them from looking further. That's not to say that the current admin theme is bad (I quite like it myself), but that the current admin theme must be an acquired taste–something probably better as a 3rd party theme option rather than the default one. Diogo and I may keep using the current admin theme, but the time has come where we need a different default theme to increase our user base. There are several other admin themes that already exist that could accomplish this already. But like has been mentioned above (and by others before) there is also a need to optimize and improve some of the framework elements behind it all. So building a new default admin theme is best done with a little bit larger scope of changes than would usually accompany an admin theme. I'm not interested in switching away from jQuery UI, but would support inclusion of another minimal framework to provide more foundation both to grid and typography–the things that jQuery UI doesn't do, and isn't designed to do. I'm not sure what framework would be right, or if homebrewing would be better. Regardless, if we were to start developing a new default admin theme from scratch, I think Philip's design here is a good direction to build from. I don't have the bandwidth to get involved with this anytime particularly soon, but it should maybe be a top priority after release of ProcessWire 2.4.

Repeaters & fieldsets take a lot of space. Most of the time I need fieldsets only for dividing fields and description & label is not needed. For several projects I use a module to remove label and set border and padding to 0 for. Also, the repeater can be way more elegant, if some space is givin back to the admin. (Did not make a module for this) (ps, if someone is interested in the FieldsetSchrink module it's here on github)

I would welcome the possibility of choosing a theme per role or user, like this we could build customized themes only for clients without worrying about a big part of the system (template editing, modules page, etc). From there, even deeper changes could be done.

To justify the optional sidebar: Screens under 1200px will not see the sidebar. It will be hidden by default. I've set the first offset margin to 15px and then increase the margin by 20px each level. On a 1280px Screen with 1/3 sidebar I get around 425px. On a 1920px Screen (24" HD Office) I will have 640px for the sidebar. The "problem" are different lenghts for the text + the edit|view|new buttons. Question: How many sublevels do you usually have? I like that aspect. In the next version of the concept I've stripped down some icons. I'm using them for arrows and the template type of a page. I think, it's the tiniest way to display the "type" of template of a page.If not, my customer just thinks of pages and not of galeries,blog posts, news, products,... The top bar is now white. I've chosen the pink/magenta color for everything that has an action, the blue colorto indicate things. The font size also went done from 18px to 16px and the overall look is now a little bit more compact. The second screenshot demonstrates a 1280px window size. This would be a great start. Especially with the theme switcher for the upcomming versions. We could quick build a custom view for a client. Another thing to the "Admin Kit". Maybe the admin-themes can get some sort of an option page where we can disable things like the sidebar. Not sure about this one...

Earlier today I was thinking of a use/case situation where I might use parenting or page fields to tie together some related pages. The better approach was page fields and really the only reason I was even trying to make it work with parenting is that it would be easier to explain to a client how to set it up. This is a case where a client-oriented admin interface could make it easy to select the related pages and declare the relationship but hide the actual details of how that relationship is expressed in PW. In my pre-PW work I've done a lot of custom admin pages for clients to use. It really pays to keep these very focused on application-specific work flow, terminology, etc. I don't expect clients to accept the level of abstraction necessary to work directly with the PW data. The admin pages provided by core should be a tech tool, guaranteed to be scalable and capable of accessing anything any application might have. Sure, there's room for improvement but what about putting that effort into easing the task of constructing a more focused and mediated admin interface for clients to use. I haven't looked deeply at how the admin pages work now but given the modular way things tend to be done in PW I'd think we could do something to streamline the building of custom admin pages. Sort of an admin construction kit. Let the client deal with "skyscrapers" and "cities" rather than "pages" even though underneath, they are all PW pages. Reuse the basic underlying CRUD while adding application specific prompting and tools to help the user with the more focused task of working on a city, skyscraper, category, etc. Build a custom interface where clients can do their routine tasks easily. if they end up with an odbball situation beyond the scope of what you built for them you can always talk them through using the standard admin interface, and if that becomes a habit you extend their custom interface. Personally, I don't think a single admin interface is ever going to be optimal for both programmer and client. Those are different audiences with different needs. I'd be wary of anything that compromises the ability of the standard admin pages to deal with huge amounts of data etc.

Just found another really interesting lightbox. Magnific Popup is a free responsive jQuery lightbox plugin that is focused on performance and providing best experience for user with any device. It's build for speed and seems highly customizable through css (and not javascript like most).