kongondo

Hi Ben, Welcome to PW and the forums. Out of curiousity, am wondering ,are you tied to using the Windows Server virtual machine? If not and especially if eventually you want to deploy your site to an Apache, Linux, PHP server, I'd suggest ditching WS virtual machine and instead, test PW on either WAMP or XAMPP. This will allow you to get up and running quickly, especially since you are new to the CMS world.... If these terms don't make sense even after Googling, I'd be happy to provide more info .

Hi Diego, Going by the title of your post, I am assuming that "standard" is the name or title of a page that would be selected via a Page Field? PW does not store the name or title of the page referenced in a Page Field. It goes one better; it stores the ID of the selected page. So, you will have to reference the ID of standard instead of using "standard". E.g. the ID could be 1035. Use that instead. Is this a single Page Field, btw? By storing the ID, PW enables you to easily get all the information about the referenced page. This is just to get you started on restructing your selector (not meant to work immediately). I have to go but may revisit this post if you are still stuck and haven't received help yet...

Former Nokia boss Stephen Elop to receive $25m pay-off.....for a job well-done I suppose? tsk, tsk, tsk... http://www.bbc.co.uk/news/business-24171520

Never trust user input. So yes, you should sanitize user submitted values.

Hi Icedogas, Welcome to PW and the forums. If you switched debug on in your /site/config.php/, you would see the queries. Please note debug should only be turned on in dev/testing installs and not on your live/production server. Find this line in /site/config.php $config->debug = false; and change it to $config->debug = true; Now in the Admin, you will see your queries (scroll down to the bottom). Note, this is only for the Admin. For frontend, you will have to do it differently using PHP code...

Mary, I'll see if I can rustle something up. I would stick with Soma's approach for now. I'm still unsure what you mean by differences here. Maybe provide an (visual) example about the differences? What I mean is this, differences in layout can mean either totally different markup or can mean same markup, but with jQuery and CSS wizardry, a different layout is achieved. Another thing, at this point in time, do you have an idea how the baby sites will look like and how many fields they will require? I don't think so, but just asking. In planning such a site, pen and paper and/or a Spread Sheet are my best friends. I'd write down all the fields that will be needed and note those that will be unique or common...But, I am jumping ahead here.

And here's another by Tina.. http://processwire.com/talk/topic/4541-custom-intranet-app-for-event-logging-and-records-management

Very nice Tina! Very inspirational. Thanks for sharing

I think that's the sanitizer at work. Can't think of a solution atm, but am sure somebody else will give you a better answer

I think I get what you are saying but not entirely. Data is not stored on a template basis but on a page basis. Yes, fields are associated with the templates in which they appear but ultimately, data stored is unique for each page using that template. By updating one template, do you mean update one page? You can also set some fields as Global (e..g the title field in the default install) but I don't know if that helps in this case. Using the API and hooks you can definitely update some fields automatically depending on some other fields. I believe I have seen such an example here in the forums...But, again, I am not sure I follow your question

Small world . Nice to know that the book was helpful, thanks. Well, I think I can say with utmost confidence that I'll never get you excited about another CMS . It's hard to imagine anything better than PW; I haven't found it and am not looking either . David, welcome to awesomeness! aka PW .

Hi flyerdave, Welcome to PW and the forums. PW "template files" are nothing more than HTML interspersed with some PHP to output the dynamic content. There are various ways to convert that theme for use in PW. One way is just to copy the output HTML by viewing source in your browser. Then, you would strip that of all dynamic content and remain with the skeleton HTML. Maybe you could also do this directly from the WP theme PHP files but am not sure. It has been a while since I looked at WP themes. All I remember is that they are a nightmare! I highly doubt you will need all those 25 PHP files in PW! After this, you will have to decide how to output those dynamic content of your site. Those would either be whole pages or fields of certain pages. I would say converting the theme for use in PW should be the least of your worries. You should instead concentrate, in my humble opinion, on learning the basics of PW. In order to make best use of the system, you will have to know some very basic PHP. Have a look at the following topics in the docs: http://processwire.com/api/variables/ http://processwire.com/api/selectors/ http://processwire.com/api/templates/ This will require some work and willingness to learn on your part beyond the point and click common in other CMS. On the other side, great rewards and total freedom await you if you are willing to overcome this initial hurdle

Hi David, See this thread and Diogo's response...it should get you on your way... http://processwire.com/talk/topic/3133-detect-first-and-last-sibling-page/

OF, I think you are confusing the Blog Profile and the Skyscrapers profile. Those images are in the latter, not the former . For instance, westin.jpg is here: /site/assets/files/4179 and marriott3.jpg at /site/assets/files/4190

Actually, Andrew, I have just realised the above may not be what you want. The above limits how many characters you can type. If on the other hand, you are looking for something that will trim the amount of text entered to a certain number, there was some code posted here on the forums but can't find it at the moment... Here it is, by Ryan http://processwire.com/talk/topic/22-how-to-build-a-news-page/?p=51

TEXTAREA COUNTER http://modules.processwire.com/modules/textarea-counter/ http://processwire.com/talk/topic/2343-char-counter-for-texttextarea-fields/ Source Code: https://github.com/boundaryfunctions/TextareaCounter TextAreaCounter.module: https://gist.github.com/somatonic/4252958 TextAreaCounter.js: https://gist.github.com/somatonic/4252962

Hi, Not answering your question...just a comment/rant at Foundation CSS. <rant>I use Foundation myself and I didn't know about this. What an absurd way of creating a divider effect!! </rant>

Yes, it is possible and has been done. I am in a hurry so can't go into details but there are at least two examples in the forum. One, a bookmarking app by Jonathan and the other an Intranet app. No code examples for the above two, atm..but, yes, it can be done See also Diogo's Admin Custom Pages module. You can also do this by creating your own Process Module.

If the report will end up being a page in the admin you might as well do this in #2 by creating a page then. Since a page's data is also stored in the db, why have a db entry (page) for the report (#4) as well as another db entry for the form (#2)? Anyway, I don't know your exact needs. As for exporting to PDF, there is a module for that. Check the modules directory. Have a go at the code in the links I posted above then we can take it from there if you get stuck. Bottom line is you will need to use: $input->post (assuming you are not creating a multi-dimensional array; in such a case, you would use PHP's $_POST) to handle the form data $sanitizer - to sanitize your data. You can also (additionally) use client side validation just to make sure emails are formatted correctly, etc. new Page to create and save new pages based off your form input data PW db class if you want to save your form data to custom db tables. You can also use PHP msqli or PDO. If using custom tables, you will need to create this either using PHP or directly in phpMyAdmin or similar An email class to send your emails I might have forgotten something...

This classic thread started by Matthew will get your started with #2 and #3 (validation = sanitization + correct input) http://processwire.com/talk/topic/3105-create-pages-with-file-upload-field-via-api/ PW $input variable: http://processwire.com/api/variables/input/ Great form examples in Soma's Gist: https://gist.github.com/somatonic

Now we are talking Please clarify: #2: Do you want to save this as PW pages or in custom db fields in your PW database? #3. What sort of reports do you want to create? PDF, Excel, etc? (this should be #4 actually?) Edited:

Nice addition Soma, thanks. This makes it even more versatile!

http://processwire.com/talk/topic/4398-two-column-admin-theme-concept/ Ongoing discussion about PW backend...

Adrian, thanks for the update! If possible, it would have been nice to have a before (original version) and after this update text and screenshots (I know could potentially lead to a long thread and not practical with every update). It helps to compare, follow progress, etc. Not a big deal though...

I guess it is safer to assume that Ryan has been quite busy lately