Hello! I have found a glitch with the new “Text + Icon” buttons. Basically, the “disabled” design elements are not working when you connect it to a dynamic page and set to “next” or “previous dynamic page”. Eg. I have the disabled background, text & icon design all set to white. The idea being when they are “disabled” they will blend into my site page’s white background.
Button background is set to all white:
Text is set to all white:
Icon is set to all white:
I discovered this glitch specifically on a dynamic page. The button is connected to data and set to go to the “next dynamic page”:
So, when you arrive at the last dynamic page available in this dataset, the button becomes “disabled”. However, instead of turning all white as I set it in the design settings, it creates this weird grey shadow.
So you’ll see the button on the left set to “Previous dynamic page” is still in regular mode, but the two buttons on the right which are set to “Next dynamic page” instead of turning all white go grey. It looks highly unprofessional to me.
It seems to me like the Corvid coding is overriding the regular Wix Editor Design formatting that I manually set?
Would love to some feedback from Wix support!Or if any other users have noticed this glitch and/or found a solution please let me know!
#featurerequest #glitch #wixbuttons #dynamicpages
Interesting issue which I ran into myself about a week ago. I was going nuts, but in the end I discovered that the background setting that I had for disabled in fact was set to grey. So, maybe this is not a coincidence - maybe there’s a bug here?
Please post the URL of your site and page so that we can look at it.
Hi Yisreal! Yes, I think I actually discovered this a few weeks ago on another site, but in that case, it didn’t throw off my design, so I didn’t think much on it and moved on.
Here is the link to the site’s editor: https://editor.wix.com/html/editor/web/renderer/edit/e0715608-0aac-4a8b-bb24-0c5c57f84457?metaSiteId=399eeec0-e3ea-46a4-b484-6223746c80d8&editorSessionId=bfe30007-3e85-4163-bea2-38dcc4557e42
It’s under the Dynamic “Properties Pages” under “Projects (Property Name)” or "www…/properties/{Title} "
To see the disabled state go to /properties/vanderbilt-brooklyn-artist-loft"
(Let me know if that suffices for links)
I played around a bit more. I was able to get the Disabled Text & Icon to disappear by setting the disabled state’s color to 0%. However, whether I set the Disabled Button Background to 0% or 100% white it still shows up as a grey shadow:
Background 0% #ffffff:
Text 0% #ffffff:
Icon 0%
#ffffff & size 0px
On preview, left side is a “regular” button and vector art. Right side is the “Text + Icon” button we are discussing. As you see, the box casts a grey shadow.
Just for kicks, I duplicated the button and set the disabled state to a red background with white text & icon at 100%. Text and Icon on disabled showed up as “greys” and the red button background defaulted to the grey shadow again:
Disabled Background 100% red:
Disabled Text 100% #ffffff
Disabled Icon 100%
#ffffff, size 40px
Preview, on the right, showing both buttons disabled. The bottom button is set to red with white text + icon. On disabled the white text appears. But the icon turns grey and the background is definitely not red:
- Here is the link to another site I mentioned I discovered the same override issue with: https://editor.wix.com/html/editor/web/renderer/edit/5f07a4b2-5d83-4a0f-8a05-e2688f644fa2?metaSiteId=93487870-1ddc-400a-a6c2-ed9c63df4f4d&editorSessionId=e6aba0b0-e6d3-408c-bee5-53d8dddfc072
You can find this on the Dynamic “All Music pages” on both the “Browse Covers (All)” or “Browse Originals (All)” - The Genre, Mood and Vocals buttons’ disabled states are set to a light blue, but when disabled they default to a grey colored palette:
Disabled Design Settings:
Disabled Preview Glitch, defaults to a grey color scheme (All three buttons are set to .disable onClick eg. $w( ‘#dropdownGenre’ ).disable(); )
I am having the same issue right now. Was this ever solved?
I’m also still having the same issue - was there ever a solution or workaround?
So we can see what you’re doing, please show screen shots and share your code in a code block.
