onjegolders

Creating separate thread as last one was a bit buried. Apologies. I think our VPS provider has been having issues today with their servers and when I tried going to one of our sites we were getting "Unable to complete this request errors". When I turned on debugging, I get the following error Fatal error: Exception: SQLSTATE[HY000]: General error: 1 Can't create/write to file '/tmp/#sql_daf_0.MYI' (Errcode: 30) Which sounds to me like it's a problem accessing/writing to the database (on our server)? Could anyone confirm if that sounds right? Cheers guys.

Tacking my question onto this thread as it has some similarities. I think our VPS provider has been having issues today with their servers and when I tried going to one of our sites we were getting "Unable to complete this request errors". When I turned on debugging, I get the following error Fatal error: Exception: SQLSTATE[HY000]: General error: 1 Can't create/write to file '/tmp/#sql_daf_0.MYI' (Errcode: 30) Which sounds to me like it's a problem accessing/writing to the database (on our server)? Could anyone confirm if that sounds right? Thanks.

Hi Eze, you have to first select a sub-forum and then you should see a "New Topic" button in the top right.

Welcome Marth!

Just carried out an export/import using this tool and the modules didn't seem to get exported. Is this a known issue, or are modules not part of the export? Thanks! EDIT: Hmm, the module files did seem to get exported and imported but I have a "no modules found" in the admin under Modules->Site. EDIT 2: OK, please ignore, seems I need to hit the "Refresh" button in the admin modules section. Clearly been away from PW too long

Thanks for this Wumbo, I've been keen for a combined internal/external URL chooser for a while now, will check this one out.

A whole lot of people are paying a whole lot of money for things they don't need / shouldn't be using / could do better for less. Conversely there are an awful lot of excellent designers and developers who struggle for work / money. A lot depends on who you target / how you sell it and how lucky you are.

Marcus, this looks fantastic, thanks for all your hard work!

Hi Yellowled, I think that's certainly true of some of them like Jekyll. Other like Assemble or Middleman you can build any sort of content you choose like you said. Then there are the NoDB CMS (like Statamic, Kirby) which make as few assumptions about your content as PW (though with some NoDB drawbacks clearly).

Just started using this because the Transmit plugin doesn't support ST3. Despite initially being put off by all the techy options, it's very powerful. I can sync local with remote, pull down remote files and edit them. It even has filediff capability. Consider me impressed.

Slight update (sorry if this is a monologue!) I was quite comfortable building out the static site in Middleman, although I did find the documentation extremely disappointing, for a seemingly well-backed product there isn't a great deal of meat beneath the gravy docs-wise. I started to consider looking at one of the paid products (Kirby / Statamic), they both seemed to be very solid, had good documentation and had the bonus of being a "full" CMS despite being NoDB. In the end I decided to go with Statamic for a few reasons. I was extremely impressed with their docs. The simple admin area is very nicely put together and pretty intuitive. So far I pretty much have the project coded up and have come across some really nice features (some that PW may learn from - as per the original post by Diogo ) Others aren't really relevant as Statamic and PW do cater to different sorts of sites. I doubt it will be used for more complicated database-driven sites, that said, what I do like about it: 1. Configuration through YAML - Have to say this is proving to be a real hit for me. Set global variables, decide which fields to show for any given template in the admin 2. Being able to add content through files - I personally haven't made a great deal of use of this yet as I still prefer adding content through an interface at this stage. Despite this I can see the appeal, especially to people who use MarkDown a lot. 3. NoDB, easier site synchronizing/backups - OK so this is an obvious one but clearly having no database is an advantage when it comes to Zipping a site up or keeping two copies in sync. 4. Templating syntax - This is controversial, not least to myself. I wholeheartedly agree with Ryan's appraisal on using PHP syntax in PW. That said, there's no arguing that when we're using a simpler system for a simpler site, there's something pleasant about being able to leave out some of the less glamorous parts of writing PHP ( ; {} [] ). My preference for tenplating engines over pure PHP completely depends on the aesthetics of the engine syntax. In Statamic's case it is elegant so a plus point for me {{ title }} 5. Variable modifiers - Sort of an extension of 4 really but again when we're keeping things simple it is nice to be able to call on some nice simple helpers that enabe us to write less code. http://statamic.com/learn/templating/variable-modifiers --- Clearly there are things here that are good because it makes a nice change from coding in a more complex site development process (as I often do with PW), maybe of things that PW could one day use, perhaps some way of writing more code in the editor than clicks in the admin, although that must be limited by the database interactions that must be necessary. I still don't think there is a system out there that can touch PW when it comes to a tool that can accomplish almost anything in an organised, lean and powerful way.

