Beta 4: Component bugs

Beta
#1

Hi, It’s Almost there!

Hopefully the team can put their feet up for a bit soon :slight_smile:

Just some very minor ones.

Field won’t give a value when phone is selected but works for the link and mail.
image

Attribute value will be empty
image

Might be worth checking any other ACF areas. I checked conditions and that was working just fine.

Component bug - upon editing a component’s -> Element CSS and double checking it was saved (as I hear this is an issue) The corresponding page using that component didn’t manage to apply the custom CSS until I re-saved the page using the component. its a small bug but could have a few people scratching their heads.

Thanks

#2

Thanks, @samc! We’re getting there. :slight_smile:

I have noted these issues down and they will be looked into!

#3

@samc, thanks for writing in here…I have tested this personally as well as another developer on the team and neither of us could replicate this issue following your instructions mentioned above. This could potentially have been a side-effect of some other issues that we are working to resolve on this cycle, so keep an eye out on this one after the release to see if it’s still happening for you. As of right now I’m going to mark it as resolved as many things have been updated and we cannot achieve the same end-result at this time.

#4

@samc To clarify we can’t reproduce the component css issue. The ACF issues will be fixed in the next release.

#5

Thanks for fixing the ACF bits.
Beta 4:
@charlie I have checked again and still have the component issues.

Component edits - Small style alterations don’t appear for me (e.g. set text colour) unless I resave the page hosting the component. If I edit the physical text on the element. then save the component that seems to update straight away.

New issue found in components: opacity from the pallet on an element doesn’t carry over to when its used on the actual page. you get the full colour. tested an rgba value just to be sure and that worked.

#6

@samc, thanks for writing in. I have tested the Component CSS issue you mentioned above and cannot replicate it, this is working as expected for me. I did the following:

  • Created a “Button” Component Set and exported it as “Primary Button.”
  • I opened my “Home” page and added the Component to this page.
  • I went back to the Component Set and added custom Element CSS to the Component, confirmed it applied in the Component Set, and saved it.
  • I navigated back to the “Home” page and the Component was reflecting the CSS changes as expected.

If you could provide more details on what CSS you’re trying to apply and how it’s working, that might help us narrow down what is happening, as this appears to be working for me. Alternately, if you can provide login details to your site with explicit details on which Components you’re having this issue with and where they’re used on your pages, we could take a look into that.

As for the global colors, I have mentioned this elsewhere but there is a nuance with adding global colors in your palette if you plan to use the alpha slider technique. Basically, you always need to ensure your color is an rgba() value for this to work, hex values will not get parsed properly at this time. If you are only using solid colors, any value will work, but if you plan to use the alpha slider to get a variation of your global color, it needs to be rgba(), and this will work on both the frontend and the backend.

Thanks!

#7

Hi @kory, I have attached a note above.

Hopefully you can figure it out. Also feel like I have to refresh the editor after switching tabs otherwise I lose changes. I’m using Chrome and this install was from beta 2 or 3 to begin with.

Thanks

#8

@samc, thanks for that…I think I finally see what’s going on for you after playing around with things. I thought you were talking about changes not being reflected in the builder, but it seems you meant on the frontend. Any change I made to the Locations Component (either with custom Element CSS or a change on a nested Element) always reflected after saving and switching to the Home page in the builder to see the changes, but when I went to the frontend, I can see that it is not showing up there. This is likely a caching issue on our end and I will notate it and make sure it’s taken care of.

Thanks!

#9

Thanks @kory I assume you are done with the dev site. so I’ll take that down. if you need again just let me know.

Thanks

#10

We should b good for now, thank you!