totoff

Hi nikola, thank you very much for your reply and I'm sure there is no need to apologize, absolutely not. You have contributed a fantastic theme, what more could we expect? Your plan for two themes sounds good.

Very good advice. And a very well designed site. Like it! Congrats.

Hi Nikola, do you plan to continue development of your theme? Or did you stop it? Thanks for letting us know.

A fantastic read, thanks Felix. I'ts good to see more developers with experience at enterprise level switching to PW. Provides us with better arguments when talking with clients. Funny remark about the English/German discussion: you use quite a lot english words (Anglizismen) where you need to be very precise ;-)

thanks to everybody who replied so far. i get a better understanding now. very helpful indeed. in particular thanks to matthew and mademyday for your profound insights. not yet. the project is at a very early stage. but unfortunately the project lead, the person that engaged me, made some determinations before they got me on board. one of this determinations are the joomla orientated coders. my advise to her was to set up information architecture first and to make a list of features required and then to decide which cms fits best - as it would be natural to all of us. if you don't mind i'll get back with more detailed questions once the concept has evolved and it comes to decision making.

you don't even have to use the children function. you could search for the post template instead with pages->get (http://processwire.com/api/selectors/).

let's say you have the following structure: - mypage -- post 1 -- post 2 -- post 3 etc. a post consists of a title and a text (to keep it simple). your goal is to display all content (title and text) from the posts on "mypage". that's pretty easy: 1. make a template "post" (it doesn't need to have a template file. it's just for holding the fields) with a title and a text field. assign it to your post pages and fill with content. 2. make a template "my page". assign it to mypage. from this template you loop over the child pages ("post") and retrieve their content. for example: <?php foreach($page->children as $post) echo "<h1>{$post->title>}<h1>"; echo "<p>{$post->text>}<p>"; ?> that should to the trick. EDIT: adrian was quicker. And sorry for the formatting of the code (which is not tested).

very nice site. one thing to polish though: on the media page (http://www.tamperemusicfestivals.fi/jazz/fi/media/) hovering over the thumbnails shifts the rows a bit. i assume this is not by intention. EDIT: Win 8.1 (awful, don't buy), Chrome 30.0.1599.101

let it be pages. easier to maintain, better performance (in case there are a lot of articles), accessible for future development of your site.

Hi folks, I'm currently engaged as a consultant for a lager scale web project. I advise on strategy, information architecture, content etc. but very few on the operational side of things. Coding will be done by guys that favor Joomla as CMS platform to go. Apart from my personal like of PW, I've never ever heard anything positive about Joomla from the community and I'm almost convinced that it is not the right choice for an enterprise-level project like ours. However, I'm lacking arguments as I have no experience with the system and everything I "know" is from hearing. Knowing all the pros for PW from my own experience I would like to learn what are your arguments against Joomla? Glad if you could give me an idea from your point of view. Maybe there is a small chance I can position PW as better alternative or - if not - at least avoid a wrong decision and vote for an enterprise-level system like Drupal or Typo 3. Just to clarify: this is not about bashing a competing CMS, it's about investing a significant budget wise. Thanks.

i find the logo in the middle intuitiv enough, but know that people sometimes expect a home link. anyway, i would say leave it as it is. how did you solve your navigation problem? http://processwire.com/talk/topic/4672-navigation-help/?p=45622

very limited in time my first idea for this kind of "dom manipulation" would be jquery rather than php. maybe this helps: http://tinysort.sjeiti.com/

declarating the charset in screen.css with @charset "UTF-8"; has solved the problem. it's a paricularity of sass.

thanks martin for taking your time to help me. i think i might have found the answer. seem as if sass outputs a wrong charset declaration, see here. i'll give this a try later tonight and report back. anyway, strange things happen with all this new technologies ...

hi martijn, unfortunately not. just a cut-and-paste error.

hi folks, a client of mine reports broken styles on his website when viewed with apple devices (ipad, iphone, macbook pro). affected are list styles i realised with css ::before pseudo element. this is the css: #main ul > li:before { color: #005AAA; content: "–"; display: inline-block; font-weight: 600; width: 20px; } you can see the problem here if you are on apple: http://www.praxisbedarf-mainz.de/sortiment/verbandstoffe/ me too, i can reproduce on several apple devices but i have no clue what goes wrong. i've searched the whole internet but it seems as if all safari editions back to version 2 should be fully compatible with pseudo-elements and no similiar problems are reported on the usual forums like stackoverflow etc. sure, i've already tried to replace the content inserted by ::before with another content. but it returns a mess no matter what i insert. is there anybody in this forum who has come across the same problem or has any advice on how to track down the problem? i would greatly appreciate your advise. thanks for your help!

very good site. have bookmarked it under "brilliant design examples". beautiful.

a very positive review from a guy who knows what he is talking about. pro pw: high performance even with large scale sites active and friendly community future safe good for commercial websites with the need to manage and display a lot of data (example scyscraper profile) highly flexible and powerful core, no plugins required contra pw: no asset/media management

hi wishbone, the german word for string is "zeichenkette", that is, every number of letters and numbers that are echoed as pure text to your code. for example, numbers that are echoed as string can't be used for doing any math anymore because they are part of a string, a "zeichenkette". does that help?

off topic, but worth mentioning: ProCache supports the head developer. Template caching does not.

Unfortunately there is no easy answer on how to give something back for such a brilliant piece of open source software. To be honest, though I don't know the context in which Ryan that this about donations, I can understand his position. Receiving donations is something completely different compared to getting paid for your hard work ... I'm benefiting commercially from PW and my clients do as well (I always point this out by the way when it comes to price discussions - most clients don't waste thoughts on where the software is coming from and why it is free for them. They think it's "just there".). So, if it comes to forms I make form builder module mandatory and currently I'm thinking about making cache module mandatory with every new project too. But this will hardly be enough for Ryan to make a living from. Hmm, could we make a foundation, that lives from donations and that acts as sponsor for new modules which are developed by Ryan? Say, everybody who uses PW commercially contributes with a certain percentage of the project budget to the foundation and the foundation in return pays Ryan a good price for new modules. Would this work? As I said, I have no final solution. But I can say that I would be willing to contribute with money. Whether it's by paying for modules or by becoming a contributor to the PW foundation.

I must agree to Soma. My live would be less happy without SFTP. Actually the integration of SASS is just perfect for my needs.

Rethinking the case I don't think that repeaters will give you what you want. They are simply not meant for that. I would rather follow diogos advice.

Hi Uliverse, I'm a long time Contao user too and I'm afraid you can't mimic the same behavior as in Contao. The above described ways are workarounds but not the same. In PW you have to be much more clear about your article structure from the very beginning. The advantage is that you have much more control over your markup. In Contao there are many if-than situations you can't foresee and thus not control. This applies mainly to site styling, e.g.a headline may be inserted inline or as a content element resulting in two different markup situations. Give PW a try. It is much more flexible in its own way than Contao. EDIT: This is possible, but repeaters are sticked as "fields" to their template. Let's say you'll have three different kinds of repeaters each of which with another order of fields or different fieldtypes at all and you want your editor to be able to choose from each of the three options on any page. In this case you'll have to attach all three repeaters to any template edtiors may use. Anyway, the described scenario is the one that comes closest to Contao. At least, as far as my understanding reaches.

i think: wow! (and feel like an idiot because i didn't buy those google shares back in the early 2000 years ...).