Itās very specific, overflow updates will also not work. I think it has to do with how Bubble applies inline styles during render. Classify updates probably get overidden.
I think I see why
This is what I have
buttonsGroup {style: "position: sticky; bottom: 0px;"}
@julienallard1 if you republish the plugin without obsfucating it, I would take a look at the code and try to help.
Hey guys, I just pushed a new update that should fix these issues. In some cases, the algorithm that parses the content of the ID field into classify commands would mess up.
From the little testing I did, it all seems to work fine. Please let me know how it goes for you ![]()
Thanks to Arron from Levupp, a little bug introduced in previous update was fixed:
The algorithm that parsed raw commands would throw an error when a command (addClass, style, attribute, etcā¦) and the colon that follow would be separated by a space.
Now both of these examples are valid:
{addClass: "myClass"}{addClass : "myClass"}
You are invited to update to version 4.0.8
Classify just saved my butt with per-question radio button spacing on a form. Thanks for developing this plugin and offering it for free!
hey, thanks for taking the time to mention on the forum, I appreciate it!
Classify has now been around for over 6 years and currently installed on 90K+ apps. I wouldāve really liked the Bubble Team to acknowledge the need for easier CSS controls and implement a native solutionā¦
hey all! I just released an update that fixed a bug where, in some cases, some Classify commands could throw an exception when content was still loading on page. Thanks to Akihito Ktakatsu for reporting the issue
.
While at it, I added a new little function that allows Classify to log informations (errors, warnings and standard messages) into an object you can access in the browserās console by typing classifyLogs. This logging feature is enabled only when running your bubble app in preview mode.
Happy new year everyone!
Hey @julienallard1 I just discovered a bug with tempclass. If the main ID Attribute does not call any Classify method but then calls tempclass in the condition, the tempclass will not get removed from the element.
| Main ID Attribute | Condition ID Attribute | Works as intended? | Issue |
|---|---|---|---|
| someElementID | someElementID{tempClass: āpopFrontā} | Temp class sticks | |
| someElementID{} | someElementID{tempClass: āpopFrontā} | ||
| someElementID{tempClass: āpopFrontā} | Temp class sticks | ||
| {} | someElementID{tempClass: āpopFrontā} |
As a test I assumed Classify will trigger a checking function if I added the encapsulation and it worked. So as long as Classify is called in the main ID Attribute, the TempClass will remove correctly.
I assume that this issue is persistent for other Classify methods that only get called in a condition cause I do remember Classify script methods failing many moons ago, when I was testing if I can trigger some scripts in conditions.
Hope a fix is not too much trouble!
Thanks for pointing that out. Iāll try to spare some time in the near future to have a look at it.
@ihsanzainal84 I just publish an update that addresses the issue. Thanks for reporting it ![]()
Hey all, version 4.1.1 is out. This update only contains a bug fix
Because of my very limited time and because I donāt use Bubble anymore, only minimal testing were made, prior releasing this update.
So if version 4.1.0 didnāt cause you any issue, consider not updatingā¦