DaveP

@kongondo I'm testing the dev branch (URL scheme 3 and comments not installed, per my earlier comments here) and a few problems appear, which seem to be coming mainly or entirely from the markup module and the included template files. Am I better posting here or on GitHub?

Yes, I was aware. My main problem is not being able to settle on a way of implementing the site. I had this daft idea of using no JS at all (no jquery or anything) for the front end, just CSS, but there are a few problems that rear up as a result. And then really interesting stuff like http://labs.ft.com/2014/09/polyfills-as-a-service/ (don't know if it has been mentioned hereabouts before) come along and really beg to be used...

@Kongondo I tried Disqus on a site that hasn't launched yet and, having played with it quite extensively, I quite like it. I really will have to bite the bullet and get on with WP -> PW!

Clicking 'Like' is not enough. V2 is brilliant - being able to choose the url structure is an absolute killer, and (for me, anyway) being able to not have comments at all from the install process (when/if I get round to migrating my own blog (very neglected) from WP, I intend to use Disqus). Thank you Kongondo!

@mr-fan Looking at the Cheatsheet, $event->addStatus(Page::statusTrash) looks as if it should do what you are trying to achieve, although I haven't tried it.

Just off the top of my head, I think I would look at using url segments (well a url segment), with one template dealing with all the steps by way of the form submitting to itself. So the page would be example.com/order/ and each step would be denoted by example.com/order/step2/, example.com/order/step3/ etc. I agree that $session would probably be a good way to store the data as you build it up, and you would need to check that, at any given step, you have all the data you would expect at that point. A progress indicator (working like a breadcrumb trail, but including 'greyed out' future steps) would help usability, both allowing the user to back up and showing them where they are in the process. Smarter people than I will surely come up with better ideas (ajax, anyone?), but, as with almost everything in PW, there are almost as many solutions to every problem as there are people attempting to solve that problem.

Just upgraded a 2.3.5 installation locally, with apparently complete success. Just a couple of very, very minor observations - I only noticed it after I had clicked the button to continue, but there was (I think) a somewhat unstyled 'Abort' (or whatever - it was grey in my admin theme) button at top left when confirming the choice of branch to install. I was initially slightly surprised that I was logged out without noticing a warning, although completely understandably. Just thought that this might worry less experienced users (or I missed the warning).

I have used SagePay in the past, some 8 or so years ago. From what I recall, their integration was somewhat easier (and documentation infinitely clearer) that PayPal, for example. I expect you will be pleasantly surprised.

The great thing about PW's reliance on real PHP for templating and everything else is that there are loads of really helpful resources to help learners and improvers - This forum and the PW main site PW-related resources by community members Teppo's FlamingRuby & Kongondo's site - and others And if you get really stuck/interested http://php.net/ and the myriad of other PHP resources out there. I would go as far as to say that there isn't a templating language/system that is anywhere near as well supported. <edit>Man, it's hard to post a link in here these days!</edit>

I'm not an expert, but I think a server problem is likely the answer, either a misconfiguration or something broken. Has this happened more than once? I'd be inclined to contact my hosting company if I were you.

Really interesting colours for the navbar and headers - works better than one would expect. Just a small point - the breadcrumbs don't seem to update.

http://www.aptana.com/products/studio3 does. I find it a bit slow to start up and it can be a little unresponsive at times (your mileage may vary). That said, you can work on files on a remote server as easily as the local filesystem. You just enter FTP login details one time and connect that way, when you hit <Save> it saves via FTP too. It also has built-in Git support. http://www.eclipse.org/pdt/ does as well, I think. (Is one based on the other, or am I imagining things?)

There is also Soma's Template Notes module - http://modules.processwire.com/modules/template-notes/

@diogo Has that not (almost) always been possible? From http://processwire.com/api/selectors/ - title|body~=sushi tobiko - seems to have been there a long time if memory serves.

That error appears to be in a jquery plugin. Are you loading jquery and any jquery plugins locally, or from a CDN where they might have changed?

.htaccess is favourite, as that error text Soulsliver quotes is not the one from PW.

@Nico I did wonder about that but since it is directly about PW, I put it here. That said, if any mod wants to move it, then go ahead.

