# Breaking changes on clickability and date-times retrieved from page URL

**URL:** <https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075>\
**Category:** Announcements\
**Created:** [February 10, 2022, 8:24pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075 "2022-02-10T20:24:47Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![cm1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/cm1/32/3947_2.png) [@cm1](https://forum.bubble.io/u/cm1)\
**Post date:** [February 11, 2022, 11:07am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/21 "2022-02-11T11:07:58Z")

</div>

my app is blown up, people calling like crazy. How can we revert this???

---

<div class="post-metadata">

**Author:** ![buero](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/buero/32/31435_2.png) [@buero](https://forum.bubble.io/u/buero)\
**Post date:** [February 11, 2022, 11:08am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/22 "2022-02-11T11:08:32Z")

</div>

We created our Buttons out of Groups, cause Buttons can’t have icons in it - so we made the text in the group to non clickable so use do not copy the text by accident. Now this way of buttons with icon usage is not possible anymore cause when they click on the text - nothing happens, just if they click outside of the text element…

Pls undo this

---

<div class="post-metadata">

**Author:** ![cm1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/cm1/32/3947_2.png) [@cm1](https://forum.bubble.io/u/cm1)\
**Post date:** [February 11, 2022, 11:11am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/23 "2022-02-11T11:11:52Z")

</div>

@emmanuel @josh can you please clarify? What should we do? things are very messy

---

<div class="post-metadata">

**Author:** ![ed727](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ed727/32/71942_2.png) [@ed727](https://forum.bubble.io/u/ed727)\
**Post date:** [February 11, 2022, 11:21am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/24 "2022-02-11T11:21:04Z")

</div>

I thought Bubble had a hard rule that breaking changes were rolled out as versions? Not sure why this didn’t follow that established process.

---

<div class="post-metadata">

**Author:** ![lakeman](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/lakeman/32/14489_2.png) [@lakeman](https://forum.bubble.io/u/lakeman)\
**Post date:** [February 11, 2022, 11:21am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/25 "2022-02-11T11:21:26Z")

</div>

Had to check and change my solid app.  
A lot of things became ‘unclickable’.  
It’s oke guys to create new features but please keep your hands of existing running apps!! Really pissed with this. sorry…  
Worried about my other apps now…

---

<div class="post-metadata">

**Author:** ![cm1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/cm1/32/3947_2.png) [@cm1](https://forum.bubble.io/u/cm1)\
**Post date:** [February 11, 2022, 11:50am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/26 "2022-02-11T11:50:28Z")

</div>

hello Grace. Can you please tell us how to revert this? My app is destroyed and people won’t stop calling us. Its really a mess

---

<div class="post-metadata">

**Author:** ![lottemint.md](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/lottemint.md/32/26549_2.png) [@lottemint.md](https://forum.bubble.io/u/lottemint.md)\
**Post date:** [February 11, 2022, 11:57am UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/27 "2022-02-11T11:57:35Z")

</div>

Breaking changes =\> Wrecking changes  
☹

---

<div class="post-metadata">

**Author:** ![cm1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/cm1/32/3947_2.png) [@cm1](https://forum.bubble.io/u/cm1)\
**Post date:** [February 11, 2022, 12:03pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/29 "2022-02-11T12:03:11Z")

</div>

what did you do? have you been able to talk to them?

---

<div class="post-metadata">

**Author:** ![mikeloc](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/mikeloc/32/93001_2.png) [@mikeloc](https://forum.bubble.io/u/mikeloc)\
**Post date:** [February 11, 2022, 12:15pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/30 "2022-02-11T12:15:58Z")

</div>

Sadly, @cm1, I think the only answer is to wait. I think most of these folks work in New York, so I’m guessing as soon as their day gets rolling, this matter will be addressed in some way, shape, or form.

---

<div class="post-metadata">

**Author:** ![cm1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/cm1/32/3947_2.png) [@cm1](https://forum.bubble.io/u/cm1)\
**Post date:** [February 11, 2022, 12:16pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/31 "2022-02-11T12:16:27Z")

</div>

It seems that it works now. Can you check your app?

---

<div class="post-metadata">

**Author:** ![ehabelbadrawy](https://avatars.discourse-cdn.com/v4/letter/e/96bed5/32.png) [@ehabelbadrawy](https://forum.bubble.io/u/ehabelbadrawy)\
**Post date:** [February 11, 2022, 1:09pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/32 "2022-02-11T13:09:54Z")

</div>

My whole app has stopped working! Nothing is clickable anymore! We need a way to revert this!

---

<div class="post-metadata">

**Author:** ![gerbertdelangen](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/gerbertdelangen/32/144602_2.png) [@gerbertdelangen](https://forum.bubble.io/u/gerbertdelangen)\
**Post date:** [February 11, 2022, 1:17pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/33 "2022-02-11T13:17:44Z")

</div>

@ehabelbadrawy, see wether there are parent groups (of the element which is not clickable ) with the option “this element isnt clickable” activated, and if so, deactivate/unmark the option, that will probably solve the problem.

---

<div class="post-metadata">

**Author:** ![yorgio1024](https://avatars.discourse-cdn.com/v4/letter/y/f17d59/32.png) [@yorgio1024](https://forum.bubble.io/u/yorgio1024)\
**Post date:** [February 11, 2022, 1:24pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/34 "2022-02-11T13:24:46Z")

</div>

My app is not working yet and maybe the team are asleep but the live apps were destroyed with this

---

<div class="post-metadata">

**Author:** ![ehabelbadrawy](https://avatars.discourse-cdn.com/v4/letter/e/96bed5/32.png) [@ehabelbadrawy](https://forum.bubble.io/u/ehabelbadrawy)\
**Post date:** [February 11, 2022, 2:06pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/35 "2022-02-11T14:06:01Z")

</div>

Thanks Gerbet!

I can see it’s fixable but this is a massive amount of work for my app and I would’ve liked not to be forced to halt all development to correct this. That fact is made even worse by knowing the Bubble team was well aware this is a breaking change, yet decided to go ahead with it anyway without any warnings.

I’m lucky the app isn’t live yet. I can only imagine what others are going through right now.

---

<div class="post-metadata">

**Author:** ![philippe1](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/philippe1/32/38163_2.png) [@philippe1](https://forum.bubble.io/u/philippe1)\
**Post date:** [February 11, 2022, 2:17pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/37 "2022-02-11T14:17:56Z")

</div>

> [@yorgio1024](#):
>
> This update broke my live app, how revert this update?, bubble it should implement this changes to update manually.

same here

---

<div class="post-metadata">

**Author:** ![sudsy](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/sudsy/32/114637_2.png) [@sudsy](https://forum.bubble.io/u/sudsy)\
**Post date:** [February 11, 2022, 2:27pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/38 "2022-02-11T14:27:25Z")

</div>

> [@ehabelbadrawy](#):
>
> the Bubble team was well aware this is a breaking change, yet decided to go ahead with it anyway without any warnings.

Clearly, this should have been a versioned update, and the negative reactions are justified IMO. The fact it wasn’t versioned just points to a flaw/oversight in the deployment procedure, which will no doubt be addressed.

---

<div class="post-metadata">

**Author:** ![ed727](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ed727/32/71942_2.png) [@ed727](https://forum.bubble.io/u/ed727)\
**Post date:** [February 11, 2022, 2:31pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/39 "2022-02-11T14:31:59Z")

</div>

> [@mikeloc](#):
>
> definitely seems like they should have been opt-in

Yup, I’m sure that Bubble will figure this out, though if they unwind the change, does it then “break” apps that people have already “fixed” from this “breaking” change? 🤔 So I suppose the ideal fix is unwinding it and immediately making available a new version, so people can decide whether to accept the changes or not.

I’m huge Bubble fan and I don’t think this has impacted my app… but the process breakdown here is what concerns me. I hope Bubble addresses it to ensure that a breaking change is never done without opt-in via a version update; otherwise it erodes trust in the platform for large-scale use.

---

<div class="post-metadata">

**Author:** ![grace.hong](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/grace.hong/32/109318_2.png) [@grace.hong](https://forum.bubble.io/u/grace.hong)\
**Post date:** [February 11, 2022, 2:56pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/40 "2022-02-11T14:56:43Z")

</div>

Hey all,

Just wanted to respond that we are in the process of reverting these changes and rolling them into a new Bubble version. I want to deeply apologize for the issues that were caused by the release of these breaking changes. Generally we do release significant breaking changes in a new Bubble version, but for smaller changes that we estimate may impact a smaller user base, may do more good in resolving previously incorrect behavior, and may closely match the user’s intended behavior, we make the decision to push the changes out.

In this situation, we misestimated how these changes would impact our users. For the future, we will aim to proactively reach out in advance of breaking changes to better understand how users might be impacted and better assess our development lifecycle to best support our users’ apps.

We are still running through some tests to ensure the revert does not break things, but I’ll update you all when it has happened.

For those who would like to use the new behavior, I’ll update this thread when we re-release these changes in a new Bubble version.

---

<div class="post-metadata">

**Author:** ![Jici](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/jici/32/30722_2.png) [@Jici](https://forum.bubble.io/u/Jici)\
**Post date:** [February 11, 2022, 3:03pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/41 "2022-02-11T15:03:01Z")

</div>

@grace.hong @josh @emmanuel  
When I saw the topic title to “Breaking changes” I was sure it was in version setting. I think it’s a real mistake here to not have push that in version that all users can control and I really hope this mistake will not happen again. If you consider a change to be a breaking change, it should always be in version settings.

---

<div class="post-metadata">

**Author:** ![ed727](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ed727/32/71942_2.png) [@ed727](https://forum.bubble.io/u/ed727)\
**Post date:** [February 11, 2022, 3:11pm UTC](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075/42 "2022-02-11T15:11:52Z")

</div>

> [@Jici](#):
>
> If you consider a change to be a breaking change, it should always be in version settings.

Agree. What’s still concerning is that Bubble is saying they are making a judgement call on how many users a breaking change will “break”, and that determines whether or not it is rolled out as a new version.

I believe the approach should be very simple – if it’s a breaking change, then it is incorporated into a version update. Otherwise that removes our ability to implement and test changes in the test environment prior to deploying to live.

[Previous page](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075.md?page=1)

[Next page](https://forum.bubble.io/t/breaking-changes-on-clickability-and-date-times-retrieved-from-page-url/191075.md?page=3)
