Saskia Teichmann

Hi again! thanks for checking it out.

I retried with cleared cache (included deleting cookies): no luck.

Retried with another browser: firefox instead of chrome. no luck.

I am being redirected to an empty white page:
[url redacted]

WP user login data sent to your email jeremy@ yourwebsite domain!

Thanks Jeremy!

I found the culprit!

On my server was an nginx directive snippet in place which caused firefox to stumble over its feet while interpreting Cache-Control which was sent by my nginx.
The problem was that wrong quote marks were used to wrap “public” in the following code snippet: ( these were the wrong ones: ″ )

location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
    expires 30d;
    add_header Pragma public;
    add_header Cache-Control "public";
    try_files $uri @fallback;
}

Firefox showed broken Cache-Control definitions. Instead of these correct ones:
Cache-Control: “max-age=2592000, public”
something like this was shown (unfortunately I didnt save the exact interpretation):
Cache-Control: “max-age=2592000, ?public?”

Chrome didn’t have a problem with the other font quotes and therefore never showed that behaviour.

Also did I find that mod_pagespeed which was activated on that server was causing caching problems.

Funny thing is, I installed a site on a client’s webhosting which is just a shared webhosting with german STRATO. Same caching problem occurs over there.
They might have this very nginx directive in place also with those wrong quotes that can’t be interpreted correctly by firefox. MAybe even also installed mod_pagespeed which is not fully configured.

@csonnek : I just moved my site to a new vserver. That is maybe why you weren’t able to access my website. The moving processs should be finished by now. It was started friday. DNS entries should be published globally now.

@jeremy thanks for getting back to me! Ok I am awaiting the fix!

What about it? still no option to exclude referrer spam

—
I tried the Ignore URL text input area to exclude those spam referrer urls manually. However the text that is being typed into the the box does not save out.
for example:

video–production.com
success-seo.com

click update options

then box is empty, nothing is saved.

Thanks for that info ??

Thank you, Jeremy!

Is there any update on this? On mobile devices it is really hard to get rid of the map lightbox without a close button to touch

Ah thanks.

Well I solved the “issue” by installing Foobox Pro.

Github filter request added
https://github.com/Automattic/jetpack/issues/2194

Thanks Jeremy!

I do not know how, but I got it to work finally. I think.. at least it hasn’t happened anymore today.

Among the things I did today:
I deactivated the infinite scrolling in jetpack. And I deleted the infinite scrolling plugin that enables infinite scrolling with twentyfifteen.

Not quite sure, that it was the actual reason for that behaviour, but it did not happen anymore after I did a whole couple of things, including the above.
Reason I think this infinite scrolling thingie was part of the cause, is that, the error only occured after browsing the site for a bit. AND after actually scrolling through any type of posts. It didnt happen right from the start with cleared cache, but it did happen when cache started to build and you’d scroll through the site with the above functionality enabled.

For now it is solved.

Anyone? As I said this behaviour occurs mainly when you use firefox/windows

Simply browse the website and then all of a sudden it happens. As long as you use a custom post type with own archive-customposttype.php

UPDATE:

The false behaviour of twenty fifteen re-occurred last night when I randomly clicked through the frontend on a firefox/windows PC.

It happened when I tried to access a single post site. Instead I was presented with the custom post type archive. -.-

WHY?

I thought, ok, WP looks for a single.php to display a post. In my child theme folder is no single.php located, because it is located as supposed to, in my parent theme folder.

So I copied the single.php, as well as index.php, search.php etc (just in case…) also over to my child theme folder.

After clearing cache, the single post was loaded correctly.

At first when I visit the site, with cleared cache, all pages are displayed as they should. I don’t get redirected to anything that should not be.

However when browsing the site, and I guess, when FF creates it’s cache, the error starts to occur.

Is there anyone out there who can help? OR knows what might be the reason for this weird behaviour of the theme?

Update:
I went through common WP troubleshooting steps. No luck.
Deactivation of plugins did not do anything to change the theme behaviour.
I deactivated the mod_pagespeed on my apache. Still no changes in theme behaviour.

Then I played with my custom post type a bit more.

This is what I did and now it works.. at least for now:
I corrected a typo in functions.php: capatibilitys…. lol. Then I decided to register the CPT via Plugin rather than child theme functions.php. So I wrote a small plugin to do the job.
I deleted the CPT registration function from theme functions.php

The weird behaviour stayed the same.

I then checked the templates once more.. I played around with file naming according to WP Codex. No luck.
For example when trying to access a page with slug ‘arbeiten’ or also my blogpage, it would redirect me to my CPT ‘termine’ archive. Or also to my page template ‘shop’.
I finally renamed the CPT archive back to archive-termine.php ( In the meantime while trying to find out what was wrong, I had named it termine.php , because I thought maybe better use it as page template…)

Still no luck. Same weird behaviour.

In the end, I thought, ok.. if WP checks step by step the page/post/archive templates and then ends up using the cpt archive or my custom page template, then the reason can only be, that it simply can not “see” the page.php, archive.php etc, which are located in the parent theme folder.

So I copied the page.php and archive.php from my twentyfifteen parent theme folder to my childtheme directory as well.
That did the trick.

Is that intended?
I think not, right? WP should check in parent themefolder as well as childtheme to decide which template to choose, doesn’t it?
So I believe there is something wrong with twentyfifteen.

Also the behaviour was worst in firefox. In chrome/safari on my Mac I could access the pages 85% without problems. At first I could not reproduce the behaviour because of this. Yes, I did get the behaviour in these browsers as well. However not as constantly. So I checked in firefox on my windows machine where this behaviour occurred reliably.

Sorry for the long post.

Is there a filter for the shortcode function output of [portfolio]?