Joss

I have been concentrating so much on working out the best (for me) way of structuring sites using ProcessWire, creating snippets for myself, understanding how it works together, that I have yet to look at how to create a custom, front end system for adding pages, basic management and so on. What I am thinking about is creating a simple system, perhaps with a blog, where you can create/edit/publish/unpublish a particular set of articles via the front end in custom forms without having to worry about page structure and so on. So, this would entail: Front end login/logout/account management Front end page list with edit/delete/publish buttons Front end Create New.... Er ... maybe a couple of other things. The thing is, I really don't know where to start! How do I protect my front end forms/templates so that only a logged in user can see them? How do I create a management area? How do I edit an existing page in a front end customised form? What I need is just some very simple pointers of what I should search for, which elements of the API I should be looking at and so on. This is just for my own learning, so I don't want to use the form builder - I need to understand this properly for my own education. Thanks Joss

When I look at what is saved in Joomla, it is just the path to the images directory as a relative path - eg: images/storyimage/myimage.png So, as long as it knows what "relative" means, then it will render the image. It does not matter whether the installation is in a sub-directory or not; it doesn't care as long as it knows what the base URL is. The {root-url} in your example above, should just be a value in the template that means it always knows where site/ is (rather than /site/, if you see what I mean). Then, if a similar value is available in the backend, then TinyMCE should save images just as site/assets/ or /site/assets/ (not sure which is best - probably without the first slash)

Trust me - off the cuff interviews, even with corporate subjects, are always the best. Rehearsed interviews, even on paper, come across as contrived. We used to have a rule of thumb that it was not in the interest of most radio stations, magazines, business publications to make you look bad. They end up looking weak and poisonous, and it undermines their role which is to inform their listeners/readers. You have to be a little careful of that principle on the web because their are a lot of blog owners out there who have not had formal journalism training or worked in mainstream media, and think that it is all about them and not the interviewee. But with people like Mke at CMS Critic, he seems to have got his head round that one and it was a well laid out interview.

Apparently you can - same as with Bootstrap Edit: Also, I have just updated my Bootwire Starter profile and the accompanying Bootwire Demo Profile http://bootwiredemo.stonywebsites.co.uk/ See this thread: http://processwire.com/talk/topic/2411-bootwire-basic-twitter-bootstrap-profile/

New Bootwire Demo Profile This is a demo profile built on the Bootwire Starter Profile It has a few extra fields and templates, just enough to show some of the functionality in a working situation. It also comes with the Bootwire Admin theme. If anyone has got time, I would appreciate any comments, especially some proof reading! See it here: http://bootwiredemo.stonywebsites.co.uk/ Download it here: http://stonywebsites.co.uk/Bootwire-Demo-Profile.zip

On my testbed version I have got flexslider working in three modes - slide show, carousel strip on its own, gallery with fade-slideshow and carousel synced together. Just with different css classes. Works quite sweetly.

I thought it was Mambo, phpNuke and News Publisher

Will do

I keep staring at the back end of Joomla to work out how they deal with it, but the only thing I can think of is that they define two base URLs - one for the backend and one for the front end. That way they keep in sync without having to worry about the fact that the admin is in a different directory. But to be honest that is a guess.

Welcome Christian ProcessWire seems to be building a solid German following! Which is good news. Yep, the forum is friendly and is more active than many forums many times the size - one way or another you should find everything you need here Joss

