Soma

I agree. If you see the page beeing edited by name/email it would be possible to ask the person to close it. In general there's rare cases where one would left it open. But having it still editable and just show a message isn't enough I guess. It would be like if you go on a water closet and there would be no lock, just a message at the door. Just have it fool-proof, so no worst case scenarios are possible at all. Versioning does help to get it fixed, I agree but still it should not rely on such things just cause it's possible. For me this would be all good and no problem, but you know how clients are that consider them big and important (cause they're trade market).

What would be needed / how expensive would it be to make it really lock? The other CMS we're working with does show a message and no edit screen. I think it's done via a flag, that get's set when editing and when leaving/closing browser. If only a message is shown the user doesn't really pay attention? If only having a message, it should be a really clear message or an js alert.

Is this possible yet? If I'm editing a page, it shouldn't be editable at the same time by another user, instead show a message. This is a really must have feature not onyl for the project I'm working for a big client. Clients always ask for such things straight away.

How can I give a user access to a custom process admin page I created in /admin/ ? Without giving them superuser?

I tried your code with and without includes, but I still can't reproduce this. Sorry, but don't know what could produce this other than something in your install or settings on page level. It doesn't make sense, that it would work differently without than with includes. Maybe someone else got an idea.

I'm not sure anybody can help without seeing the whole code. I have various sites now with multiple includes with and without navigation code and I never experienced something like this.

Sorry I can't spot any changed in the order when browsing thru your site... ? But maybe I'm still looking at the wrong. Normally you don't have to set sort selector if not custom order is set in children. Edit: Ah Now I've experienced what you telling on subnav left side. Edit: There's must be something else involved, cause I can't reproduce this using your code 1:1 on PW example Site.

Not getting what exactly happens, are they random? Do you happen to have set a sorting in children tabs sort setting?

Actually that what I thought and experienced with behaviours of co-workers. I actually modified my Teflon admin theme some times ago to make it not a tab visually. Ohh, great new theme we have here. Nice work nikola! Thanks for sharing.

Thanks a lot Ryan for the useful tips. Trying to extend the config after init, I missed the one it could easily be done before load (shouldn't try these things late at night ). I'll reconsider my approaches.

How comes I don't see any new commit?

Ok I went through this trying ways to implement something to extend core tinyMCE via module. At the end I think it would make the most sense, to make it extendable, customized from outside the core using a module, so that one can add custom editor css and plugins to his needs without touching the core. I got some issues getting this to work completely, wether with extending InputfieldTinyMCE nor with simple hook. There's problems (with js hook) to not have ways to configure per tinyMCE field in PW backend and also got problems to re-init the tinyMCE after extending the config. And on the other hand (by extending InputfieldTinyMCE) having the possibility to add more config fields to backend, but can't get it to output the additional js config straight, as it seems to get mixed up with the parent Inputfield config and only bad hacks would solve it. I'm not even sure if this would be possible or make sense to extend Inputfields in this case. No it doesn't, there wouldn't be ways extend, since it creates a new "Inputfield" type. So by extending the InputfieldTinyMCE, I would also problems when wanting to extend it further with custom plugins. So I'm not happy with it either way. So my conclusion kinda is: Most "sense" would make to have a tinyMCE located in the site modules folder? Not sure. Or should it really be all done in the core?

Yeah ,I know there's a little twist, but it's hard to visualize yours 100% . It is sure spot on and lit a spark in my brain... sorry if it did offend anyone. Well, to put it in Ryans metaphor terms, it should be anyway be called Skyscraper in the body of a Chalet.

Awesome! Can't wait to see it

I set up a field with .mp3 files to upload. I've set it to "required" in field input settings. But if I create a new page and save it without uploading a file, there's no error message shown. Bug, or am I doing something wrong?

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