Hi all!, I am working on making the

solidus_reviews

gem compatible with Solidus 4.4. While the gem integrates smoothly with the older

solidus_frontend

, I am encountering issues with routing and view compatibility when using it with the

solidus_starter_frontend

. Version Details • Rails: 7.2.2 • Ruby: 3.1.2 • Solidus Core: 4.4.1 • Solidus Reviews: 1.7.0 When attempting to access the new review form, the layout fails to render, and the gem is unable to recognize the routes defined in the

solidus_starter_frontend

storefront.rb

. This results in an error like

undefined method or variable root_path

. Additionally, when trying to create a new review, it does not redirect to the expected

product_path

because the gem doesn’t recognize this route either. These issues suggest that the gem’s route handling and view rendering are not fully compatible with the conventions or structure of

solidus_starter_frontend

. I have reviewed the

solidus_reviews

gem’s repository and explored other Solidus extensions built on top of

solidus_starter_frontend

. However, I was unable to find any solutions or patterns that effectively address these compatibility issues. Given the challenges I've encountered, I wanted to ask for your opinion. How does the Solidus team handle this kind of compatibility between gems and

solidus_starter_frontend

? What best practices or steps would you recommend for aligning the functionality of the

solidus_reviews

gem with the starter frontend? Any guidance you can provide on how to resolve these integration issues would be greatly appreciated. Thanks in advance!

The started frontend is a template. All the views and controllers are copied over the host application. For extensions to support this template, they need to do the same. The installer should copy the new compatible views and controllers over the host application. The legacy frontend code should be disabled if

solidus_frontend

is not installed.

Got it, Thank you!