One day I will do this properly completel with examples, but for the moment, this is a hints and tips approach Creating a proper video tutorial First of all I have to say that I am not in favour of video tutorials for myself, especially covering a subject which is basically concerned with reading and writing. However, they do work well as an overview and many people like following them. The Big Wrong Things "So, what can go wrong? I mean, I know the subject, I sit there coding every day, this is my world - just turn on and record. What is the problem." The list is, sadly, endless. But here are a few things that can ruin your plans (and spoil my viewer experience): Mouse pointer waving around pointlessly Bad visual quality so it is unreadable at full screen Irrelevant windows all over the place Endless leaping between this screen and that screen and this and that folder, application and so on Muttering Repetitive, "I will just ... er,...not there ... oh yeah, that one.... oh, forgot a bit..." Forgetting to introduce not just the video but the various parts Tiny font size Buzz words, nicknames, unexplained short cuts ... Too long Trying to tackle a too complicated a subject And there are many more. So, how do the pros do it? I probably have a bit too much fun listing all the things I have done over the years just to confuse people, but the truth is that my main role has been rather bland - I have produced and/or recorded THOUSANDS of sound tracks for corporate productions, and video edited and even directed quite a few too. These have tended to be big budget affairs with professional camera operators, enormous Grass Valley editing suites, professional presenters and voice overs and so on. But that does not mean that the skills eat up the budget - it is just the fees that do. The skills are straightforward and logical and are free to anyone who wants to practice a bit. So here is a bullet pointed step-by-step guide. 1. Preparation Knowing what you are talking about ISN'T preparation - it is nothing more than a knowledge base. Most technical videos are written by people who do not know the subject but do the research and turn it into something meaningful. Trust me, even if you know the subject inside out you still need to do research and preparation: What level of expertise does the audience have? What is the conclusion of your tutorial? Do you know how to explain every action your will make? If you go through what you are trying to do correctly, you will find out there are lots of things that you know instinctively that you realise others might not know, or you have no idea how to explain. List them. Break it down. Remember that your audience cannot read your mind, so look for the things that you frequently skip over that may lose someone not living in your head. 2. Script Writing I cannot emphasis this enough - WRITE A SCRIPT!!! I don't care that YOU think you are the best ad libber around - you aint. I probably am, but I would never do a lesson unscripted. Even politicians who do long speeches "unscripted" don't really - they script every word and then learn it inside and out over days. Writing scripts scares the bejeesus out of people, which is why there are so many terrible, unscripted tutorials out there, but it is not as hard as it seems and it will make the rest of the process far easier in compensation. Start with a list. Coding tutorials, in particular, are nothing more than a list of actions - write this, press that, check this. So, when writing your script - start by doing that. Make each action as short as possible: "Open a new file" "Write <?php at the head" "Save file" and so on. It is as boring as hell, but you will not only get the lesson in the right order, you will quickly find out what is missing or what does not work. Break it into scenes. I think most people think that scenes in videos and film are three or four pages long. Well, to be honest, a lot of them are just a few lines. Think of it as a paragraph. Take my bullet points above; creating a new file and preparing it to be used as a php file is a complete action - it is a scene. The next scene maybe setting out two or three empty functions for one particular aspect, or perhaps preparing some other files. These scenes are intentionally short and this will become important later. Turn it into SPOKEN English/other language. This is distinct from language to be read. When we speak, we use short phrases, breath a lot, use huge amounts of semi-colons and frequently start sentences with "and." Your script will be spoken out loud and when you start turning your list of actions into sentences, you must remember this. Read each sentence out loud as you finish it; not in your head or mumbling, but right out loud at the volume at which you will record the finished video. Do not run words together, remember to hit the consonants NICE and clearly and look for the emphasis words; you can ALWAYS use capitals if that HELPS. Recording This is your make or break moment! Actually, no it isn't - you just did that when you wrote your script. If you have written the script well, the the next stages are predestined to be okay. You will make mistakes, but they will be easy to correct. It will only go wrong if you have left stuff out of your script, so read it through a few times to make sure it is perfect. Then PRINT IT OUT. Should you rehearse? Yes and no. You will not be recording this in one lump (that way lies madness) so it is a waste of time rehearsing the entire thing. However, rehearsing each section before recording is a good idea. You need to work out your moves between screens and how you speak the words. In the pro world we would only do a guide vocal at this point and then the voice over would come into my studio with a tidied script and we would re-record the final version. That is why pro stuff is so good. You can take that route if you wish, but the chances are you want to talk as you go. Take One You have written this in scenes, so only record one scene at a time. Play it back when you are happy and make sure it makes sense. These are now bite sized so are much more manageable that working in huge chunks. Put your screen recorder into record and wait a few seconds before you start talking or making screen actions - it will take the pressure off. In the pro world, when the director yells ACTION, there is always a pause while the performers get their brains into gear. And good thing too - otherwise their first words would be a reaction to the shouted word "action" and not as part of the scene as they should be. This applies as much to a corporate as it does to a drama. How many takes you do is up to you - but do not be pissed off if you have to do several. Coders are meant to be perfectionists, and doing a voice over and screen shots requires just the same attitude and degree of patience. What speed should you speak at? Slower than you think is right. This is not a commercial and you are not a professional voice over. Speaking clearly at speed takes YEARS of practice and even some of the best voice overs never get it right. But in corporate presentations, speaking fast is an absolute no-no. Speak evenly, in a considered, non-patronizing way, emphasising all the important words and resist the temptation to speed up towards the end of the sentence. Emphasis is a funny beast - many people believe that we emphasise by speaking louder. But in reality, we emphasise by slowing down the word and leaning on one particular syllable. Which word and syllable you emphasise is important too. There are two main forms of emphasis - importance and comparison. Importance is where you want to make something the most important bit of information. That can be a verb or an adverb or adjective. "It is VITAL that you shut the door." Vital is the important word here - you are emphasising the importance of the action "shut" by saying how vital it is. Comparison is when you are offering an either or - even if you are not explaining or referencing what the other thing might be. "It is vital that you shut the DOOR" Here it is now the door that is important and we are saying you should shut the door, rather than a window or cupboard or anything else. It is making a comparative. You can get it wrong. "What did you do in the nineteen seventies?" "I went to school in the nineteen SEVENTIES." That is the wrong answer, even though it is the correct words. You have made a comparative of the date. You should have said: "I went to SCHOOL in the nineteen seventies." On your printed script as you rehears, underline words that you should emphasise to make sure you don't start making it confusing simply by emphasising the WRONG words, and make marks / where pausing slightly / will also help with clarity. Your reading will be much better and the whole process much easier. Editing. You can ruin good footage in an edit, but you cannot do a great edit out of terrible footage. Do not rely on the edit to save you - get it right at the recording stage and the editing will be more fun. You have written this in scenes and when you edit, respect those scene breaks. You probably broke it up at logical points so it will not help if you try and run it altogether seamlessly. Pause between scenes - if there are major breaks, consider fading to black and slipping in a caption; it might give people break points to stop and take stock and it will help with the clarity. Do not put music over the main content - not that sort of video. Clean up the sound as you go - remove any paper rustles or next doors dog barking! Think about pace - keep the edit pace even. Avoid tricks. Just stick to fading in and out of black - don't spiral stuff in and out or do other things that your editor can do. Again, wrong sort of video. People are not looking at this for your editing skills, but your coding skills. They should not notice the edit at all - just absorb the wonderful knowledge that you wish to impart. Try to avoid zooming into a screen - the quality can fall apart very quickly and you will have achieved nothing. Presenting your final edit You have gone to the trouble of writing a script, so when you put your video up, maybe put the script up there with it - might help people as a quick reference! Make sure you précis your video with a good written summary of what it is about and what you hope the viewer will learn/achieve. And that is about it! I have not covered every single pitfall and problem you will encounter - that would be a book's worth and a boring one at that! But hopefully I have given you some fairly straightforward, easy to follow advice that will just help your next video turn the corner from "nice chatty person telling us something" to "expert giving serious guidance." Happy filming! Joss

