[satori]

Hey Massaki,

The background images in Kanso have an automatic “background-size: cover” CSS rule, which forces the images to always occupy the available space fully, thus inevitable cropping them in most cases; however, it ensures that there are no blank spaces and strange background behaviour on various screen sizes. If you need your images to display full width on any screen size (although I would not recommend having important information in the form of backgrounds), you can add a “background-size: contain” CSS rules for the particular backgrounds for smaller screens, e.g.:

@media only screen and (max-width: 767px) {
#page-holder-12 {
background-size: contain !important;
}
}

the Google map on the front page seems to have been added via a third-party plugin, thus this part of the issue should be solved through the plugin itself.

Sincerely,
Andrii / Satori Studio

[satori]

Hey Chris,

glad you’ve found the cause of the problem!
Should you have questions about the theme, do not hesitate to contact me.

Sincerely,
Andrii / Satori Studio

[satori]

Hey JP,

the “sticky” feature in Ikebana works like the same feature classic blog layouts – the “sticky” projects are displayed in front of others; it is not possible to “stick” boxes at random places within the masonry grid, because the grid changes with the screen width of the viewing device (the Isotope plugin, which is the basis of the grid, does not support this feature as well). Please let me know if I misunderstood the question!

Sincerely,
Andrii / Satori Studio

[satori]

Hey Balazs,

I cannot seem to be able to replicate the issue – could you please send a screenshot? Thanks!

Sincerely,
Andrii / Satori Studio

[satori]

Hey Massaki,

you can try removing everything below line 253 in the “responsive.css” file, starting with the one that says:

@media only screen and (max-width: 1030px) and (min-width: 767px) {

apart from that, there are no small-screen specific CSS rules in the theme, so the elements will behave according to their floats and positions – note that on smaller screen sizes this might not be what is expected (which is exactly why the theme has specific small-screen CSS rules).

Sincerely,
Andrii / Satori Studio

[satori]

Hey Stevo,

I am not sure I understood the situation – could you please clarify what you mean by “setup a widget on that page” – is it the custom sidebar drop-down in the page editor mode, or are you talking about the “Appearance -> Widgets” admin section? Also, please clarify where exactly do you choose “show” or “hide” with respect to the widget. Thanks!

Sincerely,
Andrii / Satori Studio

[satori]

Hey Neonbrand,

I can’t see an icon menu on the page you’ve linked to – could you please clarify which filter you have in mind?

If you wish to emulate the square icons on the left as in the theme demo, please create one or more icon menu items in the “Icon Menu” tab of the Theme Options panel; more information on the icon menu and its filtering option is available in the “Menus” section of the theme manual.

Sincerely,
Andrii / Satori Studio

[satori]

Hey Timsofa,

first of all, thank you for the purchase!

I will go over your questions in the same order:

1). This hasn’t been envisaged in the theme’s back-end, yet it can be done using some additional custom CSS:

@media only screen and (max-width: 767px) {
.page-holder h2 { display: none; }
}

You can insert custom CSS into the child theme’s style.css file (if you are using one), or into the “Style: Add Custom CSS” tab of the Theme Options panel.

2). Again, this hasn’t been envisaged as a back-end option because a blog typically does contain information on when and by whom an article has been posted. However, you can hide it by using some more custom CSS:

.home #post-list-wrapper .post-meta { display: none; }

3). The mobile menu will take on all styles set for the main menu in the “Style: Header” tab of the Theme Options panel. If you wish to specifically change the color/background of any the mobile version, you can do it with some additional CSS:

@media only screen and (max-width: 767px) {
#nav-wrap { background-color: #ffffff; } #nav-wrap li a { color: #333333 !important; }
}

replacing the “#ffffff” and “#333333” with the hex codes of colours which match your preferences.

4). You’re right, there might be a need to make them always full-width on smaller screens, thank you for pointing this out! I’ve prepared a fix – please download this archive, unzip it, and upload the resulting files into the theme folder (/wp-content/themes/Kanso/) via ftp, replacing the existing files when prompted.

Let me know if any of the above does not achieve its goal!

Sincerely,
Andrii / Satori Studio

[satori]

Hey Chris,

I suspect that this error message might be caused by the same bug that causes the one you’ve mentioned in your other thread. Could you please try taking the steps I’ve described there, and let me know what happens. Thanks!

Sincerely,
Andrii / Satori Studio

[satori]

Hey Chris,

first of all, thank you for the purchase!

I’ve double-checked the theme on a new WP instance, and could not replicate the “header already sent” error. From the message you’ve posted though, I can see that the WP Cache plugin might be the culprit. Could you please try disabling it and clearing the browser’s cache? If this does not remove the error, please try activating any other theme (e.g. the default Twenty Fourteen) and checking if the error persists. Please let me know of the results!

Sincerely,
Andrii / Satori Studio

[Author]

Posts