Joss

Just because I am really nice and like to keep things nice and tidy for young Soma... Is there an issue with using the color picker in conjunction with a repeater or a page select field? (or in my case, a mixture of both) Happy Days! Joss

Hi Soma - I wasn't totally sure it was a problem or whether I was doing something idiotic. And I had a vague memory that we had this conversation a couple of months ago

Update Okay, I have it all working now (my original code was fine) But, I am not getting the colorpicker field. The value is in the database, but I cannot return it to save my life. Any one had a problem with this before?

Okay, I think the problem is two fold Firstly, I have an background colour as one of my fields, and I seem to remember that the color selector doesn't work with repeater fields (actually, I may be misremembering that) - it just so happens that that was the field I was testing. I am getting an image problem too. So I think what is happening is that it is getting broken before it can output the data. I have just got the title to work.

I have a repeater field called block_footer_boxes_repeater Within the repeater are two fields: block_span, which is a simple text field block_select which is a page field. The page field is for selecting a single page which has a pile a fields in it. For the sake of this argument I will use just one: block_textarea_body So here is my very simplified code (the proper code is a lot longer because of lots of fields and ifs, maybes and the odd but!) $footblocks = $pages->get("/settings/footer-settings/")->block_footer_boxes_repeater; foreach($footblocks as $footblock) { echo $footblock->block_span; echo $footblock->block_select->block_textarea_body; } The span is working fine. The block_textarea_body is not. I have also tried: echo $footblock->block_textarea_body; But that doesn't work either. Just to emphasise that the page field is only selecting one page at a time (and is set to the single select option), so it is not an array. Umm ... That is about it. Kind of stuck now! Joss

I remember one of our runners getting one for his birthday and turning up with it at the studios. He was so pleased with him self. At the time, my brother was working for the great Ed Ross (designer of the Quantum statistical engine) just down the road and they had bought a brand new Prime mainframe. (I think we used it to play a very early version of Zork - well, had to use it for SOMETHING important!) So I looked at this rather dreadful wooden box with a few wires coming out of it, then I looked at the mainframe with its room full of white terminals, humming air conditioning and huge, floor standing drives.... Little did I realise that the tatty piece of nonsense was destined to be far more influential and important that that hugely expensive, room full of tape drives!

Thanks Jeroen! I will have a go at that

New Stripped back version called Bootwire Starter now available on Github https://github.com/jsanglier/Bootwire-Starter-Profile (Hey, I almost sound like a pro - well, almost....)

Tandy Basic? (Sorry, that is probably far too "uk" and, um, old)

Quick, rewrite PW in PERL!

Really? At that time I was already on to my second career!

Everytime I see <? rather than <?php I think... PHP3!!! Much to my amusement, I noticed that an old acquaintance of mine that does a little bit of really, really bad website design and hosts on his own server, is still doing everything in PhP3. But then, he is also still doing everything a fixed 640 width and with very little CSS. I think he sees "styles" as something the gaming kids play with while serious people use <font>. He has eventually stopped wearing cords, however.

Oh thanks! I am inheriting an iPhone 3 next month - till then I can only try these with browser re-sizing!

Hi Aren I haven't used EE so I can't help you "translate" However, I will just deal with the slideshow for the moment. I will assume that the slideshow is just an image for the moment. You can do this with just one field - create a new field using the Images type. Call it slide_images (or anything) You can set that field to upload as many images as you like. It also comes with a description field which you can use for a basic caption. Add it to a template. The images field will return an array of the images. So, in the template file do: <?php foreach($page->slide_images as $image) { ?> <img src="<?php echo $image->url; ?>" /> <p><?php echo $image->description; ?></p> <?php } ?> That will return all your images - all you need to do is to make that work with your favourite slider! If you want a much more complicated system, you can use "repeater" fields, which is a way of grouping fields together and repeating them in the form, and also the Thumbnails module, which is an alternative image field (crop-image) that allows you to create whatever thumbnails you want while uploading image. http://modules.processwire.com/modules/fieldtype-crop-image/ http://modules.processwire.com/modules/fieldtype-repeater/ Joss

http://pwdemo2.stonywebsites.co.uk/ This is built on my Bootstrap profile and is simply a demonstration site for clients - which may explain the slightly odd copy. Images are out of stock (and then heavily processed!), except the food images which are mine (I did the cooking too!) The demo includes a block creation and management system, a news system (ultra simple), a slideshow and is fully responsive (as is the admin ) I started the site from scratch at eight this morning, had half an hour for lunch and took the dog out for two hours this afternoon. It was developed on a local server and then uploaded to a sub domain. The entire site is only just over 4 mb including large images. It loads nice and fast!! (Thanks Ryan) There is NO WAY I could have done this so fast on any other CMS - the only way I could have done it as fast would have been as a static site - but then it would not be easy to manage. Don't you just love this system? Joss PS: The ice cream on the food page is mine - made over the summer from our own home grown strawberries and then mixed in a very basic ice cream maker with just a dash of cornish clotted cream. Thought I would drop that into the mix.

Head over to the Cheat sheet again and look for inputs ... that is where the gets and posts are. That way you can use just the one category page So, you can make an href to /blog/?cat=<?php echo $category->title; ?> and then on the incoming category page, fetch the value with $category = $input->get->cat And do with it as you need.

It is also how things like Disqus work, so it will help those who want that sort of functionality without having to use a third party system. In the Looooonggg term it might be nice to have just the one system, but be able to switch the display - either from the admin or by the user (or both)

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.