Good interview Ryan!

I think I should start giving lessons on how to do voice overs. Ryan is better than most techies. but you could all learn from a few simple tricks: WRITE A BLOODY SCRIPT AND STICK TO IT!!!!! Oh, and do it in sections - NEVER EVER try and do it all in one go. There are plenty of free editors that are pefectly good for editing things together. Think I will go and write a post somewhere....

Ah, Bon! Merci! I thought about just about everything that was not being grabbed - forgot all about poor little user! Thanks, Ryan, that worked.

UPDATE I have updated the Bootwire Starter Profile to version 0.5 This version included a functions.inc file that is included into the head.inc file. This file has demo functions of various Bootstrap functionality that can either be used immediately, or (more properly) used as a starting point for your own functionality. These versions are kept very basic. Functions include: Carousel Collapse (accordion) Tabs Button Dropdown Thumbnails used as a gallery The functions are fully commented with instructions as to which fields were used or need to be created. I have also added a bootwire.js file that includes a couple of bits of JQuery to correct some issues with thumbnail and div alignment over multiple rows. Read the instructions to see how to use this code. Hopefully, this profile is now very functional as a base starting point. Any feedback from testing would be appreciated. Joss Note: I have temporarily removed the link to the demo profile while I update it with the new functionality

Stunning Luis!

