apeisa

If I remember correctly the input->whitelist is adding those get variables. So tweak your code so that $input->whitelist doesn't get set at all when empty values.

Have you defined thumbnails? Saving the field might also help.

WillyC examples always work, no doubts about his magic. Our need is actually little more difficult than that - it needs to check page access, accept only pages under certain section etc. So file timestamps would definitely be great help here.

I actually got this same error just today on one dev site. It has been running dev versions and when trying to change password it threw that error. I updated to latest dev and still same. But just for this one user, others and new ones work just fine.

Maybe implement two modules. One textformatter and another autoload module which looks for fields that have the certain textformatter.

I have need to sort files based on timestamp (when file was added). That would be easy enough within single page or file field. But I have to do it site wide. I need to find ten newest files from whole site. Since there is no timestamp on db level, I cannot query for this. Also looping through all the files is not an option. Is only way to create custom module with separate table (or new fieldtype)? Any hope to get timestamp supported on Pagefile? Or am I missing something obvious?

For remote editing I just use WinSCP (free + great) - you can set that in which editor it opens which extensions. Then you can use any editor you like. When saved WinSCP syncs the file right back to server. http://winscp.net/eng/download.php#download2

Doolak, you are trying to get thumb from Pageimages (bunch of images) instead of single image. Does this work: $page->mitglied_foto->first()->getThumb('thumbnail'); Or alternatively edit mitglied_foto field and set it to allow only one image (then it returns that single image in api instead of Pageimages).

Welcome aboard Jorge and thanks for the recommendations. No need to be nervous here

While I agree that there are differences between editors (I have found using a latest CKeditor a pleasant surprising), I don't think that settling with another editor will solve the fundamental problems. If we use just the basic features (text formatting, links) the tinyMce is just find. Replacing it with something that does those things only doesn't solve the problem, it just takes away features that someone might need in some projects. What I would like to see this discussion going is what kind of problems and solutions we have. In our projects we usually get away with very few tinyMce buttons (the more buttons, the more problems) - but the real pain points for us are: 1) image placement 2) tables (I think this is one area where CKeditor is much better - also area that many smaller editors just skip, or have very poor implementation like Aloha) For 1) problem there are sometimes nice solutions, like just using predefined image placements on template. I know that is something that Ryan uses a lot (like here: http://www.villarental.com/villas/17-the-harbour/). It works great when working with clear template (like "villa" here), but it fails when site has a lots of general content pages. What our old cms did and what newsletter editors seems to do now (like http://mailchimp.com/) is to have "mini templates" or "blocks" that keep the structure, instead of just having images and text mixed. That is nice way to do it - editors doesn't have to think about image sizes (that is pain currently), it is easy and safe on redesigns (image sizes are relational to column width) etc. For 2) problem sometimes repeaters can be used, sometimes textarea with text formatters and sometimes just good rte (ckeditor > tinymce in this regard) Very interested to hear what kind of problems people are having currently and what kind of solutions might help?

Check the console and network tab when using chrome. Track the ajax request and see what it is asking and getting responded.

My gut feeling is that it should be include everything but not unpublished pages. That is tricky question though.

Yeah, that is pretty common cause of frustration for mac fellows. If you would use it daily, you wouldn't notice updates. I have been using Win7 few years now (prettty much got it when it was released) and it is hard to find anything bad from it. Very solid OS in my opinion. I am too lazy to learn new tools, when all I need are browser, editor and local lamp.

I think that is the majority of web devs these days. Using virtual machines or tools like http://www.browserstack.com/ (highly recommended btw) to test different browsers.

One addition to the code Wanze provided: when using urlSegments it is highly recommended to throw 404 when urlSegment is invalid. So in that case: $home = true; if ($input->urlSegment1) { $category = $sanitizer->selectorValue($input->urlSegment1); $c = $pages->get("name={$category}"); if ($c->id) { echo $c->render(); $home = false; } else { throw new Wire404Exception(); } } if ($home) { //Do your homepage stuff... }

One way to solve that kind of problems is to use messaging queue, like http://www.rabbitmq.com/ or http://aws.amazon.com/sqs/. There are probably simpler solutions also, but that way you don't hit scaling problems.

Lauri, this might help: http://stackoverflow.com/questions/1676688/php-mysql-connection-not-working-2002-no-such-file-or-directory See also the comments on approved answer. PW uses mysqli.

My only gripe with current editors are image placement. Many times that cannot be avoided or predefined.

How about lightweight text editors? Or do you need some folding and pretty printing also? http://xml-copy-editor.sourceforge.net/ There seems to be good alternatives at least if you have windows available: http://stackoverflow.com/questions/308679/lightweight-xml-viewer-that-can-handle-large-files

Page field with PagelistSelectMultiple as inputfield is probably your best bet.

Oh, I have seen Zalando ads in TV here in Finland (they promote very heavily). The most annoying ones, like all german TV ads

Not sure I understand much of that, but try editing /site/config.php and setting: $config->sessionFingerprint = false;

There are one or two session security based settings on config.php that might help here.

Sorry, I misread your last post. I have been thinking about that a lot lately. I think that to get PW more popular "one click features" like blog, news, products etc are great idea. There are few things that slow down that road currently: Export and import of templates & fields - that will be huge time saver when creating such a modules (if you take a look my shopping cart checkout module, there is quite a lot code just for field/template/page creation) Field duplication: should each feature bring their own fields, like blog_body or re-use existing ones? If the latter, then we might need to increase the amount of "default" fields. Maybe as simple as adding few more fields to starting profile.

You can choose those (and many others, like radios, checkboxes, pageListSelect or asmSelect) as a inputfield, when you have created Page field.