Godfrey

Oh yeah, I saw that and that's what prompted me to think they may be interchangeable So is it that $page will only work if I make that .php into a template? And wire('') should be used if, for example, I am creating a an includes file containing functions? However that still doesn't really make sense to me because even if I use an include, it will still be rendered into the .php which is attached to a template...

Quick question: What, if any, is the difference between wire("page") and $page? I know that wire() provides you with a global variable, but it seems that if you are selecting the current page or even selecting other pages, $page and $pages does the same thing. Under what different circumstances would you use wire("page") vs $page? Or are they interchangeable?

Ah, okay, I see. Yeah I just read up on working on a testing server first and I see they're pretty important. I need to start practicing utilizing them. Thanks! (p.s. just changed my display name)

I've installed processwire in a few different roots now for a few different projects. Strangely to me, after extracting the initial processwire zip package you get a folder titled "site-default", but after uploading it to the remote and going through the installation it becomes "site". Consequently, I lose synchronization info, and I usually end up having to rename my local folder "site". Or I download the remote version of "site" and delete "site-default" in my local folder. Is this supposed to be happening (does this happen to others)? Am I missing a step?

Ah, very nice. Yes that looks like it works well. Looking forward to giving it a try.

Ah, didn't know that. That would make things a lot better. So do most people use this system when working with processwire? Or does anyone integrate another sort of system?

Hello, I just went through the PW tutorial for making a simple news system: http://wiki.processwire.com/index.php/Simple_News_System But after seeing the result, I'm wondering how this system would scale. Because right now, it seems like if you're creating a new page for each post, things on the administrative UI side will get messy really quickly : I just imagine a really long list of articles as pages under "News Articles" looking like a nightmare. I know I could modify the system so that each article displays a date, but still it just does not look pretty. So I'm wondering whether most of you use some system similar to what is described in the Simple News System tutorial, or if you use something else. If so, what do you use? Do you integrate something else into Processwire? If not, how can I make this simple news system more clean and feasible? E.g. is there a way to further categorize/archive the articles? I mean, I'm guessing that sites like http://www.cmscritic.com/ probably wouldn't use such a system for their powerful news system, would they? How did they do theirs?

Ah, ok. Yep I did switch on thumbnails. And nope, I'm using Chrome Anyway, glad I got this fixed. Maybe some additional notes should be made to the tut? Thanks both for the help!

Huh, a combination of changing the image field "maximum files allowed" from 0 to 1 and using the first()/eq(0) methods worked. Either one of those by themselves didn't work for some reason. Also, when I upload an image, it strangely produces the two files I listed above (it produces the strange pwtut-header-1.0x100.jpg.

Hello, I am following the Basic Website Tutorial http://wiki.processwire.com/index.php/Basic_Website_Tutorial After creating the site settings page and uploading an image to the header_banner img field, the tutorial says to include the path of the image file like so: I changed it to this: However, they should be the same. But unfortunately my image is not showing up. When I pull the code inspector in Chrome, this is the HTML that I see. When I go into my remote folder and navigate to site>assets>files>1008, I see two files: the original jpg I uploaded (pwtut-header.jpg), and one other one (pwtut-header-1.0x100.jpg). What is going on here? Has there been an api change since that tutorial?

Right now I have my processwire files in a folder called "processwire" on my remote server, as a child of the root folder. I'm wondering how I can begin to apply the CMS process to my existing website pages instead of the default, sample site. I'm guessing I can start by moving all those files in the "processwire" folder out into the root directory, but what should I do with the index.php file which the processwire folder came with? I'm also guessing I should replace my sites original index.php file and set the processwire one as the default. But then what should I do with the old index and the other pages as well? Where do the pages I already have go? Basically I'm unsure how I should go about "integrating" processwire into my already made pages. The Basic Website Tutorial ("http://wiki.processwire.com/index.php/Basic_Website_Tutorial") instructs me to clean out everything but leave the default site template and a few fields, but it seems like I would be adapting my site to that template. Instead, I wish to adapt processwire to the pages which I've already made. Tell me if I'm getting the workflow/structure wrong: I feel like the workflow/structure requires me to make each of the pages that I already have -- or an identical part of each page -- a template, and then in processwire spawn off a duplicate of each page in my website using the "new" button and selecting those pages as as a template. I feel like I'm kind of working backwards relative to the workflow, or I'm getting the workflow/structure wrong in my head. Thanks for any help in advance! ​ Update: I've tried changing the "home" page to a template that is basically my original site's homepage, but I get the error: Can't save page 1: /: Selected homepage template cannot be used because it does not define access. I read that ryan said the home, admin, and 404 page are essential. However I don't want the home's template style. What is the php code I need to include in my own homepage to start using it as a template? I've tried copy and pasting this from the original home.php template: <?php /** * Home template * */ include("./head.inc"); echo $page->body; include("./foot.inc"); But I'm still getting the same message.

Thanks! I posted a question about having the files in my root directory to the "getting started section".

Oh, haha, no it's because I tried using Symphony before this and forgot to rename the folder haha. I just realized I mistyped this too. Was working very late last night.

Just finished this tutorial, and one of the natural follow up questions/next steps for me is "how do I now apply this stuff to my site which is all one level above the folder in which all of Processwire is in? Instead of applying it the the sample website" (Right now I have a folder in my root folder named "processwire", which is on the same level as the files and folders for the main website) Would I just cut and paste out everything in the processwire folder out to my root directory? Thanks for the nice simple beginner tutorial, btw. I experienced this fleeting sense of childhood joy learning something simple yet very cool. This is also my first time posting and my first time starting to really use a CMS ever (or at least feel like I'm effectively using one). I've literally tried to start with dozens of others, but shied away from them because they seemed too complicated. It took me over a month to get a wordpress page going, but now that's scraped. And after months (I'm volunteering) I feel like I'm finally going to get my client set up with a good CMS.