Forum Replies Created
-
Posts
-
Hey!
We will update the theme with a minor bugfix immediately for those of you who would rather wait a few hours instead of messing with the files ;D
Regards,
KriesiHi!
we have added A fix to the upcoming release that should solve it for everyone. if you still experience problems once version 3.4 is released in a few days please let us know in a new thread :)Cheers!
KriesiHi guys!
We are still investigating and did not forget this thread but I am afraid we require more information from other encountering the error, since we can’t reproduce it.We will let you know if we can find whats causing the issue and why it only happens for some of our users…
Regards,
KriesiHey!
this seems to be a bigger problem that I expected. I will not add the fix for this with the next update since it would require to change and test multiple core functions of the builder but will see if I can fix it with one of the next updates when I got more time for testing…
Best regards,
KriesiHi!
I am not aware of any limitations but of course I am no lawyer an dnot sure how google germany operates. I am afraid this question is probably more suited for a google maps related forum :)Best regards,
KriesiHey!
I have replied here: https://kriesi.at/support/topic/windows-phone-support/#post-530175
Regards,
KriesiHey!
I am afraid I can’t make any promises that we will be able to fix it. What I can promise right now: I am in the process of getting my hands on a windows phone for a few days and will check if I can a) reproduce the issue and b) fix it.
Especially the fixing part might be tricky since fixed elements like parallax and fixed BGs are bugging us on iOS and android as well and every few OS updates we need to tweak them slightly again. Mobile devices dont play well with fixed and I am afraid windows phones in particular are currently the “ie6” of mobile development.
So even with a phone I might not be able to find an easy solution that I can apply. We have not mentioned support for windows phones, firefox mobile and opera mobile for several reasons. They got low market shares and in certain areas they are really so far behind that its often not economic to try and fix their bugs.
But as I said, lets see what I can accomplish with a windows phone…
Cheers!
KriesiHi!
Did take a little but I was able to fix the issue. Wil be available with the next update ;(
Cheers!
KriesiHi!
Thats actually not a bug. The markup should be used for SEO purposes, according to the rest of the content on that page but I can see how its confusing since its located under the styling tag. I will see if I can make this somehow more clear and if I will change the styling to reflect the selection of the tag
Cheers!
KriesiHey!
thanks for the notice. did a little longer to resolve but we will add the bugfix to the next update
Cheers!
KriesiHi!
this is intended behavior, not a bug.
Usability test have shown that users hate it if they try to scroll to a certain position to read/see something and the slider keeps scrolling. So interacting with any of our slideshows will always disable the autoscroll featureRegards,
KriesiHi!
Took a little while but we were able to fix the issue and will update the theme during the next days ;)
Cheers!
KriesiHey! Since php7 is currently only in beta we are still waiting for a MAMP php package that allows us to test it locally. Once I can get my hands on a package I will update the theme accordingly
Regards,
KriesiHi!
Sorry for the late reply, this one took a little longer. I think I found a viable solution and will add it to the next theme update ;)
Cheers!
KriesiHi!
thanks for the notice, I was able to find and solve the issue. the fix will be included in the next update
Best regards,
KriesiHi!
I will have to check with them again I guess :P
In one sentence he says its up to me and the immediate sentence right after says “to continue support you would need to purchase another extension”Does not make sense to me -_-
Hi!
sorry for the late reply, seems I missed the thread. Your username is now changed :)
Cheers!
Kriesigreat, let me know what they tell you, maybe they have already changed their mind and I wasn’t aware of it :)
Hey!
The link you posted has no answer from anyone who works at envato. If someone from envato says that we dont have to limit support to the support period we wont do it :)
But until now I haven’t read anything that indicates that this is true. Every official answer from envato until now, was that we have to play by their new rules, and that everyone who does not is jeopardizing their relationship with envato.
So truth to be told, I can’t imagine that the x-theme guys will ignore the envato ruling and simply offer support after that 6 month period, since envato could (and probably would) force them to comply.
As was said in the marketplace forum thread: right now I wouldn’t worry to much about it. There is still a long time until this affects any customers and everything might change until then. You will also always be able to read the forum and get access to updates, so more often than not I think you wont need any support after 6 months…
Cheers!
KriesiHi!
Sorry for the late reply. The mailchimp integration will be available with the next update, I am currently finishing the work on our own API connection class and everything seems to work fine.Once I have finished the remaining two demos we will release the update ;)
Best regards,
KriesiPS: I did take a look at your installation and am not quite sure why the “shop” url does not work but changing the url of the default shop to: http://highlandbespokefurniture.co.uk/online-shop/ works.
My best guess would be to check if you got a real folder on your FTP server that has the name “shop” since it might be causing the problem. Or you can simply go with a different url. That would certainly be easier than using a second installation :)
Cheers!
Hey!
Using two installations with enfold in this case would not be a problem at all so although I am curious why this error is occurring and I hope we can fix it, you can of course create a “shop” installation of enfold since its the same domain and same project :)
Cheers!
KriesiHey!
Very glad for the detailed description on how to reproduce the issue. I was able to do so now as well (timing was indeed the thing we all missed) and also found a way to fix it. Did take me a while to figure why this is happening but the good news is that there is a very easy fix that will be available with the next update.
If you want to apply it yourself you can do so by openeing the /js/shortcodes.js file and search for this line:
if( this.isAnimating || this.itemsCount < 2 )
change it to
if( this.isAnimating || this.itemsCount < 2 || !this.$slider.is(":visible"))Thanks for reporting the issue and the detailed explanation on how to reproduce it ;)
Best regards,
KriesiPS: the workarounds posted by the team are not necessary for this to work and should be removed since those are only partial fixes ;)
Hi zerodi!
I am not sure how it is possible that you have 20 people who can easily reproduce the issue and no one in our whole team can’t. I am afraid we also have no reports whatsoever about this issue from any other of our customers. As you have probably read my response to websitegurus as well you know that we keep track of these issues. If other users come along and report the issue and give us more hints on how to reproduce the problem we will fix it if we can.
Until then I don’t see a way for us to help you. It would probably help if you tell us the exact version of the browsers you are using and the exact OS numbers as well. Browser plugins might help as well. Since other people you know can reproduce this as well the chance is low that this is the root of the problem (since I don’t think you are all using the same settings/browser/os versions) but it might help us to try and replicate the problem if we try on a setup as close as possible to yours.
Sorry for the bad news here :/
Cheers!
Kriesips: was just thinking: you could also run the portfolio website and open the chrome browser console ( https://developers.google.com/web/tools/javascript/console/console-ui) and check if a javascript error is thrown on your browser.
