Hi!
I am just starting to implement Newspaper on my site and I am a bit confused, hope you can help me out here 🙂
I am setting up a multi-language blog and I need to have separate theme options (individual theme panel settings) per language.
I am using WPML (all my settings and posts are already based on that so I cannot move to qtranslate (I noticed you may have a bit more experience there) but on themeforest it says Newspaper is WPML compatible and I am hoping that’s true…
So, I am not sure if it’s something in my settings or something missing in the theme code but when I make a change setting in one language – it’s happening to all which is not what I need to happen.
(A previous theme I used from themeforest was doing that individual theme panel per language thing perfectly and from what I gather this is part of the WPML compatibility factors).
I noticed in Newspaper theme directory you have a sub called “translation” and I think WPML expects to find “languages” as well as a few other differences in file names and maybe inner code integration things…
Hope there is a simple solution to all this, please give some instructions and / demonstration on how this is supposed to work.
Since no new info posted here are some of my findings so far which I need your input on ASAP:
* Similar issue on WPML forum – http://wpml.org/forums/topic/how-can-i-translate-theme-options-content/
* From the response – this may be the missing link http://wpml.org/documentation/support/language-configuration-files/
(I did not see you include wpml-config.xml)
I am not sure why you listed the site as WPML compatible, but what I need is separate option panel per language to set:
* different header (image logo & text per panguage)
* different footer
* different template settings – to account for RTL / LTR on non category pages
* different translations – since it’s DIFFERENT LANGUAGES obviously…
* different Custom CSS
(Of course you can do a complete compatibility – but the above is a must!)
hi,
the theme panel was not made for multilanguage, but take a look here :
https://forum.tagdiv.com/translate-your-site-in-multiple-language-with-qtranslate-plugin/
maybe it helps.
Thanks for you message.
Radu A.
Thanks for answering Radu.
Since your theme is listed as compatible with WPML (which stands for wordpress multilanguage and is a very specific plugin that is NOT qtranslate) – I suppose you can understand why my expectations where different…
For a people who paid for WPML and already use it – moving to qtranslate is no simple matter since WMPL / qtranslate encode posts and stuff very different and migration is a b!tch 🙂
For now, I think I found a few workarounds – BUT I noticed in some cased your theme does separate options per language (for example in the top menu selection and in the categories section) – so that means you know how to do it, you are simply not following through in the same standard and I think that if did – your customers would get much more value from the theme…
I am trying to work with what you have at the moment – hope i don’t hit a brick wall and have to find a theme that did a better job in the multilingual aspect because I really like what I see so far.
Im in the same situation here.
I didn’t know about qTranslate before purchasing WPML for 199$! since I saw on themeforest
Compatible With
WPML, BuddyPress 1.9.x, WooCommerce 2.0.x, bbPress 2.5.x, Bootstrap 2.3.x
Only to find out now, that it is compatible but not supported.
I’m having similar issues as @virtualida with the menu selection of the different languages.
Where are we to put the Language selector? Can we get some assistance or a how to on this matter?
Hi,
Unfortunately we can not offer support for WPML, you can look for documentation on their site http://wpml.org/documentation/
An alternative would be to use qTranslate, here you have some tips on how to use it: https://forum.tagdiv.com/translate-your-site-in-multiple-language-with-qtranslate-plugin/
Also we will remove the WMPL compatibility statement from theme’s presentation page, we will put it back when the theme will be fully compatible with WPML plugin. For now unfortunately we do not have time to work on this project but we have it on our list and we will try to remediate this as soon as possible.
If you are unhappy with our theme we can offer you a refund.
Sorry about this.
Thanks for your message!
Yea…
That’s the answer I got after spending much time adjusting my implementation to the theme… not a high priority at this point for Tagdiv 🙁
Well, the good news for you @mo-tech is that I was pretty stubborn this time and followed up with WPML trying to find all sorts of workarounds for the things that troubled me so I might be able to give you a few tips if I know what you are trying to accomplish.
(With their 199$ version – chances are you can get the Multilanguage aspects – maybe not from the theme panel but using the string translation features).
BTW
In expressing my frustration from the above via the review @ Themeforest, certain members of Tagdiv support seem to have gotten the impression they can “excommunicate” and avoid providing support on my tickets…
Be AWARE | Choose WISELY | Stay TRUE
🙂
@Lucian I must admit you gave the BEST and WORST response possible.
The best: simply because you admitted that
“Unfortunately we can not offer support for WPML”
which basically tells me to stop asking questions with regard to WPML.
The worst: because I purchased your theme, purchased WPML, invested HOURS to configure everything to be only let down that you will
remove the WMPL compatibility statement from theme’s presentation page
as well as
If you are unhappy with our theme we can offer you a refund.
I know where I stand now, I have no real choice but to continue developing on what I have, I have invested too much time to switch themes now, and WPML is at least supported by their developers whereas qTranslate has no guarantees since it’s free.
@virtualida I would definitely appreciate any help you can give me, we can keep it here in an open forum or switch to PM, whichever you prefer.
What I need to know is how to add the language bar to the MAIN MENU and have it take the proper CSS styling. Have you done that?
I suppose HERE is good since we are paying customers and this forum IS supposed to offer a place for support…
+ maybe others can find it helpful in the future as well, who knows…
My main menu with WPML language switcher: http://screencast.com/t/JY2sLaaQZHtH
Well, putting the language switcher on the main-menu:
- You set the main-menu on the theme panel > header > Main Menu > Header Main Menu <br>
- You can verify this on Appearance > Menus > Manage Locations (but I think it syncs automatically)
- WPML > Languages > Language switcher in the WP Menu <br>
- Check “Display the language switcher in the WP Menu” & choose the same menu you set for the main-menu
- Do all that for the default language that you set for WPML originally & use “WPML > WP Menus Sync” to keep the menu’s sync across languages (where needed).
As for the CSS modifications, add the following to your custom CSS on the theme panel:
/* Menu Language Switcher */
.sf-menu .menu-item-language > a {
display: inline-block;
}
.sf-menu .menu-item-language > a {
text-decoration: none !important;
}
.sf-menu .menu-item-language > a {
display: block;
position: relative;
}
.sf-menu .menu-item-language > ul.sub-menu > li {
direction: ltr;
text-align: left;
}
.sf-menu .menu-item-language > ul.sub-menu > li a {
padding-right: 29px;
min-width: 1px;
padding: 0px 11px 0px 11px;
height: 48px;
line-height: 51px;
font-size: 16px;
color: #202020;
z-index: 9999;
}
.menu-item-language img.iclflag {
margin: 0 4px;
}
/* Menu Upgrade */
There’s a bit more if you are using RTL language…
-
This reply was modified 12 years by
virtualida. Reason: adding some image links to show what it should look like
ahhh… crap
tried to edit in some images..
here:
(#1) Menu setting on theme panel
http://screencast.com/t/IAW5flWpy5Wl
(#2) Menu setting on WPML
http://screencast.com/t/fT0aEXTLxs
End result:
http://screencast.com/t/JY2sLaaQZHtH
-
This reply was modified 12 years by
virtualida.
I have set per language a new homepages and a new header templates.
But the all homepages only show the header template assigned in theme panel.
It is because the theme option is still not translatable. I can only set the header and footer templates to one of the language. The theme option setting overrides the translation system in WPML.
I migrant from Polylang to WPML with your ‘compatability’ statement. I really hope to know how to solve it
Hi Jaco, please reply in this topic -> https://forum.tagdiv.com/topic/newspaper-theme-unable-to-translate-theme-option-with-wpml/