SiNNuT

I think it's fine to require the header row, without it there will be no way to do Stap 2 in it's current form. If a header row is missing you can easily add it, because you have control over the file you choose to use.

stupid, i totally missed that

Nice job Pete. The module does what you want it to do but in i agree with Soma. When a site is in maintenance mode (or more general "unavailable") i don't want to forward all the site visitors to a login page. Maybe it can be a nice addition to have some of these kinds of settings and functionality in (a) PW core (module): site status => live, unavailable site unavailable message => "The site is currently unavailable" (this would only render the message) site unavailable page => choose a specific page from the tree (if defined this will render the set page, just like we have a 404 page) Personally i would welcome this, it is something you see in a lot of other webcms.

Looking great! Seems like a very useful module. Maybe even something to include by default, because most if not all projects i can think of require you to do some importing. I have made a reference to this thread/module over here: http://processwire.com/talk/index.php/topic,24.0.html Because my code reading skills suck i do have a question: In 'Step 2', how do you come up with the list of fields found in the csv? I'm guessing you need to have a header line in your csv file?

UPDATE Ryan has come up with a nice module which automates a lot of what is discussed in this thread, see: http://processwire.com/talk/index.php/topic,432.msg2937.html#msg2937 EDIT: corrected the link (went to right topic but wrong message) -apeisa

Nice site. When viewing the source i see this: <meta name="robots" content="noindex" /> <!-- remove before launch --> Also it wouldn't hurt to fill up your meta description tag. Meta keywords aren't used by any of the major search-engines, so i would probably remove them from my templates. Also i think there is an error in your canonical link entry (link rel instead of rev)

Pete, what you are describing sounds a bit like the Babel add-on for MODx Revolution. I haven't used it but it seems quite nice. http://rtfm.modx.com/display/ADDON/Babel And a tutorial on how to set things up, including some 'gateway' code, contexts etc. Of course no CMS works the same but it gives an impression: http://designfromwithin.com/995/modx-multilingual-setting-up-babel/ Something like that would be a nice way to go from the PW prototype described here: http://codeordie.posterous.com/multi-lingual-sites-with-the-processwire-cms

Every non-existing page under 'regions' gets a 404 page plus the correct status code. Every other non-existing page/url shows the homepage and status code 200 OK. This seems strange. Example: Request URL:http://villarental.com/test/test/ Request Method:GET Status Code:200 OK

Maybe you can also consider incorporating it in the PW .htaccess. # ---------------------------------------------------------------------- # Better website experience for IE users # ---------------------------------------------------------------------- # Force the latest IE version, in various cases when it may fall back to IE7 mode # github.com/rails/rails/commit/123eb25#commitcomment-118920 # Use ChromeFrame if it's installed for a better experience for the poor IE folk <IfModule mod_setenvif.c> <IfModule mod_headers.c> BrowserMatch MSIE ie Header set X-UA-Compatible "IE=Edge,chrome=1" env=ie </IfModule> </IfModule> <IfModule mod_headers.c> # Because X-UA-Compatible isn't sent to non-IE (to save header bytes), # We need to inform proxies that content changes based on UA Header append Vary User-Agent # Cache control is set only if mod_headers is enabled, so that's unnecessary to declare </IfModule> (taken from here: https://github.com/paulirish/html5-boilerplate/blob/master/.htaccess )

A little bit OT: In exploring the villarental site a bit i noticed that http://www.villarental.com/regions/ shows a blank page. The url isn't linked to on the site but some people may look at a url like http://www.villarental.com/regions/mexico/ and expect http://www.villarental.com/regions/ to show a listing of available regions or something like that. Also, http://www.villarental.com/regions/test/ shows a 404 page, where other non-existing pages just show (redirect to?) the homepage.

Ryan, i've just tested the site with IE8 (on WinXP Pro). I see no problems with the layout, it basically looks the same as in FF5 or Chrome, just without the border-radius, that u use a lot. Maybe you could ad some css3pie magic because IE8 still is used a lot.

Don't know if you've seen this: http://codeordie.posterous.com/multi-lingual-sites-with-the-processwire-cms I think this is a pretty good way of approaching multi-lang in the front-end.

Pretty nice write-up, and Processwire deserves it, that's for sure. Ryan, back in December i asked you if you could set up a forum. You replied: Now there are 2274 Posts in 330 Topics by 105 Members. Granted, a lot of them are from a few hardcore users, but i see a nice growth in numbers. Most seem to be pretty impressed with PW. With a little promoting i think it can become quite popular. Personally i am impressed that one developer made such a nice and clever CMS.

I think Ryan has build pretty big sites with PW, with lots of data, so i think it will scale well. Examples: http://www.tripsite.com/ and http://villarental.com/ There is pagination in the admin page tree. Log in to the skyscrapers demo site and take a look at the cities and architects pages. The pagination defaults at 50 items, plus there is a 'more' link that shows the next 50 items beneath the current 50 in one view. http://processwire.com/demo/ For really big numbers of pages it could be a good idea to have another way of viewing and selecting. Maybe a grid-like view or something based on functionality of the new search functions.

I'm not much of a coder, so i could be wrong, but I think you can make a module that runs custom code after each page save. A lot of things in PW are hookable. Page save is one of them. In the module i would check if the page i'm saving is of the news article type (i.e. using news_item template) If true, run your code after page save. See https://github.com/ryancramerdesign/P21/blob/master/site-default/modules/Helloworld.module for some inspiration. If what i'm saying is bs i 'm sure Ryan or a power user will come in and correct me.

As far as i can tell the page id isn't shown in the P21 admin area. I think it would be useful to do so. Sometimes you want to get pages by id. If you have db access you can look them up but this isn't necessarily the case for all people working on a site, and it's fields and templates. Let's say i want to show a couple of links to specific pages in my footer include. At the moment i know the urls but the pages could move around in the future, including changes in parent. To avoid possible dead links the best way is to get the pages by id right? Something like: <a href="<?=$pages->get(1)->url?>">FAQ</a> <a href="<?=$pages->get(2)->url?>">Contact</a> That way it is just set and forget, wherever you move your pages. If there is a better approach i would like your comments.

Agreed, nice and simple solution, on logout just redirect to the clean login view.

That would be fine as well and is a matter of taste to some extent. However, the main reason i made this post is the second screenshot: after a successful logout the bottom right text and links don't correspond to the logged out status. Unless there is some rational behind this behavior that i don't see i think this could be called a small bug or at least something that could be improved.

After being away for a while i just picked up a fresh copy of P21 from Github. Something i noticed when logging out in P21: username, profile-, and logout link are still visible after a successful logout . This seems rather illogical/confusing. Also, imo the wording of the continue link should make clear where it leads. Maybe something like: "Continue to public site or log back in".

Not sure if it fails, because i don't know the way it is supposed to work. It saves a cache file on first page visit. No matter if you update the page later on , the cache file stays the same (i guess until the set cache time is expired). Would be nice if it is aware of changes. On update a page with certain id, delete the associated cache file.

I'm working on a site in Processwire that has a lot of pages that don't change frequently. Although they seem to render fast enough without caching it seems optimal to cache these pages. Enabling caching works fine, but whenever i update a page the cached version doesn't get deleted. I could delete the cached file manually but this isn't really an option when a client eventually administers the site. I don't know how caching is implemented but would it be possible to have some sort of 'on update delete cached file' functionality?