einsteinsboi

apeisa It does sound straightforward when you frame it like that (template != template file). I'm going to play around a bit more with that idea of one template and then loading site specific css and html, and report back. But if you have a minute to do a code sample for me that would be epic Thanks for responding again. Yes I do have a pretty good idea what the fields will be but not what they will look like as these will be different html/css files provided for each babysite by the client. This is what I mean by different. Each babysite has a different html/css template to be provided that is out of my control, I just have a very good picture of what fields will be on each at a minimum

So after spending some time reading through the template approaches thread Kongondo linked to, I am feeling quite confused and rather overwhelmed and very aware of my lack of knowledge Any simple tutorials out there to guide me with my template situation? Or a simple walkthrough of sorts? As I mentioned the sites will be different in layout and style but I can safely say they will all for the most part have most of the same fields, unless the baby site is a VIP baby in which case it may have a couple extra fields. Thanks for all the help

OK, so I definitely have a lot more to learn about how templates work in Processwire Thanks for that link I'll read through the thread in more detail and see if I can't wrap my brain around it. Yes, some of the baby sites will be structurally AND aesthetically different. After further planning I am sure each baby site will be just one page, so shouldn't need more than one template. The main reason that I was thinking that I'll need many templates is because, as I said, each page on this site will be it's own site of sorts, and will have a different layout and styling from other pages. For lack of a better example, think of each page as a landing page for a different entity with its own layout, colors, etc, or as I explained in my initial post, as a baby site. Each baby site (page) may have a different pages under it. Does that make more sense?

OK, so I've checked the database and the admin url is definitely /processwire. So that wasn't the problem. But all the directions to check the htaccess paid off I opened and made some changes. I commented out the "RewriteBase /" line and added "RewriteBase /sitefolder/ " where sitefolder is the name the subfolder the site is installed in and that's done the trick!!! I'm not entirely sure why this was the problem since I never had issues logging in a year ago when I created the site and as far as I know nothing's changed on the server since, but it works now and I can log in Thanks for all the suggestions and help!

Thanks guys!! Will go through these suggestions as soon as I can and get back to you. Saturday night here, "apparently" I have to get away from the computer and be social and whatnot... meh

Thanks for the suggestion. I did think about that, but the client is a complete non-techie and would not have touched anything. Plus he only has the login to the processwire admin, not the cpanel or anything like that. So I'm quite puzzled. The main domain just has an index.html placeholder file in place because I haven't quite started building the site on that yet. The only thing I can think of is that my host ran some updates that may have affected something. But all my other websites on that server (none of them PW) work just fine.

I don't think it's trivial, but I don't believe it's too difficult either. I haven't tried it though, but you won't lose anything by giving it a go There are lots of basic Paypal IPN tutorials on the web. Will try and find a link to a simple one for you, but google will get you started. Here's a link to get you going on the processwire end: http://processwire.com/talk/topic/1293-how-to-set-unpublished-for-a-page-in-the-api/ Best approach with these things is to start coding, trying, experimenting, and post here any hurdles you run into and people will pitch in and help you keep moving forward.

OK, so I'm satisfied with the thousands of page being a non-issue for PW. Now I'm having some angst about the templates end of things. Each of these baby sites will have its own template, so that means thousands upon thousands of templates... will PW be able to scale fine to cater for this? Any one experienced this? Any issues? thanks guys mary

I don't think such a module exists at the moment, but I would think you could accomplish this with the PayPal IPN. Once the IPN reports back that the payment is completed then you could set the page to published.

I built a simple Processwire website about a year ago. Recently the client asked me if I would make some changes, and I have not been able to get the login page. I'm not sure what's going on. I know for a fact that I didn't change the standard login url, but when I go to the domain url and add /processwire to the end of it I simply get redirected to the site. I confirmed that the login url is correct by looking at my master sheet of logins and passwords, so I know it's the right page, but it won't load. I wonder if it matters that the site is installed on a subfolder? So the url looks like this: masterurl.com/sitefolder/processwire. I've been able to make the changes the clients wanted by directly editing the database but I need to be able to log in and work on the website. Any ideas? cheers

Ryan, I like your honesty, how gracious you are, and the fact that you're just such a nice guy

Looking forward to this!

I've been working with Drupal since v5 all the way to the current version. I find it quite a powerful beast, and I can honestly say I enjoy working with it for the most part. My biggest pet peeve with Drupal is how complex the themeing is, and what a tangled mess it spits out. This is supposed to change with Drupal 8, so time will tell. The other thing is that for how flexible it can be, it can conversely be very inflexible, and the more complexity you need the more modules you have to use. The more I learn Processwire the more I believe that you can accomplish pretty much anything with it without getting too much complexity involved. Since I'm still learning PW I still find myself reaching for Drupal particularly for projects that need complex user relationships and roles and permission settings. Drupal excels at this. I am sure Processwire does too, but I'm not there yet. I guess the other thing I love about Drupal is it has inbuilt multiblog and forum, so it's the logical choice for me for certain projects where a client wants these things and has a limited budget. Because I know Drupal well I can hammer out a Drupal project with these things quickly (as long as someone else does the themeing... LOL)