Hey!

Thanks for pointing that out. we will fix this with the next update ;)

Cheers!
Kriesi

Hey!

Das problem mit dem update kann auch mit einer server Einstellung zusammenhängen. leider bin ich da auch nicht bewandert genug um zu wissen an welchen server settings man schrauben muss um das hinzubiegen. wir nutzen das envato toolkit für die backend updates, ist also auch nicht wirklich etwas das von uns geschrieben wurde.

Was die Icons angeht: ich erhalte folgende meldung von der google developer konsole:

Font from origin ‘http://www.diefleischerei.at’ has been blocked from loading by Cross-Origin Resource Sharing policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘http://business.diefleischerei.at’ is therefore not allowed access.

Ebenfalls entweder ein server setting das es zu ändern gilt oder du gleichst im backend die wordpress domain ab. Wenn du die seite über business.diefleischerei.at aufrufen willst muss auch im wordpress backend diese adresse eingetragen sein. (außer du änderst die cross origin sharing settings deines servers )

lg,
Kriesi

PS: bei weiterer Überlegung: vielleicht hat letzteres mitschuld an den update Problemen.

Hey!

Not sure what is causing this and I got troubles reproducing it. While I am investigating the issue you might want to try to open your functions.php file and remove the line

wp_enqueue_style( 'avia-print' ,  $template_url."/css/print.css", array(), '1', 'print' );

which includes the print.css file and is probably causing the issue in one way or another

Hi Guys!

We have already uploaded version 3.08 which should finally fix the translation issues. if you still got problems please open a new thread and dont use this one, we would like to keep this one reserved for new translation files ;)

Best regards,
Kriesi

Hey Guys!

I am having trouble reproducing and understanding the issue, so in order to make it as easy as possible for us to get the problem:
Please post a link to your installation and also the browser you are using. If you want feel free to add login credentials.

Also please describe the area which is now transparent and previously was not, since a few of the examples links you posted obviously are modified and enforce transparency, so I am not sure what is desired and what is not…

Best case scenario would be screenshots from previous versions as well but I guess in most cases thats not an option.

Diese CSS snippet sollte helfem:

.avia-slider-testimonials .avia-testimonial-meta .avia-testimonial-image {
margin: 0 10px 0 0;
width: 80px;
height: 80px;
}

#top .avia-slider-testimonials .avia-testimonial-content, #top .avia-slider-testimonials .avia-testimonial-arrow-wrap .avia-arrow {
border: none;
background: #ddd;
}

Hi!

Mind updating the theme to version 3.05. I have improved a few automated layout settings that might help on this particular case :)

Best regards,
Kriesi

Yes I noticed that too. At this point I am afraid we will need to wait for others with a similar issue to gather more information. If I happen to find out whats causing the issue I will post here…

Mind posting your login credentials as a private reply so we can take a look? Please also post a link to the draft in question…

Using a private window doesn’t really help I am afraid. Caching is still a pain ;D
Nevertheless I think I found a solution and it should work once the edited avia.js file is loaded instead of the old one

In that case would you also add a wordpress login for me so I can regenerate the cache once I have applied some changes?

Hey!

Elliott is correct. If you want to use a theme form themeforest for that purpose you would need to get a multisite license. It might be a lot cheaper to purchase one license for each person using the theme.

If you want more information on licensing or maybe discuss a price reduction I would recommend to get in touch with envato support: https://help.market.envato.com/hc/en-us/requests/new?ticket_form_id=37840

Hope this helps. Best regards,
Kriesi

Hey!

I actually don’t think thats a css issue at all. As far as I can tell the javascript sometimes does not calculate the height of the underlying element correctly which causes the problem. Thats why when the browser is resized and the javascript is fired again everything is aligned properly. So basically a problem with the first javascript calculation.

Whats also weird is that this does not happen to the majority of our users. But as I said, I will keep investigating the issue until its fixed :)

Cheers!
Kriesi

Hey Guys!

I have added a small fix to the parallax script that I think might solve the issue with the next update. Since I cannot be sure please let me know if the error persists after updating to 3.05

Also in that case it would be great if you can post me your ftp credentials so I can do some trial/error testing with the javascript files.
Although this does not really seem to happen to a lot of people I really would like to get this solved for the two of you. Lets hope the bugfix does it ;D

Best regards,
Kriesi

Hey!

From what i can tell #1 and #4 have been used to register the accounts:

#1: rosiefuture
#4: pelvic

The other 2 have not been used. Should it be any different?

Cheers!
Kriesi