apeisa

Direct database access is just a PDO, nothing special there.

Thanks, I committed that change to github also.

yellowled: what if you change this https://github.com/apeisa/ProcessRedirects/blob/master/ProcessRedirects.module#L94 from InputfieldURL to InputfieldText - does everything work ok after that?

Also make sure that /site/assets/sessions/ dir is writeable.

This looks great. Steve: modules need to be named with certain convention or either be autoload to be able to extend this?

Pete, Linode is UK and has managed also.

I think it's because that method is probably fired in another request (file uploads are ajax). Try writing $log instead of message.

I think most of us do that, at least sometimes. But there are no things in coding I hate more than trying to figure out where does lonely } starts. Well, there is. Add few more ifs inside each others, and the soup is ready. When you have huge chunks of html, maybe few intended ifs and then some lonely <?php } ?> or <?php endif; ?>, you are far from readable and easily manageable code. So my preference is actually: you should have so little logic on your markup generation, that echoing the parts that go inside ifs is good (usually oneliners). When having bigger chunks, then you should have other means: using functions, includes, some object or moving more logic to controller (or using actual controller). // with little html, echoing is much cleaner (imo) if($foo == $bar) { echo "<p>Show this text and this $variable</p>"; } else { echo "<p>Show this text instead with this $otherVariable</p>"; } // functions if($foo == $bar) { echo renderStuff1(); } else { echo renderStuff2(); } // includes if($foo == $bar) { include(./markup/stuff1.inc); } else { include(./markup/stuff2.inc); } // object $markup = new Markup(); if($foo == $bar) { echo $markup->stuff1(); } else { echo $markup->stuff2(); }

It's ugly stuff that probably ends some if { from earlier.

Nope, not yet. I am pretty sure there will be documentation before 2.5 is released.

tobaco: nope, but you can use new PageTable for that (that's in core - dev branch). It will be much faster than repeater, since it doesn't have to load all the information to a single page.

Macrura: https://github.com/apeisa/PaymentPaypal

http://praegnanz.de/weblog/cms-einkaufsfuehrer-2014

I have never had such a need. Maybe with just some css? Pagelist has this kind of classes: PageListID1024 I have no idea though what would be best way to inject that kind of css to admin. Some examples probably on these forums. Simple autoload module would do at least.

Clever idea!

I think I am missing single git pull here

I think only real issue left is PageFiles permissions. They still follow the template access.

Users actually are pages in tree, so you already have what you need with page field and it's various inputfields.

It's possible to localize with language support. Just translate the file InputfieldDatetime.module (if I remember right) and there is option for translation (also affects the first day of the week).

I don't see any other way for files really. Maybe bundling multiple (meaning no other changes in between and max few minutes time) additions or removes into same revision. That could be done in UI only.

Welcome! Repeaters shouldn't be there, since they are hidden. Do you have include=hidden in selector also? Also do you really need the name in the selector?

Just a reminder: above module is only useful if sorting cannot be set based on some field or created date for example.

Huge release! Congratulations Teppo! I love the preview UI, very neat.

1. Possible, but not out of the box. Probably easier, when you don't use iFrame, but embed directly as html (see section 3.) 2. Not out of the box, but possible. 3. Yes. If you have need for multiple different kind (and often complex forms), then FormBuilder is gonna be huge help in your project. If registration form is always the same, you are probably better with custom form.

Not on computer, but I think you have to tell which product you are adding to cart. I would guess it assumes (without any params) that the current page is product. That's not the case here, since you are using repeaters. Try adding $item as a param to renderAddToCart method (or check source what it requires).