Open blset opened 8 years ago
@blset Thanks for your quick reply. So first I should remove the existing original
(As I am modifying an existing deface in a gem), and then run the server again to see the new sha1 it suggest in the log, and then put that new value in the original
attribute. Correct?
Thanks
yes exactly
Le 10 févr. 2017 à 10:38, Paarth notifications@github.com a écrit :
@blset https://github.com/blset Thanks for your quick reply. So first I should remove the existing original (As I am modifying an existing deface in a gem), and then run the server again to see the new sha1 it suggest in the log, and then put that new value in the original attribute. Correct?
Thanks
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spree-contrib/spree-multi-domain/pull/150#issuecomment-278899250, or mute the thread https://github.com/notifications/unsubscribe-auth/AAio_sCs-Y5w0EZzqKYQxN1SV_MCN9gkks5rbDAvgaJpZM4Iv8Ek.
The sha1 is given by deface itself in the log in development mode
the message is something like :
this override has no original consider adding orignal => « the sha1 »