apeisa

Forget to say: absolutely brilliant module Ryan. Very friendly UI and it was breeze to use!

I went ahead and tested this. I didn't modify anything and it imported dates just fine. This was my test CSV (I just pasted it): "title","body","date","images" "Uusi uutinen","Tämä on leipäteksti, jossa on "lainaus".","12-06-2011 12:45:11","http://www.avoine.fi/@Bin/213898/ulkona1.jpeg" Only strange this was that body text was in this format in tinyMCE field: Tämä on leipäteksti, jossa on lainaus"." Not sure if they should be escaped in csv?

Thanks Ryan. I don't have csv yet, but I am telling the client in which format the date's should be. I will test this at beginning of January, but it seems like it should be work or with very trivial work.

Thanks for the feedback guys. As you know this is very early version and there is no stock for product or anything like product variations. I have thought about variations, and I see there two ways of doing it. One is in template level, using subpages as variables (or page references like Spoetnik mentions, but I think subpages will be better fit). You could have two templates, "product" and "product-variation", where product variation is always children of product. This is something that could be easy to do with the current release of shop module. Other (and probably much better way) is to build custom fieldtype for price field. It would be fieldtype that would hold variations, price and stock. You could add 1-n variations and give them each unique price and stock. If we continue our t-shirt example, then I would create unique product for each different colors and then add different sizes as variations. This is something that I am interested to build, but if we don't have project for that at our work, then it doesn't have any kind of schedule. That is the current situation.

I will need to import bunch of news items soon, and planning to use this for the job. Any clues how to get date field working Ryan? It would be pretty trivial to write custom import script also, but I have looking for opportunity to test this module.

If your post can belong only to one category and your categories are considered static, then I don't see anything wrong in your approach - it is probably little bit easier for editor. But if you have situation where categories may change, then I would use category as a field instead of having it as parent page.

One way to do categories is to have them as page fields. That way your urls would be something like this: www.site.com/blog/name-of-the-article/ instead of: www.site.com/blog/categoryname/name-of-the-article/ Not sure which way is better in your case, but I usually prefer the first one most. It is bad thing to change urls, but there might be some heavy restructuring if you change all your category names (something you should definitely avoid though). If you have first url schema, then you don't break any links and they are all pretty much "permalinks". And doing this way you will use urlSegments to get pages like: www.site.com/blog/categoryname/ or www.site.com/blog/2011/ or www.site.com/blog/2011/11/ etc..

You find my current progress as an attachment. This is very alpha stuff, but you can play with it if you want. Not looking for feedback yet, since this is so early stuff, but soon I will. Installation is pretty simple: Unzip all files to /site/modules/Shop/ -folder Go to admin, modules and check for new modules. Install Shop-module (it will install all others) Installing created bunch of new fields. Only one that is important is sc_price. Edit one of your templates (usually "product", but can be anything - if you are installing this on demo-profile, then use basic-page) and add sc_price field to your template. Then edit corresponding template file (ie. basic-page.php) and add this line somewhere: echo $modules->get("Shop")->renderAddToCart($page); Create new template file called sc-checkout and make sure it has this line: echo $modules->get("Shop")->renderCheckout(); Edit your content and add some prices to your products. Then you can add those to shopping cart and create orders. Check out the Shop page on your admin, where you can manage your orders. Shop2.zip

I am building one at my job. Hopefully get something solid enough to be released at January or February. I don't have need for product variants, but it will contain cart, order management, different payment methods etc. My focus is in the backend since it is pretty trivial to build nice product listings with pw.

I would use page id also. Depending on your site structure, but name + template doesn't mean unique.

I have never realized how dumb that lion image actually looks, tongue flying out and sword through the head But I think strangest thing is why on earth each of these northern countries have lions on their coat of arms? We do have bears and elks, but no lions up here...

I don't think using negative margins is any more "dirtier" than anything else. It is a little bit harder to understand at first, but it does have a good browser support (even IE6 handles those). As we know there isn't any tools in css for layouts (not sure how the spec is coming at the moment though). We use just hacks. It used to be table hacks, now it is mostly floating div hacks.

My bad, I thought that body should have some background, but it was about those two sidebars. Glad you got it working, and great help Nico!

Position: relative is just fine, and you most probably do want to use it, if you need to use absolute positioning later on. Absolute positioning is very handy, works well on older browsers too, but it is not good for whole layout. Very common scenario is to have something like: HTML: <div id="header"> <h1>Logo</h1> <p id="slogan">This is on top right</p> </div> CSS: #header { position: relative; width: 80%; height: 140px; } #slogan { position: absolute; top: 20px; right: 20px; } Jasper: I don't find any differences between old and new - I don't see any background images on neither, only that dark turquoise background.

Ah, your whole site is absolutely positioned, since you have set #contentBackground position: absolute; And if you use absolute positioning, then the element is taken away from document flow. So it's parent height won't grow with it. You need to find a better way to handle your columns. Try starting with removing absolute positioning from #contentBackground.

Jasper, can you put that online somewhere? I'm sure there is an easy fix when I get to play with it online.

You could also value signed-in votes more than anonymous. Depends on the use case also.

Or are you after width(200)?

That is very usual for us (even that our in-house cms has nice "recover from trash" functionality). Of course it depends on cms used, what type of sites and clients. Our sites usually have 5-20 editors with very variable knowledge and it-skills, so accidents do happen.

Actually it would be great to allow clients to see and recover pages on trash, but not able to delete there. It will save bunch of support work, because accidental page delete won't require support call. Also there are cases when they do want to completely delete page, so when client deletes page from trash, then it could be set as hidden (so that superuses could still see and recover those).

I want to be sure to get the right page. I don't want to make any assumptions that there won't be admin pages with same name or that some of the names on path won't change (although this would be pretty edge case to be honest). Ryan: Thanks! I think that is well enough, no need to make changes because of this. I'll let you know if it doesn't work.

Nice idea! This would be nice way to share templates and their fields. Actually this reminds me how Perch works: http://grabaperch.com/. I think only problem here is that PW doesn't have write privileges there, so it cannot replace those comments with php. Not sure if there is any way around it.

You actually need page there when looking for page values. Good to know is that you can also put PageArray there. So you could something like this to return all : <?php $positiveAnswers = $pages->find("name~=yes"); $questionnaires = $pages->find("question=$positiveAnswers");

I have some problems to get selectors working. <?php // This works: $this->pages->get("template=admin,name=completed"); // This doesn't work: $psi = $this->modules->get('SettingItem'); $this->pages->get("template=admin,process=$psi,name=completed"); // Doesn't work: $this->pages->get("template=admin,process=SettingItem,name=completed"); I have admin page with process called "SettingItem" selected.

Maybe looking for something like this: <?php $answer = $pages->get(1234); $questionnaires = $pages->find("question=$answer"); This assumes that 1234 is the "SomeNumber" in your example, and question is the "Field". Probably easier version to maintain is to use paths: <?php $answer = $pages->get('/whois-father-of-luke-skywalker/anakin-skywalker/');