rakaloah
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Oblique] Home posts not showing anymoreThe only symptom of masonry-init.js is “stacked” posts on the home page, the posts are there, just with a messed-up layout.
So if the posts are not showing, there must be something else happening. You can try pressing F12 (or right click and inspect) and check if anything was missing (e.g. HTTP 403/404/500 errors in Network tab after a refresh) or throwing errors.
Forum: Themes and Templates
In reply to: [Oblique] Update to WP 5.5 breaks the “recent posts” home page.@lacascinadellanima
You can simply view that .js file using your browser, like ‘example.com/wp-content/themes/oblique/js/vendor/masonry-init.js’.
If it’s still an old version, try to Ctrl-F5 (force re-download everything) a few times.
If that doesn’t work either, check your wordpress plugins with cache functionality, especially PWA ones (which requires a service worker force update), clear those cache.
And if you have CDN (since it’s a hosted service, I’m not sure about that), you may need to clear that cache too.Forum: Themes and Templates
In reply to: [Oblique] Update to WP 5.5 breaks the “recent posts” home page.Wordpress 5.5 updated its bundled Masory.js from version 3.3.2 to version 4.2.2.
Did some research on this and I found that Oblique uses'wp-content/themes/oblique/js/vendor/masonry-init.js'
to initialize masonry.In that file, the function
_getColGroup
:
var colGroup = this._getColGroup( colSpan );
was changed to_getTopColGroup
in masonry version 4, so just change that line to:
var colGroup = this._getTopColGroup( colSpan );
and Oblique works again.I love this theme but it has been abandoned by its authors.
Maybe it’s time to move on because who knows when it will break again in the future.Forum: Themes and Templates
In reply to: [Oblique] FontAwesome issue causing social icons blankBut wait, there’s more:
Widget icons are also broken because of this…Temporary fix is to add below to theme custom CSS:
.widget_recent_entries li::before, .widget_archive li::before, .widget_pages li::before, .widget_recent_comments li::before, .widget_categories li::before { font-family: 'Font Awesome 5 Free'; font-weight: 900; } .widget_recent_entries li::before { content: "\f303"; } .widget_archive li::before { content: "\f133"; } .widget_pages li::before { content: "\f15b"; } .widget_recent_comments li::before { content: "\f075"; } .widget_categories li::before { content: "\f07b"; }
It’s not about Chinese words, it’s about the translation itself…
Bundled locale file translates this placeholder text %1$s to its full-width form, which cannot be recognized by WordPress.You can see the difference between the correct ones and this full-width one:https://imgur.com/loks5HT
The fix is easy, copy the original text, paste into translation. One line in the .po file.
It looks like this: https://imgur.com/kAskRAS
It should be all half-width characters(%1$s) to function properly as a formatted string for category info, but it’s “translated” into full-width characters(%1$s) in latest Oblique theme zhCN locale.
I can manually modify .po file and compile it to fix this little bug but WordPress keeps revert it back after every update.Thank you guys for making this awesome and stylish theme, it would be perfect for my site after this little glitch gets fixed ??