diogo

Hi guys, As some of you know I'm part of the Milktop team, but strategically we decided to go back to the format we had one year ago and recover ED Design, my collaboration with Erika. Today we are launching our website. http://ed-works.com/ This is a soft launch only for the PW community because I trust that this is the best place possible to have a site tested I hope soon I can write a case study. Hope you guys like it! (still some work to be done concerning SEO and accessibility)

Ok, last one on this, but just so you guys know about the kind of journalistic quality we are dealing with in that blog post, this is the thumbnail that was used to illustrate it: http://wptavern.com/tag/processwire

MS Word it's actually a great software if you actually learn how to use it well and take it to it's full potencial (I extend that to Open and Libre Office)

I completely agree with these 3 comments. From a graphic designer point of view, it's like comparing inDesign and MS Word, you can, but for that you really have to focus on the audience. Might be a big temptation to try to please everyone, but PW would start suffering from the same problems that others do. I'm glad Ryan doesn't think like that, and we can be sure that PW will only get better. edit: try to spend 30 minutes working with inDesign without knowing anything about professional publishing systems and see how frustrated you will get.

As I told you before, you did wrong but well, whatever... it's an empty discussion and I doubt it will get richer than this. Maybe others will have the patience to listen to what you say, and I hope they will. I don't.

Jeff, first of all, welcome to the forum. I'm the one that commented in a less respectful way from your point of view. I give you credit for actually trying PW before commenting, I've seen others that didn't even do that before emitting an opinion, but I just don't think that's enough. Just think of how you assumed that one didn't even read the post to the end only because one didn't write an extensive and paternal comment (no pun intended Joss, your comment is great), or that one thinks you're taking crap on the project only because one didn't agree with you. The truth is that you didn't only document your 30 minute journey, but you had an ostensively negative tone against PW and against Mike's article that was 1000 times more careful, more scientific and more neutral than your own. edit: I also give credit to the fact that you're here. Don't take the above as an offence or something similar.

You're welcome Cramer

It was a good great comment Joss!!

Oh man... http://wptavern.com/if-i-switched-publishing-systems-processwire-wouldnt-be-my-first-choice

Welcome to the forum! I've never done anything similar so I'm probably not the best to give advice. But in my understanding, if you will have to write custom code anyway, pw would be a perfect fit, at least as much as any other framework because it will give you all the flexibility while providing some great time savers. If you need something that pw doesn't have but you find on another framework or library you can always integrate it. We usually advice people to look for out-of-the-box solutions when they want to do this kind of large projects without wanting to write most of the code themselves but that doesn't seem to be your case. For what you wrote I suspect you will have fun with pw.

A "?" is missing in <?php

You can always make those images responsive. Thanks to Horst, PWs native images sizer provides images with much more quality than before. It's really easy to create responsive images with JS or even with the new SRCSET attribute for images or the <picture> element and respective polyfills http://scottjehl.github.io/picturefill/#examples It's great that you give the option to collapse the menu to show the images in bigger, but I think the wording could be better: I don't really want to "collapse the menu", what I really want is to see the content in bigger. What I mean is that the wording could be something like "enlarge content" and turning it into "show menu" as you already have there. I also think that this ability should only be present in the gallery pages as there's no point on seeing the blog or the copyright notice in larger. Just a suggestion

You can use Hanna code to replace shortcodes by html tags, or even create a formatter that turns something like (----------) in a closing and opening div. I suspect that Ryan's new Pagination Textformatter could also be a good fit for you, but I'm not sure what it does exactly yet http://modules.processwire.com/modules/textformatter-pagination/ As for me, I prefer the template way whenever I can.

I hope you pass by Portugal on the way

There was the need for more moderators because of a wave of spam that happened last week, but someone got too carried away with the bells and whistles That's the way to go

Only in this thread Joss went already from 1853 to 1855 Distinguished has to do with the access to the payed modules forum.

If you want to write raw html, you can even use ACE http://modules.processwire.com/modules/inputfield-ace-editor/

The simple solutions are always the best And that's exactly what I did before in other projects Edit: Just a short explanation, as this was also the sort of my confusion. This solution only works because the stylesheet as precedence over the "height" attribute, if the RTE would be outputting style="height:400px" instead (like it happens sometimes), it would have precedence over the Stylesheet, and "height:auto" wouldn't work.

In this particular case I'm not interested in resizing the images inside the editor, would be even nice not to have that option there. Is it that uncommon to prefer this over giving that option? We could have the option on the field settings of not allowing the resize, and in that case the image tag doesn't need the height there. Until then, I will continue to use the module.

I hope there is a way to it in the RTEs themselves. Would prefer that than the stupid work of removing them in PHP for sure. But I googled it and didn't find anything for CKEditor. The module was a quick fix for my particular problem.

Good point Martijn! I solved that problem by finding the images, and only then removing the attribute. To make it easier I'm using PHP's native Dom parser instead of regular expressions: $dom = new DOMDocument(); $dom->loadHTML(mb_convert_encoding($str, 'HTML-ENTITIES', 'UTF-8')); $images = $dom->getElementsByTagName('img'); foreach ($images as $image) { $image->removeAttribute('height'); } $str = $dom->saveHTML(); Beautiful, isn't it?

Hey guys! I was having some trouble with the RTEs adding the height attribute to images, because it was distorting all my images (I'm using max-width on the CSS), and decided to do something about it. So, here's a small Textformatter module that removes all the Height attributes from RTE fields where it's activated. https://github.com/ocorreiododiogo/PW-removeHeights

Already done

I went ahead and removed the affiliate links and altered the first one to a regular link to the digitalocean homepage. Sorry @goro2, I would prefer to be welcoming you for the first post, but nothing on it tells us that you will stick around in the forum after dropping the link here.

Eheh, I give an example for my second suggestion on that thread, thanks Adrian http://modules.processwire.com/authors/adrian/