Forum Replies Created
-
This content is restricted to customers with active licenses.
You’ll need to push this to .htaccess file, since it’s probably a hosting configuration issue. It shouldn’t add anything to before your post’s slug, neither blog nor nieuws.
Great. Please share ;)
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
The filter in this case is ‘nav_primary_before’, which is documented.
10 is a filter importance (10 is default and neutral). If you would hook another function to this filter with 9, it would be taken instead.
2 is a number of accepted arguments for the hooked function. In this case, there are 2 arguments hooked in, first one is $menu and second one is $args.
I hope it’s more clear now, do let me know if you need more guidance.
How did you setup your blog page? – via page template or Settings / Reading as a static posts page?
You should be able to control the permalinks for this inside Settings / Permalinks. Make sure .htaccess file is created after you’ve changed your posts permalinks Custom structure. I usually recommend using only ‘Post name‘ as a permalink structure as this is more SEO friendly.
No, add this:
remove_filter( 'nav_primary_before', 'bizznis_mobile_right', 10, 2 );
You also need to remove the mobile menu CSS styling from your child theme’s style.css file.
Open your blog page and change the slug, simple as that. Pick Blog template for that page.
You have a sharp focus :) …
Fixed it and will add it to next theme release. In the meantime, replace this inside lib/frontend/search.php:
esc_attr__( 'Search this website', 'bizznis' )
with this:
__( 'Search this website', 'bizznis' )
In other words, just delete second “esc_attr” on line 15.
Nothing is wrong with the original string itself, but your translated string is missing this in it:
homepage
Add it somewhere in your translation and it should work. Of course, you can translate the ‘homepage’ text, but add the rest of it.
I’ll look into this. Thank you for reporting it.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
This content is restricted to customers with active licenses.
I see your point.
As Bizznis is a parent theme, you can override every file with your child theme, language files included. Here’s what you have to do in order to keep your Bizznis powered website translated even after updates.
- Go to your active child theme folder and create a folder called languages.
- Upload your translation files (your .mo and .po files) to the languages folder you just created.
- Next up, we need to tell Bizznis we want it to look for translation files in your Child Theme folder instead of the Bizznis folder. We need the following code pasted in your Child Theme’s functions.php:
// Child Theme Language override
define('BIZZNIS_LANGUAGES_DIR', STYLESHEETPATH.'/languages');define('BIZZNIS_LANGUAGES_URL', STYLESHEETPATH.'/languages'); - This snippet needs to go before the following code:
load_template( get_template_directory() . '/lib/init.php' );
but after the opening
<?php
That’s it. Now your site will always remain translated. Do keep in mind that a bigger Bizznis update (e.g. from 1.0.x to 1.1) will probably contain new untranslated texts in the new Bizznis .po file found in the /lib/languages/ folder.
This content is restricted to customers with active licenses.