That connection never even occurred to me! (#accidentalpartridge)

"A moment of sudden realization, inspiration, insight, recognition, or comprehension." (Merriam-Webster) (Nothing to do with these guys.) You are cordially invited to share your PW Aha! moments here. Hopefully others will benefit. For instance, the project I am currently working on includes a form to allow the entry of televised football fixtures (Time/Date, Home team, Away team). This is implemented as a PageTable and I needed to list any lines already existing and a blank line to allow the entry of a new fixture. foreach-ing through the existing fixtures is easy, but how to cleanly (in programming terms) add a blank line? $a->makeBlankItem()! $fixtures = $pages->find("template=fixture"); $emptyFixture = $fixtures->makeBlankItem(); $fixtures->append($emptyFixture); foreach($fixtures as $fixture){ ...do stuff.. }And that will include a blank fixture at the end. The ...do stuff... will very likely be form inputs. (I know a couple of lines could be chained (okay, 1-3), but it reads easier to me as it is.)

Aaah, US dates vs Euro dates! (Current project I'm on uses loads of dates & front-end datepickers ) Top Tip - PHP's strtotime() will assume 08/04/2012 is US date i.e. August 4th, but 08-04-2012 will be interpreted as Euro i.e. 8th April.

I might be completely barking up the wrong tree here, but some synchronisation shouldn't be too hard using the tools that PW already provides. Thinking out loud here, so please chime in and tell me I'm bonkers or whatever. Some data will only change on the remote server - orders, comments etc. Some will only change on the remote server - editorial changes, new pages etc. And some will change of both - can't think of an example. We can probably specify which group each changed item falls into by PW template - template=order, template=comment for the 1st above, template=basic-page for the 2nd. For each of these we just need to know what has changed since we last synced, which is doable. (I'm thinking some smart cookie can write a module for this, but it might be possible through other means.) We can easily get PW to output JSON, XML, CSV or whatever, which can be read in and the changes made to whichever (local or remote) needs to be updated. The only problem is where both sides have changed, there would need to be a diff file created or something. Your thoughts, people?

Very good points, Joss. One of the arms of the company I work for sells advertising, in just 3 standard sizes, each size having a price, and I did the same as you mention above with those sizes & prices, so each mention across the site can be updated in one place. Bonus Suggestion - (along similar lines) One thing I have been doing recently is, in /site/config.php, declare $config->siteName = 'Your Site Name Here'; and then I can use that variable anywhere in the site (navbar brand, meta title etc.etc.). Save typing and ensures consistency. (And makes standard boilerplate site profiles easier.)

Martijn is absolutely right in both points he makes. Here are a few of my own thoughts... There are some things that we can control directly - 'On-page optimisation', and that is where PW and a bit of thought & skill can make a real difference. (I'm not talking about spammy keyword stuffing or anything here.) Reading around the subject, it is clear that things Google likes include (in no order of preference) Fast loading pages - PW helps out of the box but there are plugins for minifying code & caching for example. There are also helpful post on here about .htaccess tweaks to help loading speed. Clean, (semantic?), error-free markup. Responsive designs. Microformats / schema.org markup. Indications that a site is 'for real' - a contact email, a phone number, a postal address etc. Links to actual, related social accounts (Twitter, FB, LinkedIn etc.). This kind of thing (including obvious old-school stuff like meta title and description tags) is not difficult and I firmly believe can give you a head start in the search results. This article http://www.thesempost.com/google-rewrites-quality-rating-guide-seos-need-know/ talks about revised Rater Guidelines and mentions things like offering readers other content related to the page they are on (so called 'Supplementary Content'). With a bit of programming (and we have discussed this subject here before) that is again something that can be built in. There's a bunch of other ideas in there. It isn't too much of a stretch to expect that, without doing too much traditional link-building, a site incorporating some of these ideas could launch, and with some social promotion, start gaining valuable organic, editorial links very quickly. I firmly believe that any site not taking advantage of these (relatively) easy optimisations is not making the most of the opportunity.

It's a safe bet, though! Joking apart, diogo's answer covered exactly the points that occurred to me as I was reading the original post. My only concern would be the amount of duplicate content (which I know you excluded from the original question).

What diogo said.