Adam Kiss

You could escape the values with 'htmlentities' — either manually or automatically via custom TextFormatter. --- Edit: Or it's possibly something else; I've just $cache->saved an array with string with acute in it and had no problems.

I never worked with Typo3, but is it possible that both have class Template, and when you call Template::SomeMethod(), Typo3's class is picked up?

I'm currently building small Page Label enhancement. Can you tell?

Very nice.

That is fast. Good work.

1. Is "$name" defined in the ./functions.php file? Because in the quiz.php, you don't populate it with anything. 2. in the quiz.php, when you generate the hidden inputs, you output "$name[$x]". You should output "{$name[$x]}" (note the curly braces) to output value of $name at position $x. That's what I could think of after quick read-through.

Is it possible that 1023 and 1024 were created at the same moment? Because in that case, sort=sort acts like sort=created|id and sort=-sort would be sort=-created|id, this your real order would be something like (1023, 1024), 1031 and 1031, (1023, 1024). (This is just a pseudocode, afaik there isn't anything like sort=created|id)

I use Gulp, but the difference is just in syntax; You can see my assets directory here: https://github.com/adamkiss/StarterKit/tree/master/Assets I use it this way (Gulp-ing from /Assets/src) so I can ignore whole source directory when deploying and git/rsync/git-ftp only the distilled directory.

Nice. I can redirect everyone here now, instead of fiddling with my own FYI, image upload was really really hacky, but the relevant coffee script is here: - event: https://github.com/adamkiss/InputfieldAceEditor/blob/image-upload/_coffee/modules/editor.coffee#L50-L59 - method: https://github.com/adamkiss/InputfieldAceEditor/blob/image-upload/_coffee/modules/editor.coffee#L73-L94

<?php $last = $pagearray->pop(); echo $pagearray->implode( ', ', 'title', ['append' => ' & '] ) . $last->title;

If we compare it to editors, Ace Editor was never meant to be the Sublime Text of Inputfields, more like iA Writer/Byword of Inputfields. If I ever clean up the code (its current state is total mayhem, because I've been working on it a bit every two months… and everyone knows how well that usually turns out). Maybe, if I ever clean it up and prepare it for latest PW (although it sort of works), I could make it to the point where it accepts custom CSS or something, but it's not really on my radar. I'd much rather finish other dreamt-up things, like fullscreen, etc. Sorry.

OH MY GOD. WHY? Well, with drama out of the way, if it's somehow obvious in the code, maybe… I once inherited an application to fix — I spent two days looking for where the hell application does routing, because it was borked. And then I found 4k lines long 404 handler named "error_fix.php", which dealt with bunch of things, routing (nice urls) included. Please don't do this.

Nice, it's even usable on desktop. Much obliged!

No problem. Ramble away I'll ramble as well. They are not necessarily "simpler". It's not so much about simplicity in the sense of "dump markdown and done". It's about defining everything in the plain text. I can try to give you an example between Kirby and PW: You have two pages on the site: PageA and PageB. Both are just a content with sidebar. Now you need to add three rarely updated news just for PageA, into the sidebar. In ProcessWire: ([A] is admin, [E] is text editor) - [A] create new repeater with the fields - [A] create new template - [A] add repeater to template - [A] change template on PageA - [E] add HTML and data output - [A] input the data to PageA - [E] design it with CSS - AH! You need to add a date - [E] change the HTML - [A] add the date to repeater - [E] fix the CSS - done. In Kirby: all is in [E] - the editor - add YAML structure with news - add HTML - add CSS - AH! add a date! - add YAML data - fix HTML - fix CSS Disclaimer: of course, your process in PW may be different, easier even. For larger sites, more content-heavy (templates are reused tens, hundreds or thousands of times) sites, or sites where the structure is well defined at the time of creation, it makes a lot of sense to go for the more robust solution — be it PW or something else. But then there are projects like I do; You get a site's goal, and you make up things as you go. I create the rough design idea in PS/Sketch, and then go straight to code, to finish the design, code it up, define content structure and add content. For these projects, you go through the example hundred times, because the process is much more fluid. Then add up possible incompatibility with you workflow, having to manage DB sync during changes/uploads, and you get frustrated with the more robust solution very quickly (possibly in the matter of days). For the projects I usually deal with, images are used either as a part of general design, or in some sort of gallery, which is just image+thumbnail. --- Just to finish the thought: I, both as a person and as a creator, tend to ask 'Why do you want this? Why do it this way?' a lot. This often leads to simplification of the scope and removal of features, because they were requested because "I heard it's good to do X", and not because they are needed for the goal of the site. Your clients, projects and workflow might be wildly different.

I don't quite understand what you mean? I just need to show them, right?

Yes, of course. File extension removal is actually feature I don't really care about. More the features you'd use in ProcessWire, just on smaller scale: - templates, not having to edit 20 files when you change a bit of html structure (especially during initial design/coding stage) - navigation generation - Collections of stuff (so you can write one html and just foreach it) - Having data in a nice structured YAML format, decoupled from HTML I'd go mad if I had to do that stuff in pure HTML. Hey, no problem.

@pwired, I don't understand? I do small projects. As for Get Simple, I tried to use it few times, but it actually doesn't make sense for me: in smaller projects I do not want to deal with any administration or wysiwygs, just HTML, CSS and Markdown for content. For larger projects, PW is better. Get Simple doesn't have use case in my situation.

I mostly use Kirby, which is a lot like ProcessWire, just smaller and flat file. I remember experimenting with outputting PHP files from Middleman during build process, but do not remember if I was successful or not. Also, some contact forms were originally requested "just because people use them", so those are discarded, if not meaningful.

Hey, I don't mind necroing my posts if it coincides with my resurfacing on the forums The thing is, you all assume it's just about the speed of the site — the "staticness" of the content. But in my case — which I admit might be far from yours — is that I often deal with tiny, even time limited websites, like website for an event. They usually have just a few, maybe five totally different pages, are active/online for limited time, and I am probably the only person interacting with it. So when you take all of that into account, having both the data and the templates in the text editor, and not having to deal with neither database nor any kind of administration immensely speeds up my workflow. When adding a 'field' is a question of one YAML line versus multiple clicks in (even well designed ProcessWire) administration, there really is no question.

WHAT IS THAT FONT? It's gorgeous.

How does that sound?

It's always fun tweaking these things! This one's mine:

I use the 'when I need it' approach – I don't have any value predetermined when I start with the design – it's little less tidy (the css is minified anyway), but the content likes it

SEO Module? What is this? 1999 again? But seriously:

Happy birthday to Ryan