Hi nimrodmadar,

1) No, the switch can only be applied to the actual form content.

2) Yes but it has to be done for that specific item and will need additional css for mobile if its too big a change:

Try adding the following CSS to your Quick CSS (located under the Styling Tab in the theme options) or the custom.css file in the css folder of your theme files:

#top.page-id-708 .avia-builder-el-4 .avia-form-success {

width: 450px;

}

3) You would need to completely re-style that button with css using similar methods as in step 2.

4) No, the confirmation doesn’t have that level of customization at this point.

Regards,

Devin

Hi arrt,

If it shows 1.5 still, you need to re-download from your download on themeforest. Open that up and look at the style.css in the theme folder which should have 1.6 at the top.

Regards,

Devin

My only guess is that something was set up incorrectly. You may also need to go into your styling options and re-set one of them and re-save to get the stylesheet regenerated but that was mentioned in that topic.

Hi sobrilliant,

There was a bit of discussion on that topic in this thread that may help : https://kriesi.at/support/topic/reducing-http-requests#post-115039

Regards,

Devin

Hi imagnmedia,

It typically takes Kriesi a bit of time to respond to topics in between normal bug fixes and everything else. When is able, he’ll respond here directly.

Regards,

Devin

Hi Tsukassax.

1) Try adding the following CSS to your Quick CSS (located under the Styling Tab in the theme options) or the custom.css file in the css folder of your theme files:

#top.archive.category .title_container {

display: none;

}

then this for #2 in the same area:

.avia-menu-fx {

display: none;

}

Regards,

Devin

Hi,

You use Safari for Windows? They stopped making Safari for Windows over a year ago. This theme doesn’t support Safari for Windows as far as I know, since neither does Apple. :)

http://appleinsider.com/articles/12/07/25/apple_kills_windows_pc_support_in_safari_60

I myself am unhappy that Apple ended support, but eh, why support a browser that is not even supported by the manufacturer and that accounts for .03% of web visitors?

Thanks,

Nick

Hi,

I am not sure why. Must be a reason for it… or maybe not. In any case you can remove the code that does that and let us know if it improved mobile look of prettyphoto.

Please open up /js/prettyPhoto/css/prettyPhoto.css

and put /* on line 173 and then put */ at the very end of the file so its the last thing in the file.

Now mobile pretty photo will look the same as desktop prettyphoto. But i do vaguely remember that there is some reason for that code and without it everything looks like … not good.

Thanks,

Nick

Hi,

Your link doesn’t work. I think this one is the correct one http://www.blackjava.de/?page_id=1481

I don’t have the same mobile you use, but does it look anything like this ? http://www.clipular.com/c?7309049=9qqECREC4DTzLZ92BF6jpNV7co0&f=.png

The problem is that you specified that you want to have 10 columns, so the code is doing its best to follow your command. here is some css to change the number of columns in smaller screen sizes. You can change the percent how you want,

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

#top #wrap_all .avia-gallery-thumb a {

width:20% !important;

}

}

@media only screen and (max-width:479px) {

#top #wrap_all .avia-gallery-thumb a {

width: 33% !important;

}

}

Please add that to your /css/custom.css file

Thanks,

Nick