Return to previous page

Several issues with the template regarding the translation/design

This topic has 74 replies, 6 voices, and was last updated 10 years, 5 months ago ago by mleihs

mleihs

Participant

December 17, 2014 at 17:37

Hi Olga,

thanks for your reply. I was going to look into this now but noticed that the theme update from last week featured

— snip —
FIXED: WPML compatibility
— snap —

Should I update the theme before looking into the translation issues?

Best regards

#30090 Copied

Eva Kemp

Participant

December 17, 2014 at 19:30

Hello,

Yes, you can update the theme but create a back up of your files and database before update.

Thank you.
Regards,
Eva Kemp.

#30116 Copied

mleihs

Participant

January 8, 2015 at 14:12

Hi,

thanks for the recommendation (@fuzzy). It worked out fine for the search box and the url slug: (see screenshot 1 )

I still wasn’t able to change “PROJECTS” within the breadcrumbs that way, though (see screenshot 2).

Would you mind taking a look?

Best regards

Please, contact administrator
for this information.

#32419 Copied

Eva Kemp

Participant

January 8, 2015 at 16:09

Hello,

To change projects link you need edit the theme file legenda/framework/portfolio.php (line 41)'rewrite' => array('slug' => 'portfolio') and rename portfolio to whatever you wish.

Thank you.
Regards,
Eva Kemp.

#32444 Copied

mleihs

Participant

January 9, 2015 at 11:52

Hi Eva,

thanks. I was looking for “projects” (see screenshot 2 from last post).

Best regards

#32629 Copied

Eva Kemp

Participant

January 9, 2015 at 15:31

Hello @mleihs,

Sorry for misunderstanding.
You can change “Projects” in the file legenda/framework/portfolio.php, edit the code 'name' => _x('Projects', 'post type general name'), (line 13) and write your text instead of “Projects”.

Thank you.
Regards,
Eva Kemp.

#32672 Copied

mleihs

Participant

January 9, 2015 at 18:20

Hi Eva,

thanks for the reply.

a) It tried this using the child theme but it seems like the changes to portfolio.php get ignored in this case.
b) How to deal with translations in those cases (projects, portfolio) when using WPML?

Best regards

#32700 Copied

mleihs

Participant

January 13, 2015 at 20:33

Hi Eva,

any news regarding a) or b) ?

Best regards

#33294 Copied

Eva Kemp

Participant

January 14, 2015 at 18:04

Hello,

Sorry for a delay.
a) As I see the changes you made in portfolio.php are working fine. Please clear browser cache and check again.
b) To translate those words you need edit WPML > String translation.

Thank you.
Regards,
Eva Kemp.

#33488 Copied

mleihs

Participant

February 1, 2015 at 16:05

Hi Eva,

it seems the latest update broke the code of the child theme.

Would you mind taking a look at it?

Is it possible to translate those parts using the .mo/.po files? Maintaining the php code because of translation issues seems to be quite strenuous.

Best regards

Please, contact administrator
for this information.

#38620 Copied

mleihs

Participant

February 2, 2015 at 14:33

Hi Eva,

I had to roll back the changes. I will post again once the current content tasks are finished and the latest update is installed again.

Best regards

#38813 Copied

Eva Kemp

Participant

February 2, 2015 at 14:56

Hello @mleihs,

Ok, let us know if further assistance is needed.

Thank you.
Regards,
Eva Kemp.

#38825 Copied

mleihs

Participant

February 18, 2015 at 12:20

Hi,

I updated to Legenda 2.6. #38620 is still an issue.

Would you mind taking a look at it?

How to deal with the translation issues in the future? Checking/changing the source files after each update is not very practial. Isn’t there a way to handle translations using .mo/.po files only? Why are some parts “hard wired”?

Best regards

Please, contact administrator
for this information.

#43286 Copied

mleihs

Participant

February 19, 2015 at 08:15

Hi,

sry for pushing but the site is offline and people can’t work on the content.

Please instruct how to proceed. Thank you!

Best regards

#43611 Copied

Robert Hall

Participant

February 19, 2015 at 08:24

Hello,

We’ve taken your request into our account.
At this time the translate is possible using .mo/.po files only.
What parts you mean? Please provide us with screenshot and links to them.

Regards,
Robert Hall.

#43624 Copied

mleihs

Participant

February 19, 2015 at 10:25

Hi Robert,

ok, that sounds great.

The site is currently broken because the changes I was instructed to apply to get the translation working for the portfolio section apparently aren’t compatible with the new version of the theme.

Please take a look yourself.

Best regards

Please, contact administrator
for this information.

#43659 Copied

mleihs

Participant

February 19, 2015 at 19:26

Hi,

I rolled back the changes made to the child theme. What is the best way to extend the customized .mo/.po files so that the portfolio section can be translated that way?

Thanks for fixing that issue, btw!

Best regards

#43823 Copied

mleihs

Participant

February 24, 2015 at 12:20

Hi,

I rolled back the changes made to the child theme. What is the best way to extend the customized .mo/.po files so that the portfolio section can be translated that way?

Thanks for fixing that issue, btw!

How to migrate the .mo/.po files?

