teppo

There's a closed issue related to this at GitHub; magnific popup has replaced fancybox in dev branch. This issue has also been mentioned here before. On a mobile so I can't link to related posts right now.. try Google search if forum search returns nothing useful

@Manol: might want to check this GitHub issue out. Looks like something somewhere has changed and all 3rd party admin themes may not be entirely up to date, possibly related to your issues here. By the way, have you made sure that you're running latest version of Futura?

@lundy: congratulations, you've nailed it. That's a very good way to describe it Of course it's not literally quite like that. Since you've mentioned that you're a beginner, it might be useful to know that there's a lot more happening behind the scenes: Each page is connected to a template, which is connected to a fieldgroup and each fieldgroup is connected to varying number of fields. Taking things even further, each page is represented as a row in pages table, each template as a row in templates table, each fieldgroup as a row in fieldgroups table, each field as a row in fields table and so on. Eventually each row of data you've filled on any of your pages inserts a row in that particular field's own database table, i.e. field_title, where column pages_id identifies the page this particular row is related to and column data contains actual title field content for that page. Field tables can have varying amount of different columns, but this is the basic setup anyway. Understanding how things are connected at database level IMHO makes them more obvious on the front end side, but for most use cases (and most users) knowing what you already know is quite enough. It's still good to realize that there's a lot more to a system like this than just simple database table with couple of columns and rows Each question as it's own page does seem the most obvious solution here. Of course this still depends a lot on your specific needs; are these questions just simple question-answer type of things, how much data is there going to be for each of them, do they have comments or votes etc. Ryan recently published an events field, which could also easily be modified to accommodate very simple question-answer-pairs.

@pwired: if you want to create your own starting point, take a look at http://modules.processwire.com/modules/process-export-profile/. ProcessWire blank profile already mentioned above is available at http://modules.processwire.com/categories/site-profile/ (among other options).

Hi! On a bit of a rush here, just some short answers: Yes. PageArray, when treated as a string, should look like that. See PageArray->toString() for more details. You can access specific items with $pagearray->eq(0), $pagearray->eq(1), $pagearray->first(), $pagearray->last() etc. or iterate it with foreach. Through API or via admin UI? Both should be doable, admin UI has "copy" link and http://cheatsheet.processwire.com/ provides details for API side (tip: look for "clone" method from Pages or PageArrays.) No, created date tells when page was created, i.e. added

@Ryan: not sure if you've included that in your version, but you might also want to avoid minifying content within pre tags. Personally I'd also leave script tags alone. The minifying solution I used as basis for example code in my hooks blog post didn't originally account for that, which is why it blew my site apart under certain specific conditions. Could've avoided this by altering embedded scripts, but it felt safer to simply skip them. If I really wanted to minify JS, I'd rather use a service built for that -- better results, fewer issues

@everfreecreative: make sure that you've got the latest version from GitHub. This bug was supposed to be fixed a (short) while ago.

I'm not entirely sure what you're asking here, but still: ProCache won't affect any other aspect of these page speed tests other than server response time. Expires headers, page structure related stuff, minified scripts & styles & markup etc. still apply. Your content just gets served from files on disk without PHP and/or MySQL slowing things down. So, did this answer your question?

This is kind of related to this issue and this commit at GitHub: it sounds like Fancybox has problems affecting IE10 and since Fancybox is being replaced by Magnific Popup in 2.4 these issues should be solved at that point. Another question entirely is whether it's worthwhile to fix Fancybox issues in current (stable/master) PW release.. Oh, and no worries, Joe; your IE-situation is very familiar