Fix emoji response for Bootstrap 4

[digitaldina]

Fixes #5647

• PR is descriptively titled 📑 and links the original issue above 🔗
• tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with rake test
• code is in uniquely-named feature branch and has no merge conflicts 📁
• ask @publiclab/reviewers for help, in a comment below

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software

Thanks!

[digitaldina]

@publiclab/reviewers

[plotsbot]

	2 Messages
📖	@dinaelhanan Thank you for your pull request! I’m here to help with some tips and recommendations. Please take a look at the list provided and help us review and accept your contribution! And don’t be discouraged if you see errors – we’re here to help.
📖	It looks like you haven’t marked all the checkboxes. Help us review and accept your suggested changes by going through the steps one by one. If it is still a ‘Work in progress’, please include ‘[WIP]’ in the title.

Generated by 🚫 Danger

[jywarren]

Awesome! Can you share a screenshot of your fixes? Thank you!!!

[digitaldina]

@jywarren I'm having issues on c9. When I click a note, this comes up:

any ideas?

[jywarren]

ah! I think you may have to run `rake db:migrate` there, since we've modified the database!

…

On Tue, May 14, 2019 at 4:27 AM d1g1t4ld1n4 ***@***.***> wrote: @jywarren <https://github.com/jywarren> I'm having issues on c9. When I click a note, this comes up: [image: image] <https://user-images.githubusercontent.com/19677511/57682709-69494d80-7600-11e9-8d15-a78465047b1d.png> any ideas? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5711?email_source=notifications&email_token=AAAF6J3MU25K5VE2ISKYM6DPVJZS3A5CNFSM4HMLGJN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVKVH3I#issuecomment-492131309>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAF6J3CA66EVZFKRLLFGETPVJZS3ANCNFSM4HMLGJNQ> .

[digitaldina]

@jywarren When I run rake db:migrate I get I, [2019-05-14T23:05:45.669200 #5034] INFO -- sentry: ** [Raven] Raven 2.9.0 configured not to capture errors: Not configured to send/capture in environment 'default' W, [2019-05-14T23:05:46.353605 #5034] WARN -- Skylight: [SKYLIGHT] [3.1.5] Running Skylight in development mode. No data will be reported until you deploy your app. (To disable this message for all local apps, run skylight disable_dev_warning.)

[jywarren]

I think that's all right! Are you on the latest master branch code?

…

On Tue, May 14, 2019, 7:06 PM d1g1t4ld1n4 ***@***.***> wrote: @jywarren <https://github.com/jywarren> When I run rake db:migrate I get I, [2019-05-14T23:05:45.669200 #5034] INFO -- sentry: ** [Raven] Raven 2.9.0 configured not to capture errors: Not configured to send/capture in environment 'default' W, [2019-05-14T23:05:46.353605 #5034] WARN -- Skylight: [SKYLIGHT] [3.1.5] Running Skylight in development mode. No data will be reported until you deploy your app. (To disable this message for all local apps, run skylight disable_dev_warning.) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5711?email_source=notifications&email_token=AAAF6J2YOX7UJNINM6S25BTPVNAWTA5CNFSM4HMLGJN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVNBK3I#issuecomment-492442989>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAF6J7B34WM2L33BTZBUO3PVNAWTANCNFSM4HMLGJNQ> .

[digitaldina]

@jywarren yes, I think so:
master...dinaelhanan:emojiFix

[sashadev-sky]

@dinaelhanan @jywarren I get the sentry / skylight notice too that isn't a problem. I was actually failing the same test that you're failing recently and I did a rebase (#5659) and it fixed it. Perhaps this may fix it for you? (for travis)

[sashadev-sky]

@dinaelhanan for the other issue I don't know about using c9 but when I get this type of error because of database updates i fix it by clearing my cache: bundle exec rake tmp:cache:clear

[ViditChitkara]

Hi @dinaelhanan , would you mind trying Comment.last.reply_to in 'rails console' in your terminal. There might be a case that the migration where the 'reply_to' column is added to comments may not have run.
Thanks

[digitaldina]

@ViditChitkara I tried this but it didn't work :(

[digitaldina]

@sashadev-sky I tried your suggestion but when I force pushed, it closed the PR, it also says that it got merged??? I'd appreciate some help :/

[sashadev-sky]

Hmm thats really weird!! Sorry about that!! If you make any commit to the branch, I think it will reopen it. As for the lost work I think we can recover it ny doing a $ git reflog then $ git reset --hard HEAD@{# of ref you want to go back to before this happened} and force push that.