diogo

for this kind of relations i think the best way is to use the Page FieldType. you can put one on the race template where you can choose the teams, and one on the teams template where you can choose the people.

maybe they can be there filtered, just like the advanced things

I posted before on the forum this article in German http://web-developer-blog.com/2012/04/processwire-das-geniale-opensource-cms.html You can use google translate, just as i did

What if you put the whole path on the post template? echo "<img src='http://{$config->httpHost}{$page->image->url}'>";

You can use $array->remove($page) As Soma likes to do: http://processwire.c...->remove($item)

Funny I tried this and could reproduce the same error, then I created a new fieldset and everything worked, then I tried again with the previous and it worked again... now I can't reproduce the error anymore and I'm not sure what changed. Still, make sure that the seo-serp_END field is really of FieldsetClose type. Or just delete it and create a new one to see if it works.

Welcome to the forum Seán! A similar question was asked just yesterday here in the forum. You should find the answer you need there http://processwire.com/talk/topic/1467-multiple-images-and-basic-questions/

Still it does behave nicely when resizing the brower. I would just put a transparent 2px border under all the nav links, so you don't have the behavior that it's happening now (because there is a border only on the active link, the others don't flow well under it). Like this they will stack nicely under each other. Also wouldn't hurt to make the image smaller when the browser is resized. You can do this for instance: #photo{ width:100% max-width:1000px } EDIT: concerning the image. Even nicer would be to have the logo as a transparent png above it, and crop the left part of the image as the browser is resized down, keping the logo in place. Like this you will have a responsive website without any media query

Soma, you can do this without having to upload them again?

I don't think you have this option via the API... The only way i can think of doing it without messing around with the dB, would be creating an extra field that would have a sequence like "0,1,2,3,4,5,6,7" with the same number has the amount of pictures, and updated accordingly to change the order of the pictures in the frontend "4,7,2,1,6,3,0,5". To output the pictures, you would convert the field to an array and iterate through it. $sequence = explode(",", $page->extra_field); $images = $page->images; foreach ($sequence as $i){ $image = $images->eq($i); echo "<img src='{$image->url}' alt='{$image->description}'>"; } too complicated?

Hi, and welcome to the forum. I made exactly this same question to myself, and I think I even asked somewhere in the forum. I don't remember what the answer was, but I think I know the reason why this isn't possible. The thing is that, you have a one-to-one relation between fields and pages on the database, So, although you can give the field a different name on each template, for the database they are always the same field, and so, they just can't be repeated in a row/column logic associated to the same page. Am I right? I hope I'm not saying something completely wrong I would definitely use the second option.

You didn't realize that it's responsive because it's not

Welcome to the forum! What you are describing is exactly the opposite of how ProcessWire works. This would imply that all markup would be generated by the system instead of by you, and remove all the flexibility that is the core of this system. Not saying that one day there can't be a module that will allow this, but for now, I find it very unlikely.

Maybe surprisingly, I don't use any I use some extensions though.

Why don't you simply populate the title with the native id? edit: lot's of whys

Dave, here is a bookmarklet made especially for you javascript:(function(e,a,g,h,f,c,b,d){if(!(f=e.jQuery)||g>f.fn.jquery||h(f)){c=a.createElement("script");c.type="text/javascript";c.src="http://ajax.googleapis.com/ajax/libs/jquery/"+g+"/jquery.min.js";c.onload=c.onreadystatechange=function(){if(!b&&(!(d=this.readyState)||d=="loaded"||d=="complete")){h((f=e.jQuery).noConflict(1),b=1);f(c).remove()}};a.documentElement.childNodes[0].appendChild(c)}})(window,document,"1.3.2",function($,L){$('.searchlite').removeClass('searchlite');});

We don't want people to have access to the trash so they can't irresponsibility delete some important thing, right? What about giving them access only to recover things?

Maybe you can pass the query on the url via GET, or even parameters, and prepare the templates to do a str_replace on the fields.

I understand what Ryan says here, but I will like everyone that suggests these I even think that something along maxSize should be the default behavior, because no one wants to see giant pixels on any picture.

Ok, I'm convinced Gosh*

Ya, I meant those. 1000px was a rough guess Perfect! Hm... don't forget that this is targeted also at non designers or developers, and also that too much customization can potentially turn the theme into an horrible explosion of colors.

I do prefer this one But: I think the search box doesn't fit the theme. On the 1000px media query break, the right column could go under the left column, to prevent both, the text from the sidebar and main text, to become too short. I would give the option, not only to choose the color, but also to remove the 1px vertical borders. It's amazing how this simple change can turn it into a different theme.

I totally agree with this. I even think we should take this as concept for PW. I really like the way things are happening here. Most modules are discussed in the forum, and each module gets lots of input from the community before it's finished. I know that it isn't easy to keep it like this, as the number of users and developers grow, but would be great if it would be possible to keep a truly useful official modules repository (not too big, and without repeated functionality). This could be done via the forum, and via a small number of administrators who would filter, and propose the merging of modules with the same functionality.

From what I understand, you just have to put the jcart folder on your PW templates folder, and include it on your templates with: include_once('jcart/jcart.php');

I don't, I didn't use it more than installing and having a look at it. And this was before I met PW, when I was still in the process of choosing a CMS to work with. But it does look interesting. Ya, I heard about the community not being very friendly. I back what was said here by others. At this point I'd rather spend my time learning PHP to start building modules and helping with the evolution of PW, then learning another CMS.