Skip to content
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

Migration to mobility gem - spree_mobility #100

Open
mrbrdo opened this issue Apr 13, 2022 · 3 comments
Open

Migration to mobility gem - spree_mobility #100

mrbrdo opened this issue Apr 13, 2022 · 3 comments

Comments

@mrbrdo
Copy link

mrbrdo commented Apr 13, 2022

Hey, this is not really an "issue" but I wanted to let you know that I forked this project and switched to the mobility gem, which is recommended by globalize authors as the successor to globalize (not actively developed anymore).

Mobility works very, very similarly to globalize, but there are a few subtleties that had to be updated. All the database stuff remains the same so it's a drop-in replacement.
I also fixed some bugs and I plan to update the admin views a bit because it bothers me that product description has no WYSIWYG editor, for example.
I will switch to it in production next week.

If you want you could add a note about this gem in the readme, spree guides or elsewhere, as an alternative to spree_globalize.

https://github.com/mrbrdo/spree_mobility

Also just want to point out that spree itself still includes a few lines of code pertaining to SpreeGlobalize, which should really be extracted into spree_globalize, for example like I've done for SpreeMobility: mrbrdo/spree_mobility@7d81cb2

Regards, Jan

@Kulgar
Copy link

Kulgar commented May 11, 2022

Wow, thank you so much for this gem and all the work! <3
I'll switch to your gem right away :-)

@mrbrdo
Copy link
Author

mrbrdo commented May 12, 2022

Thanks! I think I did some updates in master, so I also pushed a v1.1 of the gem now. I am using it in production, so far without problems (as in Readme, I added fallback locales especially for admin to not have issues with empty translations on secondary locales). Also as noted, need to use my version of friendly_id-mobility, until the maintainer merges those bugfixes. I also am using some fixes for mobility (https://github.com/mrbrdo/mobility/tree/mrbrdo) but I think they may not be needed for everyone, it has to do mostly with subclasses and fallbacks (although it shouldn't hurt to have these).

Please let me know if you have any issues, since I only tested it with my app. Will be glad to have any feedback.

@Kulgar
Copy link

Kulgar commented May 12, 2022

@mrbrdo : so far, so good, it works like a charm (except for the issue I posted on your project)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants