I am using AWS EC2 and facing issue
When I try to update the Basic details of the admin panel, I am getting the error “Detail update failed”
Same error is defined in following link by some user. And it was accepted as error. However no solution was given.
https://github.com/sharetribe/sharetribe/issues/3132
Can anyone please help in this?
After much debugging I could see that the error is in getting default / selected locale. The basic details page does not show the option to select the locales on AWS EC2. In local pc this works fine.
Because of this there is no locale and so the save button code shows the error.
Now tried to find out why adding extra locale feature is not shown here.
The view
app/views/admin/community_customizations/_locale_selection.haml
has some javascript and it calls the method
ST.updateLocales(#{enabled_locale_keys.to_json.html_safe});
This method is in file
app/assets/javascripts/admin/community_customizations.js
But that ST is not available during the call. The console gives error as ST not available.
And I am not understanding what is ST and why it is not available on EC2?
Any help on this is much appreciated.
Facing the same error here with Sharetribe on AWS EC2, although on local PC it is working just fine.
The issue seems even broader than mere detail update failed. In my case, all drop-down menus are absent (not displaying), such as the user menu (e.g. clicking the small black triangle doesn’t open the menu).
I had to try it on local PC to first see what those menus include because I could never manage it on AWS!
I have tried deleting marketplace and recreating it from scratch, reinstalling node, etc. but nothing will do.
My guess is that javascript itself is non-functional as per the standard Sharetribe install on AWS EC2.
Any hint or help to resolve this is welcome, as this is a real showstopper…
I managed to correct this issue.
It was due to a wrong Node.js version being used, most likely because of a broken installation.
Reinstalling Node.js version 7.8.0 and using it with the below commands solved my problem.
nvm ls-remote
nvm install 7.8.0
nvm use 7.8.0
Hope this helps!
Yes. I think It was Node version issue.
Now the issue is resolved. But don’t know what exactly resolved it. I did the Complete new installation