-
Posts
-
First of all – thank you so much for an amazing theme. I’ve been a web designer for roughly 12 years now, and have been working with WordPress for about half of that. This is the best theme I’ve come across. I was very confident I wouldn’t have any issues, but of course it’s with the one thing you guys didn’t make directly!
In the help documents for the Revolution Slider it says that if it came with a theme, to contact that theme’s creator. Thus, I am here!
The problem visually (explanations below the images):
As you can see, the slider works great! Even when you resize the window’s width. However, once you maximize the window via the maximize button, the blue shape (a PNG image layer) and white text seems to stay small, and not respond accordingly. A quick resize of the window’s width fixes the issue, as does increasing / decreasing the font size (ie: via ctrl+scrollwheel). I’d imagine this is because it’s refreshing the viewport of the browser.
Also, I’m working on Windows 7, in Chrome.
I’m wondering if there is a way to trick the browser when the window is maximized or restored to refresh the viewport and redraw the page’s display. Or, any other fix to fix the rendering of this slideshow.
Even if it’s some extra code I have to add in, I’m fine with that, I just want it to work! 🙂
Thanks so much.
-SJFScott,
Thanks so much for your kind words! It’s great to hear from someone with your level of experience share that this is the best theme you’ve come across, so excited to hear that! I’ll let one of our support gurus help you with your issue, but just wanted to chime in and say thank-you!
We look forward to continuing to impress 🙂
Kyle
No problem! I really wish I could provide a URL but all of our sites are on a development server and I’m unable to push anything live. Hopefully screenshots will suffice.
To recreate this issue, simply set a background image (like the red tree) and add a few layers (I have that blue PNG and a text layer). Also, I have this placed in a row with the Visual Composer:
[vc_row no_margin="true" padding_top="0px" padding_bottom="0px" border="none" inner_container="true"][vc_column width="1/1" fade_animation="in" fade_animation_offset="45px"][rev_slider_vc alias="frontSlider"][/vc_column][/vc_row]Lastly, the page template is “Blank – No Container | Header, Footer” — hopefully that helps!
Hey Scott,
Thank you so much for writing in and for your exceptionally kind words about the theme! I have tried to recreate this particular error on our own installations on Windows 7 in Chrome and cannot seem to replicate these exact conditions. Can you confirm for me that everything is resizing on our own demos when selecting the maximize button as you state? I used Integrity 1 as our test for this.
Additionally, have you tried your slider with another theme such as Twenty Twelve? I’d be curious to know if the error persists with another theme, which would lead me to believe that it’s either a bug with Revolution Slider or a conflict with another plugin that you might be running on your site.
Let us know when you get a chance, we’ll get to the bottom of this. 🙂
I have the same issue, I use windows 7 and chrome and when I minimize then maximize the slider doesnt go back to normal.
http://www.activize.verylegendaryee.com/
Hope this helps.
At first I wasn’t able to recreate it when looking at Tiffany’s example (which by the way, thank you for sharing!) but I figured out the steps:
In Windows 7, in Chrome I did the following:
- Visit Tiffany’s Link
- Start with the window maximized, and then restore it.
- Then resize the window down until the media query changes the navigation to the 3 line menu icon
- Hit the maximize button on the window
You’ll even notice in her example (and this happens in mine too) that the slider goes on top of the row below it. I’ve tried adding a clearfix below but that doesn’t work. It seems like maybe there’s a media query that gets stuck or isn’t reset back to its original values or something? Just speculating.
Also this topic is marked as “Resolved” but it isn’t. I hope I didn’t do anything to mark it as such! 🙂 I believe the issue is still pending.
Thanks for your input guys! Regarding the issue being marked as “Resolved,” we mark all tickets that we have answered at lest once this way. We will of course continue to assist you until an answer is found. We simply ask that our members wait patiently while we work through issues and responses as it can take up to 24 hours to provide a reply to certain threads depending on how busy things are and how complicated the issue is. Thank you for your understanding.
As stated above, I’d be curious to know if this is happening if you switch to another theme such as Twenty Twelve and go through these exact same steps. This will help us to confirm whether or not this is a theme or plugin issue. We do not make any updates to how the JavaScript for Revolution Slider works, so I cannot imagine anything we are doing in the theme would interfere with this (same goes for our CSS). I’ll be looking forward to hear what you all have to say after trying this out and following the exact steps above with another theme.
Thanks!
I have set this up for you.
http://www.sourcec.de/x_demo_test/
I put X on there temporarily to try it outside of my current internal project. It seems to still happen on this install. So I went ahead and turned on the twenty twelve theme to show you it does the same thing.
Same steps. Resize down until responsive mobile menu icon/button shows up – then hit your maximize button on your window, and it happens just as the screenshot shows 🙁
Hey Scott,
Thanks for setting that test up! This does indeed confirm that the issue is with the plugin and not the theme as it is still occurring with Twenty Twelve active. This is seemingly a very unique bug to this OS/browser combination. Regarding this particular situation, you are at least fortunate in that to reproduce this error users must reproduce a very specific set of steps. As I’m sure you know, most users tend to not spend their time resizing browser windows the way we developers and designers do, so they’re not likely to see this particular error. 🙂 It’s definitely something that you can take to the Revolution Slider team and comment about on their ThemeForest comment section. I would link out to your test install and describe to them the exact steps that you’re using to get this bug, and then explain that this is happening in multiple themes. Additionally, you should mention that one of the themes is a core developed WordPress theme.
Hopefully that helps for this particular situation. Unfortunately there is nothing we can do regarding this as it has to do with plugin functionality.
Thanks!
This is seemingly a very unique bug to this OS/browser combination. Regarding this particular situation, you are at least fortunate in that to reproduce this error users must reproduce a very specific set of steps.
Thanks but the only reason why I had mentioned the OS/browser originally was due to the fact that that’s what I had tried initially. It is not specific to that browser and OS. I was giving you information to recreate the issue. Also I was giving specific steps because that’s ALSO how to recreate the issue, but not the ONLY way to recreate the issue.
As I’m sure you know, most users tend to not spend their time resizing browser windows the way we developers and designers do, so they’re not likely to see this particular error.
You’re right. Most people won’t be resizing their window. Unfortunately, this happens even if you start the browser and it’s a smaller window size, and you simply hit maximize on the browser window. This is a very common occurrence that I don’t feel we can ignore.
Also, their support section says to go to their support site, which due to the fact that the slider came with your theme, the text on that site says the following:
In case you purchased the Plugin bundled in a Theme,
Please contact the Theme Author via his profile page, or his support forum, as it is there responsibility to provide you support for the complete package ie Theme+Plugins. Due to the high number of tickets from users who have not purchased from us directly via codecanyon, we can not responding if the plugin was included/bundled/bought with a theme purchase.
So while I understand that this may be the plugin issue, according to this – I must go through you guys to get support, and cannot even access their forums otherwise.
With that said…
I’ve narrowed down the possibilities of the issue down to the file jquery.themepunch.revolution.js and begins at line 407 where it says “// IF RESIZED, NEED TO STOP ACTUAL TRANSITION AND RESIZE ACTUAL IMAGES”
It’s the only section in the code that does something when the window is resized, and therefore is a high suspect for the issue. Perhaps someone at Themeco has to contact ThemePunch regarding this issue.
Hey Scott,
We will investigate this issue and we’ll get back to you when resolved.
Thank you.
Just a heads up, I checked out their site:
http://themes.themepunch.com/?theme=revolution_wpAnd theirs does not do it, and it is inside of a responsive framework. So their updated plugin seems to work fine. Any way I can get the updated plugin from you guys?
Hey Scott,
We have submitted this inquiry to their support team in order for them to investigate this further. Regarding the plugin version, X currently includes the most recent update of Slider Revolution (v4.1.4) with the theme, so if you’re using that you’re all up to date. Regarding our request to have you contact the author, we fully understand that due to the fact that Revolution Slider has come included with the theme that you cannot receive support from the author. However, that doesn’t mean that users still cannot contact them to report a potential bug. Most authors will appreciate this as it enables them to better their product by informing them of a possible error. We are sorry if it seemed as though we were trying to have you go receive support somewhere else as that was not our intention. Sometimes these things can simply be addressed quicker in the manner prescribed, but either way we have submitted a ticket ourselves and are awaiting a response back from their team.
Thanks!