Thanks Pidelux, I will take a look at that on my next project. Regarding the static project, I think I've narrowed it down to using Middleman, Statamic or Grav. Statamic (or Kirby) looks useful in as much as it would have a very simplistic admin area if ever a client did want to get involved but they are both private, paid products unlike Middleman or Grav which are fully open source. At a push between Middleman and Grav I think I may go with Middleman as it seems to have a fair weight behind the people using it and it borrows quite heavily from Rails which I am comfortable with to a reasonable extent.

Steve, thanks for the answer but I think if I started having to run anything like that it would take away from the initial positive which would be the simplicity and feel-good factor of using these systems - much better, for me at least to run PW than have to deal with complicated PHP scripts. --- I have a project that I am going to try and run a static or semi-static CMS on to see how it works out but I guess I have two main fears: 1) I'm going to end up needing some more advanced functionality further down the line 2) The client is actually for once, actually really, no seriously, going to actually want to login and update the content themselves. If either of those happen then I guess I'll have to recode it in PW and rue the fact that I didn't just start out there in the first place. Maybe these fears never come to fruition though.

Thanks for a great answer Adam So YAML vs mouse clicks is the big player here for you (plus lack of a DB to keep in sync)

Hi Adam, sorry the question wasn't very clear. I was just wondering how you deal practically with images. I mean on most sites I build there will be different sizes, thumbnails etc. Perhaps multiple images for an area. I guess in a general way, I'm not sure as to the benefits of using these sort of systems once one knows how to use a system like PW. Certain parts of them do appeal to me (the configuration files) but when I download any of these projects and peep through the code, they don't really seem any simpler to me than to using a fully-featured CMS. I totally get the appeal to someone who just wants to load up a theme and then manage their content in Markdown files but once you get beyond that and want to start editing template files and working with more complex structures, isn't that initial simplicity then lost? At which point you might begin to resent the lack of certain features that fuller systems like PW offer. Think these sort of tools go in the "I really want to like them but I don't quite get it" category... Anyway sorry, just my ramblings on the matter

Thanks Adam, how do you handle images? When I tried tools like this in the past I found the threshold above which it made sense to use a "full" tool like PW was actually pretty low. Thanks Macrura, some of these look interesting for static sites.

One thing I do like about CMS like Kirby and Bolt are the configuration files in YAML. As I haven't really used these before extensively I couldn't say if they reach a natural sort of breaking point where things get difficult but there are times with PW when I would prefer to do more work in the text editor than clickety-click. (Never thought I'd say that )

Adam, do you find this a big improvement over just creating static files (html) - I guess the file extensions being removed is the main one...

Superb!

Hi Adam, How do you deal with contact forms and the like on these sites? External URLs or don't use them?

Bolt does look like a nice lightweight CMS.

I have to say that as someone who is using a few other languages to work on a few web apps on the sideline that I haven't found any CMS that offer anywhere near the level of productivity PW offers. Take Ruby for example - it's great using Rails but a CMS using it? They are so far behind it's crazy. I guess most people who veer away from PHP are looking at building things with frameworks anyway so maybe the point is moot. In the PHP world Craft does look great but it just can't rival PW's power (not to mention its Open Sourcenessness).

Write is also very nice http://writeapp.net/mac/ I feel the same. All these static site generators look so cool and easy but essentially you're relying on someone adding a Markdown file in a special format. I don't know many clients (myself included ) who would want to do that.

Sorry Horst, as I had to get this project finished, I have removed the module for now so cannot give better info. Will definitely try to do so on a new project though. Thanks again for all your hard work!

Hi Horst, like Felix I've been running into serious performance issues when using 2.5.18. I'll try rolling back a version - am sure you're already aware of this. Thanks.