Martijn Geerts

Some companies still using XP so IE is limited to IE8, the real problem here is not IE8, but their compatibility mode. Which turn render engines to IE7. We all hate the box models in IE7 and hate the bloated extra markup to let it work as expected. But we can't simply use conditional comments to know if IE8 is rendering in compatibility mode or not. (This is real ugly) I do think in a controlled environment (pw admin) we should set some restrictions. All companies using XP, can browse happy the internet. Please Ryan, drop IE8 support and make happy site editors !

If you have popular video's on youtube, then from youtube there can be links to your site. So having youtube movies can have a positive side effect. An other positive point is that YouTube movies can bring in some money. But using Youtube as SEO tool is a whole lot of work , and I don't think it's worth the effort.

The complete error message is I think: "Your submission was not saved due to one or more errors. Please check that you have completed all fields before submitting again." So I do think that or you've build the comment form yourself, and there's a typo in the name of the input or not all fields are filled in.

Stupid game.... (can't stand I still didn't reached 2048)

The pedigree is a little more complicated, so I need some structured data where I can work with. If you trust & allow me you can send me login credentials to the site or send me the site zipped including SQL dump and I can figure it out for you.

I didn't post anything for the pedigree. The pedigree part can be done later on the horse template. Don't overcomplicate things, just build things from the bottom up. The part I posted goes till you have a list of horses. (Pagearray) That array you can loop and link to the individual horse. ( So forget about the pedigree till the navigation structure is complete. ) These are in the group contexts just search filters: - a checkbox, named: horse_owned, (horse template should also have horse_owned checkbox, checked means you're owning the horse ) - a checkbox, named: for_sale, (horse template should also have for_sale checkbox, checked means you're willing to sell the horse ) - an Inputfield type Page, see structure above name the field 'types' (IS this Field for the Select "- a Page field, [stallions, Broodmare, Colt, etc..]" ) Inputfield type Page in the horse template just to identify what horse type it is. But it the Group template it is used as a filter. (the code is fro the group template) Here you gonna test if the UrlSegments matches the checked horses in the group template. This way you can control which horses to list. If your navigation setup is complete, I can help you to setup the pedigree function inside the horse template. I would advise you to leave it alone for now.

The thing you should remember is that each item in the repeater is a Page. You should threat them as they are pages. foreach ($page->home_bullets as $bullet) <-- here bullet is the page If images is a multi image field, you can get them all with the repeater-item page. $bullet->images // all images, these can be looped. (see the page named $bullet, coming from the foreach above )

I can't find the time to install ImageMagic. Lot's of stuff happening right now and to many things on the todo list... Wished, time was on my side.

IE8 in compatibility mode uses the ie7 engine. I still need to support that from time to time... But as Support for XP is dropped, brighter skies are on the horizon.

@Shehbaz, welcome !

It's been on my mind for quite a long time. The reason I didn't start it is the reason you mentioned. Maybe someone comes up with a genius solution.

search: "site:processwire.com/talk/ soma or diogo" result: "Mixed Joss with Soma - ProcessWire"

uuuuhh... ooopss, silly me I didn't realize it... (but I knew) There's something suspicious with that name.... Sorry bout that @einsteinsboi.

On the otherhand, Adrian really love loops... (I did almost the same this morning as I remembered a post from DaveP)

Up to a few moths ago I read all forum posts, but lately I can't keep up. 3 reasons for this: 1) Not much spare time, but the most important 2) ProcessWire has a growing community, ways more posts then a year ago. 3) lot's of things to checkout like new modules. @einsteinsboi has it right that he points to the /api/, and look at @adrians posts, search the forum with google.

This is exactly what I was thinking. It's a pity that you discover this bug so early on. Most little bugs in PW are solved soon and ProcessWire is really stable.

Haven't seen the issue for a while, but I think it's still in there. Somehow it's hard to track this down. I've spend some few hour on this but couldn't find anything suspicious.

