[Yves]

Contacting SKT gave me even more confidence that I made the right choice in choosing them for all my themes. I have now been with SKT for over two years and and they are still coming up with awesome new themes and providing excellent support. As somebody who has provided support for many years I can only salute them for their professionalism when customers are often rude and not easy to work with. When you contact them for support do not assume the theme is at fault and be humble enough to admit you may not understand what is happening or that you may be lacking some knowledge on how to further customize it yourself. They do a super job at helping you move forward with whatever may be the issue. Just be polite and kindly ask. I will be staying with SKT for a long time for sure.

[Yves]

Oh boy, this is so simple it’s almost embarrassing! Thank you, it worked perfectly. I didn’t put it in the Custom CSS portion of the Customizer but in the styling sheet of a child theme I linked to the parent farming theme. Your answer was perfect considering my absolutely novice question, but the child theme will work better in the long term. Now I have to spend much needed time on improving my knowledge of css, php and wordpress so I don’t ask such questions again.

On an unrelated subject you might be interested to know that your themes work beautifully with WPML users. The easiest (and quickest way) for novice users like me to translate fields in the Appearance Customizer is to use the WMPL shortcodes and the WMPL string translation. I just register new strings as I go in each field (example below) and then translate them in WPML string translation.

Reference: https://wpml.org/documentation/support/wpml-coding-api/shortcodes/

Anyways, many thanks, love your themes and will continue to refer people to your site!

Regards,
Yves

[Yves]

Of course, my apologies, it should have been essential information to submit. I did not think it was relevant as this can be reproduced in any WP installation in less than a minute (sorry again).

URL1 – http://dev.auvieuxmagasin.ca – This is a temporary WP 4.9.9 install with the SKT Farming theme that I purchased. You can see the problem with the site title on the home page. Two words of the title are in bold/strong, the last word in regular text, and it cannot be changed with functionalities in the Customizer (only colors for separate parts of the title).

URL2 – https://auvieuxmagasin.ca – this one is in heavy maintenance and cannot be accessed (plus many store orders and financial users in it). URL1 shows the problem.

My request for assistance is:
I purchased the Farming theme based on was was presented in the demo: A Site Title with a single typography (ex: bold across all words), and the functionalities presented in the documentation. It did not say anywhere the site title would be presented in a different fashion -if- it contained more than one word. Two separate colors can be applied to the Site title with the Customizer but the typography is enforced (no functionality to correct that).

My question is: Can I prevent this in any way and keep the site title with only one font having the same typography across the title? I tried inserting html space characters between “Au” and “Vieux” and “Magasin and that seemed to work because the theme would no longer put Magasin aside in it’s own span element but that really messed up WPML – it could no longer translate the site title from french to english.

The reason this is causing a problem is because the Site Titles are often used as:
– a business name
– a sentence of importance with meaning.

It remains after all the subject or title of the whole site. If the theme forces emphasis on the first portion of the title (strong/bold) and removes it for the end it can, and does, interfere with meaning as much in the name of the business or a sentence with meaning. How can I keep the site title the same across all of it’s words?

Thank you much for take the time to assist me. I try to keep my support requests to a minimum. Actually this is the first in two years 🙂

Yves

[Author]

Posts