Martijn Geerts

Yes, it's stores the amount of attemps the time of the last attempt and the name of the username. This prevents brute force attacks.

@LostKrobrakai, it's not a real big deal to develop in a sub folder and everything can be solved. I just prefer to drag'n'drop the development folder to the end location and import the SQL without additional steps.

Some posts about other CMS's are the result of frustration I guess. (I have a few) But we have this remarkable framework called ProcessWire. We all have to know that we will sparkle even more if we don't bash anything, we don't need it. Not 'bashing' will suit us better. +1

Welcome to the club Charles

There's one rule that rules them all: Be eager !

@LostKobrakai, are all url assets used in WYSIWYG fields abstracted by default ? So are they are converted at runtime to valid urls? I know there's a module that can do that, but is it now the default in ProcessWire ? And what about url used in javascript, stylesheets etc. It's just a good practice to make your dev environment the same as the real domain.

Maybe this: $page->rootParent or $page->closest($selector)

For the next time, it's better to avoid this. It'll save you extra unnecessary work.

@Vizz, i'm interested to see what ProcessWire work you did. Can you please post some links from sites you've build ?

In the template you search for POST, but on the form you don't post the value. $.ajax({ type: "POST", ... etc.

No problem.

+ the field names that make sense for the full 100%. +100% never calling customers, simply cause they are satisfied for the 100%.

Maybe this can be done with a cookie, store the width of the image in an array of templates. This way the image width settings can be different from each template.

The php date function needs a unix timestamp. $month = date("F", 1408946806); // here's the $page->date replaced with the value. echo $month; // outputs: Augustus

I'm not sure about that notices loop, if you didn't delete the install.php for example does that prevent your $session->redirect ?

I do think field errors are cleaned in the InputfieldWrapper render() methode. So maybe you need an additional hook before InutfieldWrapper render and loop through the fields and count the errors.

Sorry, but this question has nothing to do with ProcessWire. For Foundation support better go to Stack Overflow or some other Foundation support.

Something like this will work: <?php /** * On a page that loads the widgets * */ $widgets = $pages->find("parent=/widgets/"); foreach($widgets as $widget) { $widget->set('motherPage', $page); echo "<div class='widget {$widget->template->name}'>"; echo $widget->render(); echo "</div>"; } <?php /** * logic on a widget page * */ // The $page variable of the mother Page bound to $motherPage. $motherPage = $page->motherPage; // Throw 404 if a guest access the widget directly if(!$motherPage && !$user->isLoggedin()) throw new Wire404Exception(); echo $page->body;

I do think you know this, but ones all data is stored in PW pages, it's quite easy to loop them and update those pages (clean process). On every loop you do little steps. recent: In the dev there's now $sanitizer->purify this can be used for cleaning HTML.

not correct From the docs $options = array( 'quality' => 90, 'upscaling' => false, 'cropping' => 'southeast' ); $img = $image->size($x, $y, $options);

Little bit short in time lately. Please send me a personal message, so I won't forget this...

I would not recommend the one over the other. There are a lot of factors that will effect a decision. Time, money, experience in a 'search' technique, amount of traffic etc. etc. Build what makes sense for your position. And you don't need to choose, maybe you're better of with 2 types of search in your site.

@BernhardB, look at the following structure: vehicles | +-- Cars | | | +-- Coupe | | | +-- SUV | | | +-- Crossover | +-- Bikes | | | +-- City bike | | | +-- Comfort bike | | | +-- Trekking bike | +-- Boats | +-- Canoes | +-- Rafts | +-- Yachts‎ Say someone wants to search a SUV First <select> is Vehicles, that lists all vehicles: Cars, Bikes and Boats. When cars is selected, query all car type & present the user with a select with all types. When the user select a type, present the user with all found SUV's.

A highly categorised site is a different beast then a textual 'animal' site. So what advanced is depends a lot from the context of your site. For a big news portal (mainly textual), I used the google search api to search the site. This way all textual content is searched, even in PDF,s. The results I get back from google (json) I store for 1 hour with markupCache to reduce requests to google. I use the urls from the results to get back to the page Objects. This way I let google do the search and ProcessWire the presentation of the results. ( showing thumbnails etc, headlines descriptions etc. ) But if you have a site with a lot of categories, highly structural. I could imagine you build a chain of selectboxes. This search is a Perfect fit for ProcessWire.

@pwired, I was talkin about the cookies in the slider, yum yum... But yeah I could see the page & it loads quickly !