DaveP

I think PW has you covered there, There's a Content-Type select on the Files tab for each template. The note underneath says 'To add more content types see contentTypes in /wire/config.php (and add them in /site/config.php).'.

Lovely looking site. First thing I saw was Bradley Wiggins. One of his gold post boxes is a couple of hundred metres from our office. Small world.

Hmmm, PHP 6? Really? AFAIK not an officially supported version. (Google for more info.) You would probably be better served with 5.6 or maybe even 7. Anyhow, GD support is pretty much a requirement for most hosting. PW uses it to resize/crop images. The combination of PHP 6 and no GD throws real doubt on the competence of your hoster,

Which, in plain vanilla PHP is $pageID = abs(intval($id));

https://www.cloudflare.com/ddos/

If you have control over your nameservers, it's a complete non-issue. You just configure CloudFlare to point to your hosting, and point your nameservers at CloudFlare. For historical reasons (ie I didn't know any better) all my own domains are with Godaddy, while my hosting is elsewhere (currently vidahost, who have been excellent in the couple of years I have used them and before that nearlyfreespeach), and CloudFlare sits between them nicely. Even with the free account you get end to end encryption (CF accepts a self-signed cert for traffic from your server to them and provides a free cert for traffic from them to the browser), HTTP2/SPDY, minification, automatic injection of GA scripts, email obfuscation, CDN features and a whole slew of other stuff, even on the free account. Feel free to visit my blog which uses CloudFlare (link in sig) and have a sniff around. There's at least one post on there specifically about using CF with PW sites.

Just a couple of observations - In the first image they say they scraped your site December 31, 1969 at 6:00pm. That implies a problem, as it is very likely the Unix epoch in your time zone and suggests to me a problem at their end. The other thing is somewhat minor, but one thing that you might want to address. That is standardising on the www or non-www URL for site and assets. You can enforce one or the other through .htaccess and, while it might have no bearing on current issues, is generally a Good Thing.

Could use some help from AIOM.

Are you sure the files aren't compressed (.tar or .gz or the like)? If they are PW core files, check if file sizes compare to those on git.

Tricky to say for sure, but if you are lucky it might be a failed restore from a successful backup. Are permissions on the /site/ folder as you would expect?

+1 for that.

Just for the record, I ended up using leaflet.js instead.

First, take a look at the docs on pagination, if you haven't already done so. Important thing to remember is that you need to enable pagination in your parent template (/galerie/) in the case of your example, or in the case of a shop perhaps /produkte/. If it is for a shop, then each product should probably be a page, but you can paginate images just as easily. (And if it is a shop take a look at this.) If you get stuck, come back here and ask some more.

Looks as if you have an entity encoded ampersand in there - terminio.at//en/social-login/?hybridauth=login&hauth.done=Google <edit> and a double slash (.at//en) </edit>

This is sweet. And sooo easy to add to any PW site. http://blog.watchandcode.com/2016/03/17/the-single-piece-of-javascript-on-hacker-news/

http://getuikit.com/docs/flex.html

Cured it for me.

Material Design Lite - http://getmdl.io/ - is quite interesting. One of the best-documented projects of the type that I have come across.

I'm getting a strange double vertical scrollbar. Chrome, Win7, 1600x900 <edit>The scrollbar in the image is the extra one, the 'normal' one wasn't in the screencap.</edit>

Thanks, guys. It's cloud hosting, so everything is all over the place anyway. This page gives a bit more detail, and shows how WP can be configured to use such a setup. Would be nice if PW did something similar. Just a bit of background - it's going to be a new site of my own, and be very image intensive. And as it's my own, it'll be PHP7 and PW 3 dev. (So I'll be using lots of your stuff Horst ) Yup, that was my fear. That said, I'll have a look at the module Horst linked to.

I know that files are usually stored in \site\assets\files, but my hosting has the option available to host such content on a static subdomain, served by an NGINX cluster. So what I am asking is, instead of files being stored at example.com\site\assets\files, is there a way to have them stored on a different url eg. at static.example.com\site\assets\files? ​Is there a way through site\config.php, or through hooking something(s), or would the change need to be in the PW core? Or something else?

Competing with WP is a dead duck. The things 'missing' from PW are completely absent from CodeIgniter, CakePHP and Laravel as well, but those three have waaay more 'market share' than PW.

Similar problem, but I'm getting a 403.

Not sure if I understand your question exactly, but <?php echo $config->urls->root.$page->headerImg->url; ?> would produce a fully-qualified URL.

Guilty as charged,