compatibility with Falive theme & issues

I don’t see a link to download the source code in the link you’ve provided.

https://themeforest.net/item/falive-beautiful-creative-fashion-blog-theme/11640640

this download will cost me $49

yeah, how can I help you? I’m not sure I can download and send you the files since is are under their copyright probably.

Anyway looking inside the Falive theme folder for a POT file i notice the sub folder language are named lang

wp-content/themes/falive/lang/falive-themes.pot

Is that the problem? (rif. https://localise.biz/help/wordpress/translate-plugin/beginners point 4 says: “Looking inside the Omega theme folder we can see a languages sub-folder containing a file called omega.pot. […]
wp-content/themes/omega/languages/omega.pot
” )

The child folder doesn’t contain any lang\language folder or pot files

If you need more info let me know, I asked to falive theme support if the theme support Loco, I’m still waiting.

nothing wrong with the folder name “lang” as long as the theme declares this is where files are to be found. This is done in the style.css header Domain Path declaration.

Thanks Tim,

here is the beginning of style.css of Falive theme, it doesn’t contain any domain path:
Shoud I add it to myself? Could you please tell me the exactly what to write and where?

Thank you very much for you help!

/*
Theme Name: Falive
Version: 1.1.1
Theme URI: https://themeforest.net
Description: Multi-purpose Fashion Blog Theme
Author: Jegtheme
Author URI: https://jegtheme.com/
License: GNU General Public License v2.0
License URI: https://www.gnu.org/licenses/gpl-2.0.html
Tags: light, right-sidebar, fluid-layout, responsive-layout, custom-menu, featured-images, theme-options
*/

Try adding:

Text Domain: falive
Domain Path: /lang/

Replace “falive” with whatever the text domain actually is. If you don’t know, ask the author.

Thanks again for your kindness Tim

I did what you said, I asked also to the theme author off course and he said me to remove the code you gave me.

The conversation is here: https://support.jegtheme.com/forums/topic/translate-problems-with-upgrade/#post-19508

I know is not completely under your control and responsibility to help me futher, but I reaaly appreciate if you cold read that and give me your opinion.

After that I’ll consider this ticket as solved no matter what happens.

My best

Tommy

Version 2.0 introduces theme configuration options that allow you to declare those headers tags without modifying the theme files: https://localise.biz/help/wordpress/translate-plugin/developers

If your theme vendor would like to make their work more compatible with Loco translate, please send them to the following link: https://localise.biz/help/wordpress/translate-plugin/authors

If your problem persists in v2, please start a new topic. I’m closing this as support for v1 has ended.