lassial358

I also have issue with another plugin.

Which URL is your problem at?

Hi,

I can’t give a full account, but please note that many picture sizes are automatically created so probably already have square thumbnails on your system.

Adit,

Using Chrome Dev tools you can figure out what’s causing the problem. Inspect the element, under Elements tab, check subtab Computed and filter for text-align

Okay.

I forget to mention that W3 Total Cache minification actually includes combining manually listed files in the user defined order (i.e. concatenation).

However, this issue was not solved, although I dislike the fact that I have no idea why it broke down; I have minified 25+ JS files (sic!) without problems.

Anyhow, I’m quite pragmatic so I’ll move on to other changes and optimizing the mobile view headers next…

Okay, thanks for the tip.

I now un-minified

https://saunologia.fi/wp-content/themes/tiny-framework/js/navigation.js?ver=2.2.0
https://saunologia.fi/wp-content/themes/tiny-framework/js/functions.js?ver=2.2.0
https://saunologia.fi/wp-content/themes/tiny-framework/js/skip-link-focus-fix.js?ver=2.0.1

with the desired effect!

However, I want to minify as much as possible so I need to take the files back to minified JS package one by one to see when it breaks.

I think this feature is very unintuitive; why should JS interpretation fail only in mobile devices!?

Thanks Tomas,

However, I was unable to reproduce that even with your Firefox tip.

I have not touched that .JS file. I suspect this might have something to do with the W3 Total Cache plugin JS minification and wrong inclusion order of JS files.

The only JS changes are in the child theme’s JS
https://saunologia.fi/wp-content/themes/sauna-tiny/js/custom-scripts.js?ver=2.2.0

I also double checked my customized Child CSS for any properties which might conflict site-navigation, but I don’t see anything.

https://www.saunologia.fi/wp-content/themes/sauna-tiny/style.css?ver=2.2.0

Mysterious.
If I get my Anrdoid device recognized in Chrome Desktop I may get somewhere.
I checked the order and dependencies, finding nothing wrong – as well as the fact seems unlikely to create that kind of behavior. The impossibility of debugging this in development browser makes this very inconvenient.

Thanks Thomas for the reply,
however, it didn’t quite help.

Luckily, I finally remembered what I did for the homepage; modify content.php and lines 78-80 which for me now contain

<?php if ( is_search() || is_home() || is_category() ) : ?>
<?php tinyframework_excerpt();?>

that is, forced excerpt for Search, Home and Category pages. The is_category rule was added.

However, I don’t think MORE is the best solution.

At least I use a separate SEO plugin (All in One for me) and write 150 ch descriptions for the articles – that’s what I’d ideally like to use. I think I could try that next when I have the time to do it.

Finally got around to finish this.

Only change to the code posted above required to get this working is replacing

wp_add_inline_style( ‘twentyfifteen-style’, $css );

with

wp_add_inline_style( ‘tinyframework-style’, $css );

because the twentyfifteen-style is naturally not enqueued in Tiny.

Additionally I suggest the following style definitions, which you could place in style.css:

/* thumbnail navigation backgrounds @lassial*/
.post-navigation .nav-next, .post-navigation .nav-previous
{
padding: 1.5rem;
background-size: cover;
text-shadow: 1px 1px #000;
}

Okay, good to know.

Too bad about the Photon – although AFAIK, my installation seems to be working, at least I can’t say there’d be any other problems with the featured images I’d yet discovered (but didn’t find anything from Jetpack change log regarding the bug since 3.7.0)

You’re right, the POT file from GlotPress is different, which probably explains the difference.

Seems that I didn’t quite grasp the way you translate the strings, but this is irrelevant if it starts working after the future update!

I investigated this for a half an hour. I found the code snippet required to generate the CSS but didn’t have the time to figure out how to inject the inline CSS to HEAD in order to get it working.

This is from 2015’s functions.php :

function twentyfifteen_post_nav_background() {
if ( ! is_single() ) {
return;
}

$previous = ( is_attachment() ) ? get_post( get_post()->post_parent ) : get_adjacent_post( false, ”, true );
$next = get_adjacent_post( false, ”, false );
$css = ”;

if ( is_attachment() && ‘attachment’ == $previous->post_type ) {
return;
}

if ( $previous && has_post_thumbnail( $previous->ID ) ) {
$prevthumb = wp_get_attachment_image_src( get_post_thumbnail_id( $previous->ID ), ‘post-thumbnail’ );
$css .= ‘
.post-navigation .nav-previous { background-image: url(‘ . esc_url( $prevthumb[0] ) . ‘); }
.post-navigation .nav-previous .post-title, .post-navigation .nav-previous a:hover .post-title, .post-navigation .nav-previous .meta-nav { color: #fff; }
.post-navigation .nav-previous a:before { background-color: rgba(0, 0, 0, 0.4); }
‘;
}

if ( $next && has_post_thumbnail( $next->ID ) ) {
$nextthumb = wp_get_attachment_image_src( get_post_thumbnail_id( $next->ID ), ‘post-thumbnail’ );
$css .= ‘
.post-navigation .nav-next { background-image: url(‘ . esc_url( $nextthumb[0] ) . ‘); border-top: 0; }
.post-navigation .nav-next .post-title, .post-navigation .nav-next a:hover .post-title, .post-navigation .nav-next .meta-nav { color: #fff; }
.post-navigation .nav-next a:before { background-color: rgba(0, 0, 0, 0.4); }
‘;
}

wp_add_inline_style( ‘twentyfifteen-style’, $css );
}

add_action( ‘wp_enqueue_scripts’, ‘twentyfifteen_post_nav_background’ );

I understand the limitations, in this case, just adding two words in

simply create your own tinyframework_comment(),

to

simply create your own tinyframework_comment() to functions.php,

would have solved the confusion.

Thanks for the compliment on customization, I’m still in the process of tweaking the theme, but please feel free to reference it after February once the site officially launches!

Yes, I understand this is quite difficult to come up with any good general purpose identifier.

Customization is thou quite easy if you use this reference:
https://fortawesome.github.io/Font-Awesome/icons/

and the customize the CSS, e.g.

.entry-header .entry-meta .posted-on:before
{
	content: "\f073";
}

Okay,
I have emailed you with the .PO and .MO files I currently use. I admit that I changed the “Using” string translation in my local setup as the rendering in footer was really odd.

As I see it, anything beyond freemium is premium. There’s a clear business in selling premium and I respect your decision to not appear as a merchant.

Nevertheless, I’m in!