Mike Rockett

Hi! I thought this may come up. For me, this is a design choice. I'm one of those people who swims away from the stream, and so I like to make things different, as I believe they have an appeal. At least, this is what I have come to find with some of my customers, as well as theirs. That said, if more people find this to be an issue, I'll rework the design. Again, this is a style thing, but I do agree with you. I'll make the labels clearer, and easy to read. I did give this some thought. I mainly deal with businesses, and have only had one experience working with a professional (a site for a spiritual musician). That said, I think I may land up breaking the form into a wizard, so that the correct questions are shown, dependant on whether the person filling out the form represents a business or not. What do you think? Agreed - I think it'll be better to formalise, but keep simple at the same time. Yes? It is only one box - but yes, I'll do that. Thanks for the input - much appreciated

Greets I'm building a quotation request form for my teeny business, and I'd like to know what you all think about it - if you don't mind. http://www.foundrybusiness.co.za/quote I've tried to keep things simple, and to the point. Do you think that's the case? Have I asked too many questions? Am I missing anything important (except for the submit button, hehe)? Thanks a ton!

You're very welcome

Felix I really like this one. It's clean, yet vibrant, and then so easy to use. Great stuff!

Hehe, indeed - it is working now. I have a small critique about the boxes on the home page, specifically the ones at the bottom left of the image. I think it's because of the font width that the text is slightly hard to read over the darker portion of the image. Obviously, it is readable, but there's a small amount of strain there. I also see that there's what appears to be a language switcher at the top right. Will there be any new languages in the future?

Something wrong with your public root? I have to click on htdocs to load up the site... Links don't seem to be working either - must be a rewrite issue there... If I wanted to see a specific page, I'd have to visit the following, for example: sgh-net.de/htdocs/index.php/?it=loesungen/scan-und-dokumentenmanagement/scanning-von-altbestanden/ But, from what I can gather on the home page, site looks good to me!

This has happened a few times now - I'm running the latest Opera, and the forum (whenever it feels like it) loads up the Mobile theme. How is this possible?

Sure, I'll include it.

I see - so it wouldn't be a common thing then, I guess. I was just thinking if I needed to include it in my module.

Hey Tom - so I have a question about the alternate domain status codes: Why would we redirect to the domain (and URI) if it returns a 301? Surely you would redirect to it only if it returned a 200?

Greets I'm busy with a new module, and I'm using PageListSelect. However, like the Page Tree, it isn't easy to select a page in a different language. To get it right, I have to go to my profile, change the language for the entire backend, and then go back to the module's form. Any way to show language tabs for PageListSelect?

Adrian, Tom - Indeed, it will support that, quite fully. It would be a case of directing /programs/{program:segment} to /about/programs/{program}. I'm sure it'll be ready by the time you need it, Adrian. I worked on a bit yesterday (importing). I have exporting on the to-do list, but I wonder how necessary it is. I may just leave it out, until someone needs it. Or perhaps we put it to a vote, or discuss further. Anyways, by the end of next month, I'd like to have a beta put up. I know it sounds like a long way away, but I assure you, if I had time on my hands, this module would be finished by Friday next week, if not sooner. Edit: I need to get everyone first names right! Hehe!

@Phillip - True, but I just feel that it would be handy to have it in one module... That's just my opinion.

Looks cool to me! One thing: perhaps auto email obfuscation is in order?

Are all your templates doing this? The only thing I can think of is that your home page is not doing what your other templates are doing. Granted, I am sure you haven't hard-coded paths, but it is worth a look-see. Have a look at $config->httpHosts in site/config.php. What's in there? However, it's probably not that as your other pages work. Perhaps you'd like to share your template files so we can see where the problem may be coming from?

@Zenophebe You can call it a 'mish mash', if you like, but that's not what it is. Let's be plain about this, and compare to a CMS like Bolt, which I use for some projects. Where you have your content-type definition in Bolt (which is defined in a YML file), you declare all the fields and options for that content-type. In PW, the same can be said of templates, only it's much easier to accomplish, and has support for an infinite hierarchy. So, templates are your content-type definitions, and Pages can be based on any of these templates, and can be put anywhere you like. What makes this not a 'mish mash', as that it allows you huge flexibility. I don't think I fully understand this... Why would creating a child page create a content type? If you create a 'products' template (that lists child products), you can then set rules (Family tab) on it that only allow the creation of pages based on the single 'single_product' template as children - this creates your 'product data'. Once again, I draw back to flexibility. PW doesn't force anything on you. You need to fully grasp the concept of how PW works before you can fully understand, and make good use of, it's flexibility. From a CMS point-of-view, it allows you to do almost anything.

Are your URLs hard-coded? If not, you only need to edit your site configuration by changing the domain(s).

I see - makes sense indeed