Well, its part done, but Joshua is currently working through some major updates with Kickstart, so I am waiting to see what he comes up with. I have currently done a sort of proof of concept, but I have changed a couple of his JQuery utilities - changing fancybox1 for colorbox and bxslider for flexslider and his tabs script - so that it is compatible with JQuery 1.9.1 - But I think he is trying to address some of those issues anyway, so I dont want to get too far ahead of him. The approach I am taking with this (and I am redoing my bootstrap in the same way) is a function file with some of the main components demo'd using basic fields. That means to get them working you can just do <?php loadKickwireTabs(); ?> in your template file and you will have tabs, assuming you have done your fields the same way. Most people will then edit it like crazy to put their own fields into play, but at least they have the basic markup done rather than have to start from scratch. Obviously, that is only for a few things like carousel, the rest will be up to the user! Joss

I am using the multi-language module for processwire. I have set up using example 3 on the documentation page: http://processwire.com/api/multi-language-support/multi-language-fields/#examples And I am looking at the code from example one to sort out my navigation. However, my navigation is in a function (thanks to dear Soma) and I cant get the right values to leap the function barrier. The code I need to run for my menu is: if($user->language->name != 'default') $segment = $user->language->name; else $segment = ''; And then output $segment into my URL. But I am not getting any value out of $segment, so I assume it is not getting $user->language->name from outside of the menu function. What am I missing? Joss

In theory - but I am not sure when! I still miss my old sony Z5 I was just thinking, would it be possible to add a bit that defines a gallery? So you would create two - one with the "name" myphoto, and the other morephotos and then on the email, immediately after an image, put either myphoto or morephotos. The script reads that and accesses the right page. If nothing is put (or it does not relate to a known gallery) it goes to which ever is the default. EDIT: you could extend that for adding a caption too. caption: my caption

Oh, very clever! (I cant test it because my mobile does not take photos and cant email either!)

There is another one here http://wiki.processwire.com/index.php/Basic_Website_Tutorial

HI Georgson As you scroll down, on the right hand side of each section, there is a Green square. You have a right angled bracket in it > which looks like you can scroll through something, but in fact it takes you to the top or the page. Nothing major, it just through me for a second.

Very slick! I really like it. Just one tiny thing - I was confused by the right Arrows > until I realised that they take you to the top of the page. Should they be Up arrows? Rest is really nice. Congratulations!

Yeah, I was going the "if you shove the wrong path in this field don't blame us if you suddenly make your entire private website available as a download to some idiot hacker with a Guy Fawkes mask" route. PS: Make sure the directory actually exists.

Just as a thought, is it worth, even at this very early stage, having a field for putting in an optional path for the backup? Doesn't feel right putting the backup in the very directory that you might want to rescue if something goes wrong.... So, nice to put it above the web root, where possible.