Soma

You know what? I also wrote a review on OSCMS 5-6 days ago. I also went a few times in the past to this site to look for cms's, but haven't really payed attention to the ratings as it seemed to be unserious... seriously just looking at this dead ugly unserious website, fucked up by far too many ads... I've spent too much time with online votings in the past when creating custom content for games, there was contant fights for years going on on star ratings. So what. I think star ratings aren't really what should be chosen anyway. I tend to think, simple "like" buttons are better, and only for registered user. Back to topic: I discovered PW through an "Best CMS" online poll/voting I went coming from an tweet by modx community. Somebody mentioned PW in the comments with only: "ProcessWire, like modx done right.". This caught my attention. After reading "jquery inspired" and watching the video and what it's all about I was hooked in a matter of minutes, didn't even try out the demo, just started installing and playing around. I was amazed by how simple and powerful the API was and the general approach seemed to makes all sense. I was literally thinking "Finally the CMS I was looking/wishing for since a long time appeared! It's a dream come true". Also reading through all the threads in the forums I was only confirming, that there's the right mood and philosophy towards what it should be and where it should go. Simply love PW! Can't thank Ryan enough for sharing his work, AND providing amazing support and love for the people using PW. EDIT: Yes I found the concept of the weightlifter/ballerina so funny I couldn't stop laughing. It made my day/week!

FORMMAILER You're right. I also read that "note" but haven't really gave it attention until recently. I tried it out and it parses the content.css, you can include in TinyMCE, for html tag selectors. To get it working, classes should be defined like "ul.small-list{} ul.small-list li {}". Only downside I have figured yet with using bramus_cssextras is that it doesn't seem to allow me specify child::parent setups and at the same time have a child::self on the same selector. Like I wanted to give selected images inside an anchor link a class ".fancybox", but only on the anchor and not the image itself. This can be done using img::a[fancybox]; – But now also wanting to specify classes to the image itself with img::self[align_left,align_right]; will overwrite, cause when selecting the image in a link doesn't select the anchor. You can actually use the node path on status bar of tinymce to select the anchor tag, but that's too cumbersome for clients to use it that way. I solved it by having both a.fancybox and img.fancybox, and init fancybox looking for images and a's.

Great Picture! Happy birthday Ryan! Wish you all the best for the future, stay healthy and enjoy life with your family! Soma

Sorry couldn't resist ;D

hehe, could be. I'm mostly using "collapse if empty" option on most fields, which is a really nice feature. I think having some fields unused will not make much of a difference. I remember Ryans example site, he uses also a sidebar field, if empty it will look the parent up for the next filled sidebar and outputs it. I use that concept for background images on each page where it is used quiet prominent. In the same template I also have an optional iframe url field and pdf download references that can be set and will output after bodytext content. And even more, if children of a special accordion template is found same php will generate a accordion of them. If the layout, pagetype design concept is simple enough this works pretty well and can be extended quiet well using only one template in pw and one php file. From there I can still split up or create a more restrictive template if really needed. Just sharing how I currently work on a site in PW cause it makes me happy. And I really liked to see what others come up with. Different requirements of a website need different setups, and it's always up to the one building it or using it.

I also have only 1 template. For me it doesn't really matter having those stay empty on other language pages.

