[satori]

Hey Chris,

the “gallery”-type tiles were not given overlays for a specific reason in Ikebana: otherwise the overlays would obstruct the navigation buttons, which would make it impossible to manually go through the slides. If you want to enable overlays for “gallery” tiles, you’ll need to add a specific call to the javascript that shows/hides the overlays on mouse hover. I’ve prepared a custom solution for this: please download this archive, unzip it, and upload the contained files into the theme folder (/wp-content/themes/Ikebana/) on your server, overwriting the existing files when prompted.

Sincerely,
Andrii / Satori Studio

[satori]

Hey Jonathan,

at the moment you can use different static image backgrounds on different pages, yet one instance of a background slider. Same goes for the header slider – if you create one in the Theme Options panel, it will be displayed on every page you feature it on. If you need more variety in sliders, you can try installing any of the free or premium slider plugins and using their slider as an additional one.

Sincerely,
Andrii / Satori Studio

[satori]

Hey Trish,

thank you for the suggestion! I am not sure though that selectively hiding part of the website’s content is a solution that would fit most projects, since mobile users would then experience a significantly different website than desktop users. There was an idea to shrink all tiles proportionally on smaller screens so that the layout of the original grid is preserved, but after extensive testing we’ve decided to go with fitting all tiles to screen width and making them uniform because when screen sizes shrink past a certain point (typically below tablet screens) the tiles in a grid become so small that their content becomes illegible or incomprehensible.

In case you do need to hide certain tiles on mobile screens, you can achieve this using some custom code (you can insert it into the “Style: Add Custom CSS” tab of the Theme Options panel:

@media only screen and (max-width: 728px) {
.iso-masonry #post-XX,
.iso-masonry #post-YY,
.iso-masonry #post-ZZ { 
display: none; } 
}

where “XX” and “YY” are the IDs of the posts to hide. You can get the ID for a post or a project by entering the editor mode for that item and looking at the URL in the browser’s address bar: the number after the “post=” bit is the ID.

Sincerely,
Andrii / Satori Studio

[satori]

Hey Jonas,

I’ll cover the issues below, in the same order:

1). This is indeed a bug, stemming from the absence of one declaration in JS that governs tile sizes on smaller screens. I’ve updated your website and the theme, will include this into the next version update, thank you very much for the heads-up.

2). Frankly speaking, so far I haven’t had such plans for the immediate future, but I will investigate the scale and the time needed to make a decision. As far as the particular case is concerned, I am not sure if it will be solved in the new version directly, but what you can do for now is e.g. force the images to scale proportionally on tablets, i.e. adding a

.wpb_single_image { height: 100%; }

declaration for medium-sized screens. This will tell the images to stay square, but might make the page longer vertically.

3). I’ve just updated WooCommerce to 2.3.11 on the demo website, so far haven’t identified any bugs – in case you encounter any, though, please let me know, and they will be solved ;)

Best,
Andrii / Satori Studio

[satori]

Dear Sascha,

first of all, thank you for the purchase!

I’ve produced a fix to make the theme fully compatible with the latest version of WP Customizer – please download this archive, unzip it, and upload the resulting file into the theme directory (/wp-content/themes/Kabuki/) via FTP or your hosting provider’s file manager, replacing the existing file. Alternatively, you can provide the admin access to your WordPress installation, and I will add the necessary code fixes by myself; you can email me at support@satoristudio.net.

Regarding the logo – in Kabuki it is fixed at 116×120 pixels, in order to ensure proper scaling of the website on various screen sizes (foremost mobile); in case you need the logo to be wider or taller, please let me know, and we will come up with a solution that fits your requirements.

The theme manual (page 2) lists all the Theme Options tabs that are available in Kabuki – could you please clarify where the “Header, Header Slider and Style: Header” are mentioned?

Sincerely,
Andrii / Satori Studio

[satori]

Hey Caroline,

I’ve investigated the issue, it was caused by an is_product() function in the theme’s “functions.php” file – in one place the function was being used without checking whether the WooCommerce plugin, which supports it, is indeed installed on the particular WordPress instance – which messed up the posts created automatically by the FeedWordPress plugin. I’ve corrected the file, and will also include this fix into the next update of the Shogun theme. My apologies for the inconvenience, and thank you for reporting this!

Sincerely,
Andrii / Satori Studio

[satori]

Hey Caroline,

I’ve tested the FeedWordPress plugin with a fresh install of the Shogun theme, using a feed from the same website (recruiter.co.uk), and it seems to be working fine. To further investigate your case, I will need access to the admin area of your WordPress instance – please send me the login and password in response to the email I’ve sent you. Thanks!

Sincerely,
Andrii / Satori Studio

[satori]

Hey Olollo,

the native theme’s submenu in Ikebana is vertically aligned (i.e. one submenu item under another), and the theme does not envisage as ready horizontal submenu. Certain customization work, which is not covered by the ThemeForest support offer, will thus need to be carried out in order to implement this; I can recommend Envato Market as a source of knowledgeable WordPress developers who can take on ad-hoc customization tasks.

Sincerely,
Andrii / Satori Studio

[satori]

Hey Olollo,

the 500 error might be caused by numerous reasons, and is in general due to the workings of the server (as the error message suggests). One thing to try before you contact your hosting provider though is that the file you’re uploading as the demo content has the .xml extension and not any other. Another possible culprit, on the server side already, is the maximum upload size limitation set by your hosting provider, but normally they shouldn’t get in the way since the demo content file is quite small by any standard (less than half a megabyte).

Sincerely,
Andrii / Satori Studio

[satori]

Hey Christoph,

since the URL you’ve linked to is not a “project” post-type nor a custom post type in general, but a new page template, you should add a corresponding declaration for the #content element to stretch to 100% of width – to do this, you can add the new page layout to the declaration on line 537 of the theme’s “style.css” file, so it looks like this in total:

.page-template-page_full-width-php #content, 
.page-template-page_full-width-no-header-php #content, 
.page-template-page_portfolio-four-column-php #content, 
.page-template-page_portfolio-three-column-php #content, 
.page-template-page_portfolio-two-column-php #content, 
.page-template-page_portfolio-one-column-php #content,
.page-template-single-workshops-php #content  {
  width: 100%;
  padding: 0;
}

Sincerely,
Andrii / Satori Studio

[Author]

Posts