Joss

You dont need a system page, simply a top-level page that is set to Hidden. I do that with categories, tags, articles and so on. The new system would not create this, the admin would as part of designing the image library - that way it can be moved to wherever in the normal page tree is most useful. The main issue is creating a field type that can then work within the existing structure. I was just thinking about this, and it may be more logical that each image is a single page rather than is grouped together on pages. That simplifies things a little since it can use much of the existing system. We already have the ability to create a page in another part of the tree from the Page Field. So, perhaps what we need is a slightly re-written page field that does not just list the titles of the pages, but can list the thumbnail in each case. In its simplest form each page would have the Thumbnails (crop image) field, limited to 1 image and with various thumbnail sized (set by the admin), a title field, obviously, any other information related to the image (possibly also retrieving meta data). You could set up tags, anything really. That is the easy bit! The new page-field variant, needs to be then a cross between the multi select page field and the image field. You can browse the image library by thumbnail/title in a pop up (probably) and select one to either be stored in a field (path) or a variation that allows you to insert into TinyMCE. You can also "Add new image" which effectively creates a new page, including selecting where in the tree it goes (within the image section).

ER .... I didn't add them. Can you let me know where they are so I can lose them? I try and avoid those where I can. Edit: I have found two - inherited, so I missed them. I will check for others then re-upload. Edit 2: I think it was just the two - I have re-uploaded it. Sorry.

hehe - I would try if first! (And I had help)

THis is now out of date and WILL NOT WORK with recent versions of ProcessWire This is a Bootstrap based admin theme This is a very early release and may not be up to production standards - use at your own risk, or just play around with it. UPDATE New version has lots of improvements (see screenshots) and has been updated to Bootstrap 2.3 And roll back to 2.2.2 - at least the JS. It runs into problems with the version of JQuery, I think. Important - this is developed for the DEV branch of ProcessWire and is not fully compatible with the current stable release. The Bootwire Admin theme uses the most current version of Twitter Bootstrap and should be easy to update as new versions come out. Any changes to Bootstrap are done with overrides and the bootstrap.min.css and bootstrap-responsive.min.css are left untouched. Features The theme has been kept sympathetic to the original PW admin colours and layout. The top menu features drop downs rather than linking to an intermediate page (thanks to Soma and his lovely Teflon theme for the menu). I have tried to make the theme as responsive as possible, but I was foiled on some pages by some Tables and TinyMCE - if you want a responsive edit page, make sure your TinyMCE tool buttons are over a couple of rows rather than one long one. Page list actions have been replaced with Icons so that they take up less space (useful for small viewports) Compatibility This was designed using the PW Development branch and using the Chrome browser. It has been tested on other browsers, but not extensively, so any problems, please yell! Overrides Overrides to Bootstrap are in the bootstrap-overrides.css file. Main,js has several overrides to turn elements Bootstrap compatible. There is also a commented out section which changes the page list icons to a dropdown button - however, this is not working in this version. Installation Unzip the archive and place the template-admin directory in your "/site" directory. Note: since this is not a full release, it is not available through Soma's Module Manager. Thanks Soma, for allowing me to steal bits from Teflon and helping with the menu markup Diogo for Teaching me a bit of JQuery and helping with the page list action button (still to be implemented) Ryan for making it possible to create an admin theme in a couple of days (including working on other stuff) Files Now on GitHub: https://github.com/jsanglier/Bootwire-Admin/ Download Hope you enjoy it - leave nice comments below! Joss Screenshots bootwire-admin-v0.4.1.zip

Dead right! (Psst! Where is the code edit button?) murof eht htiw gnorw gnihtyna ees t'nac I ,yawynA ssoJ

I've been caught out with that - on a shared server where they did not have the php short code thingy switched on, so did not recognise the opening <? Should not be much of a problem in most hosts, but always worth checking, maybe.

How about Mambo? They still have people on their forums telling people they should still use it!

haha I don't actually need the span or the </a> - what I was looking for is whether the word "edit" needed to be expressed in a special way for language translation purposes.

Hi Diogo - I thought you had gone home! All that does is print <i class="icon-edit"></i> (As in you can actually see it) and replace the "Edit", though at least it does not duplicate itself all over the place I have just tried html instead, and that is better, but I need to rescue the original text

Hi there JQuery shaped people! I need to prepend something to an element on the page list, but because of the way it is working, I need to check whether it has already been prepended! So This is what I am starting with: <li class="PageListActionEdit"> <a href="/siteadmin/page/edit/?id=1">Edit</a> </li> And I need to end up with <li class="PageListActionEdit"> <a href="/siteadmin/page/edit/?id=1"><i class="icon-edit"></i>Edit</a> </li> Since this is part of the ajaxified page list, I can't simply do this: $('.PageListActionEdit a').prepend(' <i class="icon-edit"></i> '); Because it will just add another one on every time I click a page. I assume this is probably using either .not() or .has() to make sure a particular version has the Icon, and if so, doesn't prepend it, but I cant get it working! Help! Joss

Nice one pete! Can we put puppies on it?

Okay, that sort of worked. I got all the required mark up in, but it messed up the way the actual page list worked. Everytime you clicked on a child page, it just added more and more buttons till I had a page of them. Oh well.

Thanks Diogo! That worked. I will now try the series of bits I need to get the effect (this may horribly wrong.....) Joss

Hi Wanze Because this is a theme, I cannot hack anything but need to override instead. Basically I need to wrap the page list actions in some html and css to make it work differently.

I am having trouble modifying elements on the page list in administration. I am trying to do this: $('.PageListActions').addClass('test'); (Actually, I am trying something more complicated - but this is a simplified example just to work out the problem) The problem is that it is simply not taking at all. I have used similar bits all over an admin theme, but when it comes to the page list, it all falls over - or rather, does nothing at all. I have tried both $(document).ready(function() { and $(window).load(function() { and stuck it all over the place, but to no avail. I am assuming it is something to do with how the list is loading, but I dont know what to do about it. If I work my way backwards, I can addclass to PageListRoot, but not to PageList, which comes after the loading span. Anyone got any suggestions?

Goedenacht, Martijn

oh! The button says "Like?" I must invest in some new spectacles..... (And thanks for your menu help anyway!)

Ah, that is exactly what I need (or will need) later this year for something. Nice one!

Hi Martijn I think I mentioned that. That is the best way of creating a library since it uses the native PW PAges structure, is automatically categorised by the Tree (to a certain extent) and is accessible. However, it should also be accessible for an images field and not just for TinyMCE and, ideally, you should be able to upload to that pages tree even though you are on a completely unrelated page. The existing system is part the way there already really, at least philosophically!

Ooh, just learned something! Thanks.

*puts unfinished novel back on shelf*

Hi Christoph Although you might hide the parent (and therefore the children will not appear on the menu) the children and the parent are still published. If you look through the Cheat Sheet you will see you can call a specific page and then the children. So, for instance $pages->get("/path/to/page/")->children - will retrieve all the children to a specific page. Now you can create a foreach loop to retrieve the fields you require from the children and display it however you wish. http://processwire.com/api/cheatsheet/

I agree - I like to make sure I have lots of Soma's modules installed to see exactly how much trouble I am in ....

Now, that is a challenge. The last proper development report I wrote was 70,000 words..... (Damned thing didn't happen either!)