Reno: Indeed - and I believe it's the only module of it's kind. I'll still be releasing the module, as I'm sure there are those who'd like to use it. Also, I find what you're wanting to do with your site quite interesting. I have a question: why would you want to maintain the URI structure for the legacy site, instead of performing permanent redirects? If it's something that many developers do, I'd be willing to include the functionality in the new module: Perhaps I would add a field called "map to domain" where you enter a domain ("legacy.site.com"), and it will check that domain for the page being requested. Then, it will (per the choice selected) either load up the page on the new site, or redirect to the legacy site. Sound good? Edit: Alternatively, and to make things a little simple, I could make the module ask what kind of redirect needs to be created before showing the form. So it would ask if you want to create a "Standard Redirect" or a "Legacy Site Redirect/Map". Yes?

Hey guys - so sorry, things have been quite hectic on my side of the world. As such, no real time to finish up at the moment. I'll give it a bash for some time each day for the next few days and see how far I get. I'm really just porting my redirector extension for Bolt into a PW module that can be modified from the back-end. You can learn more about the Bolt extension here. Reno, you'll probably be using something like this with the new extension: /somepage/{name:all}, or even just /somepage/{path} (a smart wildcard)

It's included in the initial invoice, and I include information about all the service-provisions in an SLA. A year later, they're given another invoice for the hosting (and thus maintenance). With regards to site changes, I don't bill if the change takes me less than 10 minutes. Reason being: I don't have a lot of clients. The second I have plenty, and support becomes a time-issue, I'll be revising it. I may set up a retainer programme, or I may separate the hosting fee into two parts (actual fee for hosting, plus maintenance and site changes at a flat fee per month, payable per month or per year). I find this quite interesting, and it has been debated amoungst my colleagues a few times. Here in SA, the onus is on the the person who signed up for the hosting to legally state (that is, on paper, signed) that he/she will not interfere with confidential information, such as email, customer databases, etc. Further, I keep a video-log of everything I do on their server when I sign into it. If the client requires me to prove that I haven't interfered, should something go wrong, I show them the videos, and state that I have kept to my word. There is the issue of trust, however. The client doesn't know if I ever logged in between any two sessions, for example. Once again, it's a 'word' thing. Personally, I keep my word - I don't know so much about others (most do, but you get some dingy people on this humble [or not-so-humble] planet). Also, like Joss does, I don't force the client into getting a hosting package with me. If they choose to host it with someone else, I investigate and inform them whether or not I can provide server support. If I can't, I recommend someone who can. However, I always offer site support. After all, I built the thing, and so I should be the one to do it. That said, I do give the client the opportunity to choose someone else (perhaps someone in their IT department, if any) that will do site-support. If that becomes the case, I sever all ties from that front, leaving them responsible. When it comes to things like this, there's no half-in and half-out. That said, I do make sure, at the onset, that the appointed person knows what he's doing, and then I sever ties on that front. This is something I'll be venturing into when I have more clients: a cloud package. Some South African ISPs do have cloud servers around the world (like Afrihost, which uses MTN and its network), and they're pretty good, so I've heard. That said, I'm sticking with shared hosting for now, as I have a solid legal framework/process for them, and it's all mentioned in my SLA, and any other binding contracts. My process: I get asked if I can build a site, or offer a non-client with an old/outdated website if they'd like a new one Once we've established that they want one, I request all the information/requirements I need in order to build a quotation Information and requirements received (written), and so I build up a quotation Once they've accepted it (after revisions, if necessary), I draft up an SLA (based on my blueprints), get it signed, collect 50-60%, and begin the design and development process (including conceptual work). Once I've done major pages, such as Home and About Us (for example), with the full design (and templates) at least 90% ready, I upload a development version to a server (be it mine or theirs, whichever they prefer). The preview is also user-name/password-protected. We then discuss what's already there, and what content/design tweaks need to made. I then make any changes, add all final content, and update the preview (now in beta). Client makes final reviews. Once they're happy with everything, they're informed that they need to pay for the remainder of the quotation, at which time an invoice is issued (stating that they've already paid x amount). Once paid, I upload to the staging server (or move to staging folder on the server, whichever is the case). Job done! Of course, the process is subject to change, on a client-per-client basis - but most of the workflow stays in tact. Edit: Oh, and a note about the 50/50 (@MindFull): I've never had a problem with clients changing their mind. If they do, I'll revise.

My process differs per client, but follows a simple model, similar to yours. In terms of hosting, the client pays me for it, and I host it with my HSP. I believe that it's a cleaner way for me to charge a tad extra, which covers maintenance, and ad-hoc server-support (creating email accounts, releasing things caught in SpamBox, etc.). I also ensure that my clients pay me upfront for an entire year of hosting.

Or just use Repeaters... Yes?

Oooh, I see. I guessed something was up on the server. I had already installed with the URL. I should have checked the modules page first. Just assumed it was on the list because the link was made available, and I was on the page. And yeah, that button really has to be fixed. I just don't get what button it's really pressing...

Great site you've got there! Well done!