patrikelfstrom

Hi Danny. Yes it works beautifully now! Thanks!

It was a few month now so I don’t know if the bug is still there but it probably is.
I don’t have time to check on it right now so I’ll just send you the version I’m running and I’ll test it in a few hours when I’m back.

$ curl --version
curl 7.40.0 (x86_64-apple-darwin14.0.0) libcurl/7.40.0 OpenSSL/1.0.2 zlib/1.2.8 libidn/1.29
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP UnixSockets

Array
(
    [version_number] => 468225
    [age] => 3
    [features] => 33469
    [ssl_version_number] => 0
    [version] => 7.37.1
    [host] => x86_64-apple-darwin14.0
    [ssl_version] => SecureTransport
    [libz_version] => 1.2.5
    [protocols] => Array
        (
            [0] => dict
            [1] => file
            [2] => ftp
            [3] => ftps
            [4] => gopher
            [5] => http
            [6] => https
            [7] => imap
            [8] => imaps
            [9] => ldap
            [10] => ldaps
            [11] => pop3
            [12] => pop3s
            [13] => rtsp
            [14] => smtp
            [15] => smtps
            [16] => telnet
            [17] => tftp
        )

)

3x photos i can understand but icons/small images will still be blurry even if they are 2x.

What about an option that allows advanced users to define their own pixel ratios.
So as default only 2x is enabled but if the user want he can enter multiple custom pixel ratios in a textfield (or something to keep it simple).

Something like: http://i.imgur.com/5UxJPGO.png

function override_translation( $mofile, $domain ){
    $plugins_to_move = array('jetpack');

    if( in_array($domain, $plugins_to_move) ){
        $mofile = WP_LANG_DIR . '/plugins/' . basename( $mofile );
    }

    return $mofile;
}
add_filter( 'load_textdomain_mofile', 'override_translation', 10, 2 );

I went thru the code and found this in models/monitor.php:30:

if ( $post->post_status != 'publish' || is_post_type_hierarchical( $post->post_type ) )
			return;

The first bit; If the post_status of the post is not publish don’t create a 301-redirect. Which makes sense since you don’t want users to get redirected to posts that are not public.

The last bit is something I am more curious about. is_post_type_hierarchical( $post->post_type ) checks wether the post type of the post is a hierarchical one. If it is, don’t create a 301-redirect.

A regular post is not hierarchical but a page is. So the automatic 301-redirect will only work on posts and not pages.

Can anyone tell me why it’s like this?

Anybody, Please, my client/boss is getting pissed.