-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual glitch when adding new sets #2
Comments
I checked this and actually my field labels / handles are:
|
So that code is Bard related. Where do you have that Bard field? |
I think it might be the replicator, this blueprint has no Bard fields. Here's a basic blueprint - deleted. |
I had to make some minor changes to get that blueprint to work on my Statamic installation.
With those changes the blueprint works, but I still couldn't replicate the issue. @stuartcusackie If you want to chat about the issue, you can find me in the Statamic discord. |
Sorry, now I cannot produce the errror from the blueprint I shared earlier. Can you try this one please? Sorry for the length! DELETED
|
this should fix Visual glitch when adding new sets #2
See if v1.0.3 solves the issue. |
It's partially fixed! There is also a delay / lag of between 3 - 10 seconds before the button on my replicator is clickable (see my first screenshot where the icon is missing). I haven't seen this problem before so I think the tabs are causing a delay somehow. Also, the sets from my replicator don't appear until I switch tabs. See my gif video below. |
I see. I could see that issue as well, but it was fixed for me in the last update. |
Yes I tried it in a newly created entry and the same problem occurred. If I have less fields in my blueprint then it doesn't occur but I can't quite narrow down to any specific field that is conflicting. |
I have narrowed this down to an asset field conflicting. Simply having a single asset field within my replicator sets tabs introduces a lag and breaks the tabs. The blueprint below should recreate the problem. If I just remove the bg_image asset field then everything is fine, no matter how many sets I add. Maybe it's something to do with the Droppable area of the asset field...? That's the only thing I can think of that makes an asset field special.
|
Awesome. I'll investigate further based on that input. Thank you. |
Any joy here? I've got a couple of projects that could really use your tabs. My fields are a mess! Happy to make a donation once I've got everything working. |
Hey @stuartcusackie. I've been really busy lately and I forgot about this! Sorry! 😳 |
Thanks man! Sorry for the trouble! Statamic really needs this tabs package. |
I remember experiencing this bug my self a few times on some test sites I'm working on. |
I was fairly certain last time I tested it was a simple asset field causing the problem. The field was hidden behind a tab. I'll fire up my codebase now and see if I can reproduce it.... |
I cannot reproduce it now either! I even downgraded as far as Statamic 4.9.1. I have a feeling it will reappear when I go to develop my tab-based page builder. I'll come back when I go ahead with that. Thanks for looking!! Sorry if it's something weird I'm doing! |
I have experienced the bug as well on multiple occasions, so it's definitely not just you doing something weird. |
I'll keep thinking on it it anyway, and I'll try to put together my full page builder over the coming weeks. There's so many moving parts in Statamic - it could be anything I guess. Thanks again! |
I'm closing this issue for now, but please reopen if you experience this again. |
Each time I add a new set containing tabs I get this glitch:
Note that:
Thanks!
The text was updated successfully, but these errors were encountered: