Leaderboard

I just updated the cheat-sheet to avoid confusion. Thanks! They're always are cheating!

Welcome, Charliez Hehe. It seems like you are coming from MODx realm, right? You don't really need to do it in PW the way you did it in MODx. I think what you mayby need is pages serving as building blocks, so that you can choose what blocks you want to use on your page and then just call them to render themselves in your template. Maybe it sounds a little complicated at first, but it's really easy after you've wraped your head around PW's philosophy. And yeah, storing php in fields is evil

Nico create a blog module. I haven't tried it myself, but you could give it a try: http://processwire.c...__fromsearch__1 Processwire has built in user management with different user roles. Is that what you are looking for? jQuery for the backend is included. If you want to use jQuery on your frontend, you would simply call jQuery from your template. Why would you need this? I agree with SiNNuT that PHP should be in the templates, modules etc. As I see it (simplified but still...) fields can be populated from the admin by editors. Templates and modules are created by designers/coders. Would you really want to have editors writing php code? /Jasper

If you could be a bit more specific about where you are switching from and what you would like to achieve/make it would be easier to advise. PW is a very flexible tool with almost all of the building blocks to create great sites fast. I've seen people migrate from typo3, drupal, wordpress etc., so this is all within the realm of possibilities. If you haven't done so already i would just install PW a give it a spin. Play around with some templates, add a couple fields, do some page relations etc. Regarding your questions: - Not that i'm aware of. PW doesn't dictate how you setup and structure your sites. It's pretty easy to setup blog functionality though. However, if all you want to do is blog there are other systems available that are more geared towards out of the box. - Not sure - You want to use these plugins in the PW backend? - Haven't tried to input PHP code in fields myself, don't know if this is possible. It doesn't really sound like something you would want to do. In general i think this belongs in template files, modules etc.

url.segment configerable san /site/config.php - /** * Maximum number of extra stacked URL segments allowed in a page's URL (including page numbers). * * i.e. /path/to/page/s1/s2/s3 where s1, s2 and s3 are URL segments that don't resolve to a page, but can be * checked in the API via $input->urlSegment1, $input->urlSegment2, $input->urlSegment3, etc. * To use this, your template settings (under the URL tab) must take advantage of it. Only change this * number if you need more (or fewer) URL segments for some reason. * */ $config->maxUrlSegments = 4;

While this is in development, I will vote for OpenCart. I starte using ZenCart (but it is old), then went to Magento at the beginning (but it turned into a behemoth) and lately I checked LemmonStand, Interspire and OpenCart. Both Lemmon and OpenCart are really good. Lemmon is commercial and its modules do add up and thus the cost, but I found it very well developed. OpenCart is really good for what it makes, simple ecommerce shops.

Adam, I think we just answered at the same time... don't be so harsh on yourself

Just pushed changes made by Ryan. They went in almost exactly like that.

I've been suggesting to have a better click through functionality a while ago (http://processwire.c...-functionality/) Now seems a proper time to bring this up again, so my suggestion is to have a direct link to the default properties of a fieldtype in the modal window of the context-based settings.

Pure Shit