I'm currently working on a rather big/complex site with multiple languages. I created different language paths in the root. /de/ & /ch-en/, /fr/ & /fr-en/. Actually those are two different domains at the end. I solved the language switch link with having a page reference field. But there I'm doing only a one-sided reference from /de/ to a page in /ch-en/. From the english page, when loaded I do a back trace check for a page reference that links to the current page. But I didn't know that page references are loaded when saving. Anyway, is there any drawback in doing it like this or would there be any better solution to having language pages linked? Also regarding doing a back trace, which neccessarely need to go through all other language pages, is there any drawback or performance issue when having 1000's of pages? There will be only around 100 Pages in each language trees. I know, I'll do more filtering regarding the templates to limit the find, but limit doesn't work here. Here's my current code for the language link. Will be more complex ones all language trees are in place, also this solution wouldn't work as easy when having more than 2 languages. <?php // if a page is selected in the language_page field if($page->language_page_en){ echo "\n\t<li><a href='{$page->language_page_en->url}'>English</a></li> | "; } else{ // if page found with reference to current page $de = $pages->get("/de/")->find("language_page_en=$page")->first(); if($de) echo "\n\t<li><a href='{$de->url}'>Deutsch</a></li> | "; } (Edit: updated my code example, cause first one wasnt optimized.) I'm still working on building up the german pages, and only set up few english pages for testing. So this solution seemed the most easy and straight forward, and couldn't think of another solution. EDIT: Just thinking a little more, I think best would be on big sites to use markup cache? If having more than 2 language, I think possible would be to only have the "primary" language pages reference to all the other language pages, but having separate page reference field for each language. Then from the main language it would be easy to render the links, and from the other side there could be a back trace to the main language page and from there getting all the other references of other languages. Hope that all makes sense.

He did it again! ;D

When I create a user with and login, I can't see trash page. Not sure if this has was always like this, or something broke in my installations.

pretty good from here. ~110 processwire.com ~180 processwire.org ~25 my private host provider somewhere germany ~15 our host we use for projects zurich I think there's many good hosting providers in switzerland. http://nine.ch http://everyware.ch http://hostpoint.ch http://hoststar.ch

No need to encode sepcial chars if you're using utf-8.

Thanks Ryan for your response and talking about how things came to be in the context. I respect that and understand that your time is limited here and currently are focusing on other more important things. Don't take this personally or anything. I'm just expressing my experience without having any context of knowing how things came to be or what you're thoughts are on certain things. Sometimes these are really minor things. Regarding this Inputfields and the Page list tree functions and usability behaviors, I think everybody has different expectations how something should or shouldn't work and you've done an amazing job on this, but still as you said yourself there's always room to improve things. As for the Page reference field: I think this is one of the features which I really enjoy having in PW, and I'm using it a lot for different things. It's a really strong feature, very useful and flexible. I go as far as saying this very feature, is one why I finally chosen/love PW. I think I'm not the only one here. So I think if these page fieldtype/inputfields will become even stronger and get more love in the future it's will be awesome. I understand that it serves for what you and your client need/needed and having it to build on it, is such a great thing already. I would love to help you out on this, I would just start right now, but I fear my knowledge of the system is yet not enough. Some help and more time getting familiar with the core would be neccessary. Instead of saying "I want this or that is not good" I would get my hands dirty with this and help improve it. Thanks Ryan again, for this amazing CMS/CMF.

Aah, thanks Ryan I didn't know, that makes sense. I don't know a way around that problem with enter. I just know it can be really tedious to implement such things cross browser.

I just noticed that custom modules are displayed bold, while core modules are normal. When did you implement that? That's really nice, as I thought it would be nice to somehow make it clearer to see which are custom modules. Great!

While my co-worker is building pages for a website, I've came across a page that has name: "1.-title" How's this possible? I thought only a-z 0-9 dashes or underscores. I figured it's possible with space or number before ".".

BTW. Not sure if we already mentioned this. Will it be possible to have pages not being mapped?

hey lorgg great to hear you're working on it again. I think there's no reason to go delete a page manually in the trash? Just empty trash... ?

Aaaaaaah, but that's cumbersome. Why is it like this? Would it be possible to have a remove button beneath the add button?

I recently noticed, when using PageListSelect, and I select a page, how can I remove that again, so it's empty again?

Thanks Ryan, I think we been there already..., it would be really great to have "select" button not show on pages not having template specified. Since there's this option I wouldn't expect other pages to be selectable and disappear when saving, not even showing a message. It doesn't break anything, but is bad design in my opinion.

Yes, but I can't use another since I need the user to be able to browse the tree and with other inputfields this doesn't work the same. When using PageListSelect is the same issue. The select action appears on all.

I'm using PageListSelectMultiple

Yes I have a parent selected. And field setting is multiple. I can select all pages not just the ones using the template specified, but once saved they dissapear.

I've set up an page reference field to allow certain template to be selected. But I still can select other pages with other templates too. I think they shouldn't.

+1 ;D