Create this structure: [ later on used for the Inputfield type Page (Multiple) ] Home | +-- Types (template: types) | +-- Stallions (template name: type) | +-- Broodmare (template name: type) | +-- Colt (template name: type) | +-- Foals & youngs (template name: type) | +-- etc. // both templates need no template files To the template 'type' you add a textarea with a WYSIWYG editor if wished. On the Horse Template 1 ) a checkbox, named: horse_owned, 2 ) a checkbox, named: for_sale, 3 ) an Inputfield type Page, see structure above name the field 'types' Group template ( Our Horses & Horses for sale ) Assign the same fields as above to this page. 1 ) a checkbox, named: horse_owned, 2 ) a checkbox, named: for_sale, 3 ) an Inputfield type Page, with the structure drawn above ( Name it types ) The real purpose of these fields in the 'group' template are for building the search query to the horses you want to list. (Tell you later more about this) Enable urlSegments to this template. Create a Page with the group template named 'Our Horses' Check the checkbox 'horse_owned', so it has the value of 1 Leave the checkbox 'for_sale' unchecked. For the 'types' field select: [x] Stallions [x] Broodmare [x] Colt [ ] Riding Horses [ ] Foals and young horses Those checked pages are used for the urlSegments. Basic structure of the PHP file could look like this: $segment = $input->urlSegment1; $types = $page->types; if ($input->urlSegment1) { $name = $sanitizer->name($input->urlSegment1); $type = $pages->get("template=type, name=$name"); if ($types->has($type)) { echo "<h1>{$type->title}</h1>"; // echo $type->body; // assumed the textarea added is called body // scaffold the search query $query = array( 'template' => 'horse', 'types' => $type, 'horse_owned' => $page->horse_owned, 'for_sale' => $page->for_sale, 'limit' => 10 ); $query = array_filter($query); // remove all boolean false elements from array $string = ''; foreach ($query as $key => $value) $string .= "{$key}={$value}, "; $string = rtrim($string, ", "); $horses = $pages->find($string); if(count($horses)) { echo "jay we have the horses"; } else { echo "Sorry, at the moment we don't have the horse that you're lookin for." } } else { throw new Wire404Exception(); } } else { echo "<ul>"; foreach ($types as $type) { echo "<li><a href='{$page->url}{$type->name}/'>$type->title</a></li>"; } echo "<ul>"; } (not fully tested, so could have a bug or 2 )

And rebuild the EventsFieldtype a little?

$options = array( 'cropping' => true, 'quality' => 80, 'remove_variations' => true ); ?

I really liked this idea & added this setting, tnx for mentioning it @wanze It's splitted in 2 settings actually. 1. Specify the headers. 2. Start with table. This way it is possible to start with a table with or without the headers. If start with table is set, it prevents editors to see th CSV import. As in Europe (most countries) floats are divided with a comma and not divided with a point. As a result CSV data mostly use the semicolon as a delimiter. There's a setting to set the delimiter to comma semicolon or tab. In the Inputfield, the editor can upon CSV import choose which delimiter to use (by default inheriting the default setting). The force to integer setting, will recognise if the European float, and will convert this to normal float. ( heavy on CPU, so only check if needed ) @adrian, also added the ability to delete all data returning to the CSV import.

I love the ProcessWire road with the by-product of learning PHP. ProcessWire makes me eager to learn. And for the question: I don't like HTML in my template, I like php strings of HTML better. At the end it just makes it more readable. Mostly <?php is only used ones at the top of the file and thats it.

Didn't read your message very well, nevertheless I hope that you get what I want to say. I can see you love using relative names (child-template, parent-template etc.). Using names this way makes it really confusing. What if the child-template, has children and if those children have children to? You'll end up with a template named child-template who is actually grandpa. Consider relative template names in a static way bad practice. My father is child of my grandpa and is grandpa of my child.

echo "<a href='{$page->url}tralala/'>tralala/</a>"; tralala could be any string you want.

i'm confused here. what values should the field drenthe has ? Does it contain a pagearray of all cities in Drenthe ? But in your drawing you draw pages. It's all to cryptic. urlSegments are just a nice fancy alternative to get variables, so you should treat them like that. For relative simple sites you don't need them most of the time. As said before, the best thing you can do is to start simple, and start with the documentation from ProcesssWire.