kongondo

Only thing to add here is that it is only one of the various approaches possible. Work with what makes sense most to you and what you are currently developing

Yes, you are missing something cool ....You do not need to have a template file named 'abc.php' to use with a template called 'abc'. You can tell PW that you will be using an alternative name for you template file. Have a look at the links I provided. For example, you can have one template file called 'main.php' for use with your template 'events'. Then, you can create a sub-folder called events, i.e. /site/templates/events in which you can place your related template files, e.g. 'details.inc' (or even details.tpl), 'list.inc'...etc...Hope I got you correctly..I have a feeling you already know all these and I am misunderstanding you...slow Friday here!

Hi Enrico, Welcome to PW and the forums... As for template files, the have to go inside site/templates but remember you can use includes in your template files to grab other files in other folders or sub-folders... Have a read here: https://processwire.com/talk/topic/740-a-different-way-of-using-templates-delegate-approach/ http://processwire.com/api/templates/ http://processwire.com/docs/tutorials/how-to-structure-your-template-files/

Btw, default RTE is now CKEditor (in the dev version of PW). I've read something about Redactor in these forums I think...can't find it now... Edit: Here's one of the discussions: https://processwire.com/talk/topic/1964-redactor-wysiwyg-editor/page-3 Main issue is licensing... Tip: best way to search these forums is by using Google, e.g. Redactor site:processwire.com/talk

Wise words from a wise man; Thx T

Btw, you links to the demo videos here lead to 404s...the ones on your site work just fine...

Great first post and webapp zwergo! Welcome to the forums and to PW...There's a number of ex-Jomlaarers here in the forums Is there a missing 'not' here btw? or did you really mean to say your found PW has a steep learning curve?

Yes...read Ryan's reasons from here downwards...especially post #27

Or you can just use PocketGrid CSS (grid system only) and have any number of columns you want...

@NooseLadder, Thanks for testing Blog. If you find any issues or have suggestions please feel free to bring them to my attention here. It's still work in progress and I haven't yet gotten the chance (ahem) to write some documentation

All Site Profiles need to be installed as a fresh installs (i.e. cannot be incorporated - at least not directly) into existing sites. But there's a module that can help with migration...Having said that, if you go this route, you can eventually add other 'normal' pages around the Blog install that don't have to be part of the Blog. If you are familiar with PW, you will know that it's all about pages...In this case you incorporate the site around the Blog install (note: Site Profiles are not module per se) The other Blog module (the second one I linked to) can be installed on an existing site. Currently, it doesn't support multi-blogs. In this case you incorporate the Blog around the site... Read more in their respective forums

That's not the link Sparrow is referring to; This is the broken one..(further down that page)...there's some extra stuff in the URL in the link to the Skeleton CSS Framework.. Markup and styles based on the Skeleton boilerplate CSS framework.

Hi Sparrow, Wow, it seems we are not doing a good job advertising what's already available in ProcessWire .... There's already two Blogging solutions (actually one is just an extension of the other...) 1. Blog Profile: http://mods.pw/2M 2. Blog Module: http://mods.pw/6U They both support commenting (though not threaded comments)....For any specific help please post in their respective forums...

@Pravin, As pointed above, for those who have bought Form Builder, there is a dedicated Form Builder VIP support forum. To get registered, send Ryan an email.

Er, ahem...psst...that was already mentioned by SiNNuT in post #12

I'd suggest you learn PHP first [when it comes to server-side tech]...since it is the most popular server-side programming language (>80% of market). On client-side, learn HTML, CSS and some js, or better jQuery ;-)...you can then pick up node.js along the way....but I am biased. Seriously though, it will do you good to learn PHP. It is not going to disappear in the near future (if it does at all)...

Uh? Old school is not always bad school

Yeah, was mulling this...The option would work best at page level, no? i.e., one may not want this to apply universally....Could be tedious though at page level...

Good point...for Blog I'll go for preserve then unless there is a compelling counter-thought? @Philipp: Sorry to mess up your thread ...Oh, and welcome to PW and the forums...

I'd go for not. In Blog I'll go for not (when I get round to it ). Otherwise, we get into guessing why a page was unpublished in the first place territory - (1). Initial publish was done in error OR (2). Client wants to temporarily make a page inaccessible from the frontend OR.....

Hmmm, does this apply to you? http://share.ez.no/forums/install-configuration/cannot-load-module-pdo_mysql I've run out of ideas though...I'll let others chime in

Btw, what are you PHP and MySQL versions...?

Hmmm, no idea but Google points me to this (amongst others...) http://www.boonex.com/forums/topic/MAJOR-problems-after-PHP-update-PLEASE-HELP-.htm

Cool...let us know how it goes..

Version of PW? See also https://processwire.com/talk/topic/6279-pdo-enabled-but-not-recognized-by-pw/