Yeh - so I see. Now I've dug a bit more. I'd not encountered it before.
I'm still horrified but as I'm not going to write my own CMS I'll just shut up now ?
Ok... get the idea. Thanks.
I'm going to add this to the list of things that I would give one of my devs a row about, though ? Along with jQuery's '$', most uses of try..catch (rather than writing proper error handling) and anything that results in 'unknown error'. Always use descriptive function names. I don't mind typing a few extra letters.
There seems to be a function, somewhat bizarrely, named double underscore. Which confused the hell out of me for quite a few minutes.
After a bit of digging, it seems to be to do with language translation.
Why would anybody call a function __? Probably just venting...
What's the thinking behind 'site' being in .gitignore?
Is the thinking that someone developing their own site (which must be pretty much everybody) will have just 'site' in a separate git repository for version control? Or am I missing something...
I feel a bit stoopid asking this (I'm new around here), but module class files have a .module extension. Which is a bit annoying as it's a .php file and it stuffs up my editor. To save having to remember how to map extensions in Vim is this required?
That's all helpful. I really just wanted to make sure that there wasn't some magic that I had entirely missed.
I'm quite keen on using mustache for templates so I've got a bit of work to do there. I have 'TemplateEngineFactory' installed.
I think it's going to be one of those - get stuck in, make a mess, start again things ?
I'm completely new to Processwire (but not PHP development) and have been playing around with the included sites.
I'm slightly hazy about the best way to start my own development. Is it normal just to start with an existing site, dump the 'install' directory and so on? To deploy the site just backup and restore the database and copy the (and my) Processwire code and modified site to the live server (well, I'll use Git)?
I think I might be asking if there's a fancier way to handle database changes/upgrades once my site is launched and then there are subsequent changes.
I'm wary of creating any 'gotchas' down the line when I want to deploy the site - in particular around the database.
Sorry for vague questions