uliverse

Thanks! I will try.

Thanks for your explanation. Of course, it is always an option to keep the map and the address fields separate (your option 2), but it seemed to be a better user experience to combine the two. I did try to use the original Map Marker module by Ryan. But things have become so complicated with the Google API console and somehow I can't get it to work, the geocoding won't work any longer even though I have created an API code and all... Besides, I do like the Open Street Map idea. That's why I hoped to use the Leaflet module.

I would like to output the address field in the frontend. However the field contains too much information. It's automatically populated with address, road, city, state and country, sometimes even more. Is there a way to only get the basic address?

Hi guys, I have a peculiar issue: I am using a repeater which contains an image field. I can upload and then edit (crop, resize...) an image, but after saving the page once the editing function is no longer available. The crop icon completely disappears. Does anyone experience the same problem?

Hi... like Pete I have trouble putting images in PageTable to display in the frontend. How did you do it? Edit: Got it solved. It had to do with my syntax. Now it works without any problems.

OK. Thanks!

@quickjeff: I would be interested to know if and how you were able to implement paid memberships.

Interesting read, I think that is well expressed. That's why it is even more important to "force" the non-technical users to build semantic content rather than only "nice to look at" content. That could be achieved by providing blocks (or whatever) that produce clean markup in the background. So far I have never seen a CMS that has really gone all the length in that respect. For text heavy sites/pages styling via template might work well, but it does not work for campaign websites. Those tend to not only consist of a bunch of <p>'s <h1>'s and a few <ul>'s – because they DO have to look good and not just convey information that can be automatically styled. So you are left with either a lot of manual coding work or terrible markup. I agree with the author – it's time to re-think how CMSs work with content layout. Even though the web has dramatically changed over the past 10 years, the way content is put into most CMS (at least the ones I know) basically has not changed at all and is still inspired by word processors. Maybe a CMS is just not the right tool to build a certain kind of website – but we just use them for lack of better options and try to force something in there that shouldn't be there at all. The more creative and individual the design the less automatic processing is possible (because you need the human factor for creativity). That's where animals like Mailchimp and Weebly and other web builders fit in. But I am not aware of any serious open source CMS that takes such a drag and drop approach. But we are actually mixing two discussions here. Maybe this threat should be split into the extension that Soma is working on and the fundamental discussion about content layout and styling in the CMS of the future...

Thanks for all your comments! I agree that content blocks make it harder to migrate content to other systems. And if an author doesn't understand the basic intentions of the designer - I see that point, too - the freedom to quickly click together anything that looks cool doesn't help produce consistency. Besides those blocks even add lots of additional markup that somebody has named "DIVeritis". Still I have experienced over and over again how quickly I can achieve exactly the design I intend for a particular page with having those content blocks at my disposal. There are very few limits. In the end I guess it boils down to two paradigms: a consitent, predictable look or creative freedom. Whatever works better in a particular case should be the method of choice. That's why I had asked in the first place, to find out how PW users approach this issue. Maybe the discussion also depends on if you ask developers or designers. I have come so much used to working with blocks that it is hard for me to think of a workflow without them...

That would technicaly work and provide a good level of flexibility. I wonder how the average editor would come to terms with it, though. Thinking of it diogo's solution might really be the best way to imitate the "content element model". That's what I was guessing, too. I read somewhere that repeaters are not the best in terms of performance either.Hanna code looks very powerful indeed. Definitely something to check out! Would be great to have a non-cryptic implementation for the technically challenged end users. Like a drag and drop way... That's beyond my modest skills, though... I will definitely give PW a try if I have a project that fits. There are scenarios where Contao doesn't give you the powerful tools to enter and retrieve data in a very streamlined and customized way (out of the box at least, there are extensions though that do exactly that.) That's where PW seems to really shine. It does seem to come at the cost that the resulting pages should be highly standardized and follow a pre-defined "cookie cutter design" (well, that's what a template really is) - or much tweaking and workarounds are necessary. At least that's my impression so far. After all PW is meant to be a CMS not a site builder, I understand that.

Maybe I should be more specific with my original post. Just to clarify: I don't have to replicate Contao's behaviour. That's just one efficient way that I know. I am trying to find out how you guys avoid using Rich Text editors for content styling. I think you agree with me that RTEs are not the prime choice due to the messy markup they tend to produce and because authors have too many possibilities to create a mess. So - how do you do it in PW?

Thanks for the replies. I think repeater fields would come the closest to what I am looking for. Everything else still forces the output in a predefined order. But is it possible to repeat a group of fields with repeaters ( for example a group made up of heading, textarea, image, accordion, and whatever elements could be of use)? Then the author can use whatever field he needs, add another repeater and again choose what he needs and so on.

Hi, I am a mostly happy user of Contao which I have successfully used for many projects. What I like about Contao is the great flexibility when creating pages/articles - each article is pieced together with content elements (text, images, galleries, accordions, modules...) in any way I like. Typo3 works very similar I believe. Especially for marketing websites this is extremely useful because in that case pages tend to be styled and designed very individually. I have been "flirting" with PW now for some weeks but this is still my biggest question: can I achieve the same flexible design/layout approach for individual articles with PW as in Contao without having to create templates for each case? How can I p.e. have some text, then add an accordion, continue with text followed by a form and then add some images at the end - without pre-defining those elements in the template and frontend template? I understand I can do all this using plain HTML - but I can hardly expect that from clients. Maybe this is a very particular obstacle to overcome in my mind that only applies for users of Contao and Typo3 - other systems don't offer content elements either. I always wondered how those users get to individually designed pages...