Martijn Geerts

Be aware of the div element has no special meaning at all. it's just a structural element to group elements that belong to each other. If those first 10 lines ( I think it's better to have a paragraph ) needs styling, it has a function within the context, say 'intro'. Then it's a good thing to have a separate textarea field for that as you know where to place it in the article. There are other meaning full blocks. Say you want to quote, you can use blockquoute etc. You can however manipulate the text output with js, textformatter or some custom PHP replace functions. But manipulating the raw text in a wysiwyg editor is a bad idea. If the customers wife really hates orange and tells blue or yellow, you've have to change all pages. $(function(){ $(".body p:first").addClass('standout'); // asuming that it's all wrapped in .body }); .standout { do your styles here. }

Using MYSQL with php is not part of the starters lessons PHP. First its time to understand the basics. What are types, variables, operators, control structures functions etc. etc. This basic knowledge is enough to get start with ProcessWire. For the MYSQL + PHP only way, the second lessons for PHP starts & you have to subscribe to the starters lessons for MYSQL. side note: Take the multi lessons hard way, over the easier step in to ProcessWire. This knowledge will make the difference from 'can make a website' to 'to be a developer'. Comparing only getting 1 field from SQL to ProcessWire is not fair. On the time you get 1 field out of SQL with PHP, ProcessWire has take care of all the stuff thats needed to be a fully functional CMF/CMS and given you back the field data needed. ProcessWire takes care of an awful lot of logic. But on the end it's the developer who decide. There's the framework part of PW. ProcessWire is build with PHP and done very well. The simplicity to access data with ProcessWire is unique. Never seen this simple way anywhere. What you decide is up to you but the multi lessons hard way will come in handy !

As you find out, can't speak it. But everytime when I arrive on Suvarnabhumi and I feel at home.

Found a little typo on "/site/modules/InputfieldCKEditor/ckeditor-4.3.0/plugins/pwlink/plugin.js" line 70 Which prevent popup the modal for the link. - var modalUri = config.urls.admin + 'page/link/?id=' + page_id + '&modal=1' + lang_id; + // typo's fixed below + var modalUrl = config.urls.admin + 'page/link/?id=' + pageID + '&modal=1' + lang_id;

Oké Arjan, I continued the conversation here. @ Soma, I saw you're thinking the same. (sorry, unnessesary post :-( )

I have this situation: I have users with a role 'partner', They have a folder in the tree where they have they have custom rights. ( based on PageEditPerUser). Now when I unpublish their "HOME" folder, I wish to prohibit access to the admin for all 'partners' who have custom access to that folder. It's working, but there's no visual feedback. (no strike-through)

Unpublishing a user from the API side is easily done with addStatus(Page::statusUnpublished). And it nicely prohibit access to the admin. But there's no way I can see in the admin that the user is unpublished. What do you think guys, is giving visual feedback for unpublished users in /processwire/access/users/ a good idea ?

Just a few words I love Ko Lipe.

Chok Dee Krap ! (thai)

Welcome gebeer, There're some ProcessWire addicts over here, watch out, so you've been warned now! if(count($page->images)) { foreach($page->images as $img) { if($img->width > 600) { $config->styles->append('/path/to/popup.css'); $config->scripts->append('/path/to/popup.js'); break; } } }

Sorry, I forgot to say Welcome !

I'm not shure I understand the question. But if you want to retrieve data from an external ProcessWire site maybe you can use Pages Web Service.

I like that spirit Harmster

@Xeto: Screen height would matter ! At 480 rows, your screen should be at least 2.5 meters high. oké, seriously. all data is in the same table, so performance & scalability is good.

Browser cache ? Yesterday, couldn't save roles, after emptying the cache (several times) it was oké.

It's easily missed, didn't put it on the modules directory because it's really basic. It's more of a starting point. Mistreat it if you wish.

I think you're searching this.

For simple table rendering on the Front, you can use my repeater Table module. It's very simple, but works. And easy to change if wished.

Will see tonight if I have the time to debug. I'm not very handy with that git stuff. // start at line 160 if(in_array($data_key, array('editRoles', 'addRoles', 'createRoles', 'roles'))) { $array = $data_value; $data_value = ''; foreach ($array as $id) $data_value .= $this->pages->get((int)$id)->name . ', '; $data_value = rtrim($data_value, ', '); } $settings_str .= "<span>$data_key:</span> $data_value<br/>";

@adrian, yep same here, for now I just 'fixed' this local.

As a side note: I use English for my system and all my programs, no exception. But when I visit a site I'll read dutch. A turkish developer in Germany with a turkish system, would he want to use English, German or Turkush ? Making assumptions from collected language info is in my opinion not the way to go. The only way you can play nice using the domain name, as the user has 'chosen' for the language. ( sort of )

It's hackish, but something may work. When you select the first select, trigger a click on the save button with javascript ( needs a module ) Then after page save, the other select ( type of page ) uses the data from the first select to query the 'sub' pages Show the second select only when the first one is not empty with field dependencies. Forget this, this is not very thoughtful.

Keep up the 60fs

Only available in de dev.

I like this approach from the admin edit side. Thank for posting this one Diogo ! One drawback is with search facilities for of the page. For the frontend, it's quit good doable, But don't know how to handle it with the Admin Ajax Search.