artaylor

@nik: Thanks for the idea. I scanned all .php & .inc files in both /site and /wire and the only 2 files that contain the text $config->demo are /site/config.php and /wire/core/admin.php. Neither of those set the variable to true. going to do an apache reset and see if that helps...

I am running a local server (XAMPP) and have been converting a site from MODX to PW for the last few days (while I learn PW). Everything has been great. Now, all of a sudden I get the following message when I try to save anything: Saving is disabled in this demo. I have logged out and back in. I have checked the /site/config.php file and $config->demo = false; I did set $config->debug = true; earlier today while trying to figure out a problem. Suggestions?

Performed a fresh install. Win7 XAMPP: - Apache/2.2.21 (Win32) - PHP/5.3.8 - MySQL/5.5.16 On my local dev server I use the default root with no password since I am the only one on this machine. The installer would not let me leave the password field blank and I had to create a user to finish the install. Anthony

@joss: don'f forget the vital design tool called a restaurant napkin. @ryan: thanks for your input. I have to say your experience would far eclipse mine in the web development world so I will take a solid look at how things are being done and perhaps move that line... In general, I am working my way through my first PW project. It is more challenging than I thought it would be, but I think that is because I am making it more difficult that it needs to be and I need to "grok" this more fully. I keep thinking how I would do it in MODX then having to re-think it. It is coming along, albeit slowly. Thanks for all the feedback. Excellent forum!

Wow. I did not expect this much response. I think it says a lot for the community and the passion behind Pw. As I mentioned, I am very new to Pw so it is possible that once I get to know it better I will agree that a template language is completely unnecessary. Also, I have no problems with it being a module that can be loaded if needed. I certainly don't think it needs to be in the core. So, if there are modules that already exist then I am satisfied. For example, I hate TinyMCE is totally screws up my code. So, I don't use it, but it is there for those that want to. That is one of the things that I see with Pw that I like. Thanks for all the feedback and comments! Now, for my own enlightenment, I am interested in where you all draw the line between Design and Development. In my current situation, my designer knows HTML and CSS (he obviously knows design too). So, in my thinking, that is the demarkation point. I should not need a copy of Photoshop to develop and he should not need to load debugging tools, etc to design. He provides clean HTML/CSS and I fill the templates with data. That is why I feel it is important that the designer can modify the templates and not just hand them off to me to implement. The user is expected to handle the data so why are we keeping the designer away? Is this not a 3-way partnership? I know that some of you are one-man shops and totally capable of doing it all, but I am trying to understand this from a small team perspective. I have done the last few sites in MODX Revolution and the designer was fine with being able to modify the templates and leave all PHP to me. If he needed something specific, he could ask and the same for me. The user just entered the content. It seemed to work well and balance out the work. My musings... I will probably look back on this message and laugh at my Pw naivety. It's all good and thanks again for being so responsive and open. Anthony

Hi, Brand spanking new to ProcessWire and I must say I am very impressed so far. My background is 24 years in non-web development, and recently working with Joomla, WP, Drupal, custom PHP and learning Laravel. I would like to suggest that this is not "syntax" question as it is just as easy to learn <?php echo $somevar ?> as it is to learn {{ somevar }}. However, as a developer who is working on a team with a designer, I really believe it is important to separate out display from logic. It is too easy to give a designer with limited PHP experience the requirement to use PHP to create their template (WP anyone?). We all know what happens with a missing ; in a PHP script... BLANK SCREEN. This is totally unacceptable in a team/enterprise environment and also, I think it is a flawed design decision. I understand that PHP was initially disigned as a template language, but it has moved beyond that at this point and PHP5 is a decent programming language. So, we are really saying that we expect designers/users to actually know and understand a full programming language when all they want to do is create an HTML template that has some placeholders to put their content. Laravel was mentioned in an earlier post. I think it is a brilliant product and it includes Blade, a templating language. Why? Because it is important to allow non-PHP developers access to this awesome technology while still allowing the developer full access to the framework. I work on small teams with a designer and a moderately competent user. As it stands, I would not let my user or my designer have too much control over the PHP so that means more work for me so I don't get the 3am phone calls saying the site is down because they missed a ; or a closing >. This is a project with HUGE potential and I think KUDO's are deserved to everyone involved, especially Ryan for having a brilliant vision and forsight. Let's not make this a "geek" only tool but be inclusive to others by allowing an alternative to PHP as the templating language. Think beyond a one man shop and this product has tremendous potential. My 2 cents! Anthony