Did I miss something within the upgrade notes?

Best regards

#44850 Copied

Eva Kemp

Participant

February 24, 2015 at 17:32

Hello,

Unfortunately you can’t move these files into the child theme folder.
They are active only in the parent theme.
Why do you need to move them? Your .po files won’t be overwritten after the theme update.

Regards,
Eva Kemp.

#45052 Copied

mleihs

Participant

February 26, 2015 at 12:55

Hi Eva,

Robert wrote:

At this time the translate is possible using .mo/.po files only.

So I concluded that there would be changes within the .mo/.po file structure. -> I removed most source changes done via child theme. Those are the open issues:

Please take a look at [1] (private content):
– Within the url “portfolio” instead of “autorinnen” gets listed
– Within the breadcrumbs “projects” instead of “autorinnen” gets listed

Best regards

Please, contact administrator
for this information.

#45654 Copied

Eva Kemp

Participant

February 26, 2015 at 15:47

Hello,

You can translate “Projects” in the file legenda/framework/portfolio.php, edit the code 'name' => _x('Projects', 'post type general name'), (line 13) and write your text instead of “Projects”.

To translate portfolio slug in the link you need edit the file legenda/framework/portfolio.php (line 41) 'rewrite' => array('slug' => 'portfolio') and rename “portfolio” with your translation.

Thank you.
Regards,
Eva Kemp.

#45760 Copied

mleihs

Participant

February 27, 2015 at 12:10

Hi,

Robert said it is finally possible to do this using the .mo/.po files.

Me:

How to deal with the translation issues in the future? Checking/changing the source files after each update is not very practial. Isn’t there a way to handle translations using .mo/.po files only? Why are some parts “hard wired”?

Robert:

We’ve taken your request into our account.
At this time the translate is possible using .mo/.po files only.

Now you are telling me something different. What is going on?

Changing the source for simple translation issues is really bad because you have to take care of the modification with every update.

You state that your theme is fully translatable. Changing hardwired words in the source code is not what is meant when talking about support for multible languages.

Please fix this issue asap. This thread is going on for WEEKS now and there is still no solution, or at least explain why it is a good idea to hardwire language in the source code. Maybe I don’t see the advantage of this.

Best regards

#46147 Copied

Eva Kemp

Participant

February 27, 2015 at 14:22

Hello @mleihs,

Please take our apologies for misunderstandings.
Robert meant you can actually translate theme content in .po file and not slugs.
Unfortunately to translate slugs you need edit the file I mentioned in the previous post.

We’re very sorry for the troubles you had to experience.

Thank you.
Regards,
Eva Kemp.

#46182 Copied

mleihs

Participant

February 27, 2015 at 15:00

Please fix this issue asap. This thread is going on for WEEKS now and there is still no solution, or at least explain why it is a good idea to hardwire language in the source code. Maybe I don’t see the advantage of this.

So your recommendation for updating is to reimplement that change after every update?

Does this sound sane to you?

#46197 Copied

mleihs

Participant

March 2, 2015 at 17:28

?

#46671 Copied

Eva Kemp

Participant

March 2, 2015 at 18:48

Hello,

You can use child theme and copy the files in there. Or you can always keep the file safe and update it after each theme update.
We’re sorry for such inconveniences.
We’ll try to fix it in the nearest update.

Thank you.
Regards,
Eva Kemp.

#46698 Copied

mleihs

Participant

March 3, 2015 at 14:11

Hi Eva,

thanks. That’s great news. I really appreciate it.

I applied the recommended changes to portfolio.php @ child theme but it seems the changes are ignored for now.

Please take a look yourself.

Best regards

#46947 Copied

mleihs

Participant

March 4, 2015 at 13:24

Hi Eva,

the fuzzy translations stopped working. Maybe it has to do with the latest theme update?

Do I need to retranslate all the .mo/.po files starting with the .de version of the latest download?

Please take a look at:

http://imgur.com/ExVAYgO

vs

http://imgur.com/frlicn8

Best regards,

Please, contact administrator
for this information.

#47246 Copied

Eva Kemp

Participant

March 4, 2015 at 15:22

Hello @mleihs,

We’re looking into this.
Once there is a result, we’ll let you know.

Thank you.
Regards,
Eva Kemp.

#47288 Copied

mleihs

Participant

March 4, 2015 at 15:39

Hi Eva,

thanks for the reply.

If you tell me that I need to start over using updated .mo/.po files it is fine. I just don’t wanna waste my/your time and get some clear instructions on how to deal with those translation issues. My client kinda ran out of patience during the last week; so I need to solve this during the next days.

There’s another book shop project in queue once this one is completed. Maybe others will follow. It’s not much money in terms of licensing but I guess everyone apart from the english speaking realm will be happy if the theme is translatable without getting a stomach ulcer.

Thanks again!

Best regards,

#47313 Copied
← 1 2 3 →

Viewing 60 results - 31 through 60 (of 74 total)

The issue related to '‘Several issues with the template regarding the translation/design’' has been successfully resolved, and the topic is now closed for further responses

Several issues with the template regarding the translation/design

Explore our best WordPress WooCommerce Themes collection