apeisa

1. yes 2. yes and no

Since I found ProcessWire, I have been huge fan of different Villa sites (all build with ProcessWire). This one is my new favourite, brilliant work Ryan! Amazing how fast the site is, even from this side of Atlantic and with all those huge images. ProCache, PW, AIOM, server and good image optimizations all doing their magic I suppose.

Haha, that would definitely save my time too

I think how you are using the redirects module is still more like a url shortener than why this module exists (keeping urls form old site alive and also permanent shortcuts to most important stuff, like /board/ => /about_us/people/board/). Have you thought about creating a template called "redirect" and adding two fields for it: redirect_url & description. Template code would be: $session->redirect($page->redirect_url); You could use that method for your "non permanent" needs and keep redirects module for urls that need to live "forever".

Clever stuff arjen and nice example about PW flexibility.

I think best would be single repo per language and each module as a subdir.

Uh. You guys seem to live in different world than I do I mean I don't remember ever removed redirects. They are permanent you know. How about others? This would be minor addition, but not keen on adding features I don't need (unless everyone else needs it).

hmm. not sure I fully understand the value for it...? In my use it would always be "url from old site" or "marketing shortcut" and both of those are pretty obvious. What kind of information you would store there?

Yes, they can. Actually the exact case what you described is absolutely best use cases for repeaters. Having only few fields (and mainly page fields) keep repeater UI simple and end result is very powerful. I just build something very similar, works great.

Here you can find latest dev: https://github.com/ryancramerdesign/ProcessWire/archive/dev.zip

$user->language->name

No, not at the moment at least. Hmm, haven't thought about that. I just glanced the code and it shouldn't be much to get that working. I actually wonder why it doesn't - maybe the added cropping link is messing things or some init() is missing. Does it throw any errors on js console?

Thanks for the PR soma! I think those are good to go. Although I think price support in repeaters/variations probably mean that I need to update my payment modules to support that instead of direct price. Agreed about using API to generate markup. Actually, now when thinking about it more, payments should be ok already, since they are using order-items instead of products, so you have taken care of that already.

This is fun horst, thanks for building it. This clearly shows the alarming trend about those damn youngsters like Teppo, Nik and Wanze who come and post few silly posts with cool emoticons that everyone just likes... I believe in hard facts like member id, alphabets of member name, number of posts, number of likes and hotness of avatar.

http://www.martanpuoti.fi

Well, Paypal has tons of different APIs and ways of doing things. This one works like this: 1. Send regular form data to https://www.paypal.com/cgi-bin/webscr 2A. User pays (using paypal or using credit card through paypal - no need to login in that case) 2B. Or user cancels (then redirected to cancel url - it is different from success url) 3. After payment user returns to shop and their return is validated from paypal (that Paypal really has that kind of payment made) It is very simple actually and 100% tied to shopping cart. Recurring payments would need something different to handle recurring subscriptions etc.

Nope, nothing to do with subscriptions (just paying the shopping cart items through paypal). Regarding IPN check, it does verifies from Paypal that payment was made and came from Paypal. I will add more checks there though, at least will validate that order sum wasn't altered at any point.

I actually have build also payment module for https://www.maksuturva.fi/, but that is not for shopping cart, but more like general payment module for PW. Looking for a way to drop shop dependencies from payment modules - meaning that this paypal module would be usable without shopping cart too. It shouldn't be too hard though, just something I didn't plan when implemented payment methods for shopping cart.

Here you go: https://github.com/apeisa/PaymentPaypal-deprecated If you are trying to implement this one and not feeling lucky, just ask here. While developing this I played a lot with latest pw dev and shop modules. Everything worked just like they should - so I will move them out from alpha stage.

Ok, i just build paypal module, will release it soon after little testing. Will also test everything with shopping cart that alll work with latest PW.

Hi wilsea and welcome to the PW and forums. What kind of examples you are looking for? I found that there are decent amount of examples and guide like text on current docs, like selectors for example: http://processwire.com/api/selectors/

This code that I just wrote might help: // Lets clone the "mallitoimipiste" that has all the required pages $fc = $this->pages->clone($model); $fc->title = $this->input->post->name; $fc->name = $name; $fc->location->address = $this->input->post->address; $fc->removeStatus(Page::statusLocked); $fc->save(); // create role for this fitness-center $fcrole = $this->roles->add("fitness-center-" . $name); $fcrole->addPermission("page-view"); $fcrole->addPermission("page-edit"); $fcrole->addPermission("page-sort"); $fcrole->addPermission("profile-edit"); $fcrole->save(); // add template permissions for the new role in fitness-center template $fctemplate = $this->templates->get("fitness-center"); $addRoles = $fctemplate->get("addRoles"); $addRoles[] =$fcrole->id; $editRoles = $fctemplate->get("editRoles"); $editRoles[] =$fcrole->id; $createRoles = $fctemplate->get("createRoles"); $createRoles[] =$fcrole->id; $fctemplate->roles->add($fcrole); $fctemplate->set("addRoles", $addRoles); $fctemplate->set("editRoles", $editRoles); $fctemplate->set("createRoles", $createRoles); $fctemplate->save(); // add the current role as a edit_role for the page $fc->edit_roles->add($fcrole); $fc->save(); Not sure if that set("createRoles", $createRoles) is even required, probably works with ->add just like "roles" does.

We will put up http://fi.processwire.com site like there are http://de.processwire.com and http://it.processwire.com. If you want your company or yourself portrayed on that page, please provide image and link here on this topic. We also have processwire.fi domain, that we will simply redirect to fi.processwire.com when everything is ready.

Ryan - any ideas how much work that would be? We have need for this also in next project, so interested in providing some support (=money) for this.

Thanks for the pr Teppo, just merged it!