sw360 / sw360portal

We have moved and *archived* this repository. Pls. continue at the new place at https://github.com/eclipse/sw360 ... A software component catalogue application - designed to work with FOSSology.
Other
35 stars 20 forks source link

Broken release edit page? #526

Closed adrian-evo closed 7 years ago

adrian-evo commented 7 years ago

Deployed the latest branch master (2d10feb), and when trying to edit some of the release fields, it is not working. For example Vendor dialog is not opened and the same with moderators dialog, Programming languages and operating systems autofill also not working.

The error from the log is: 2017-08-01 12:19:12,086 ERROR FossologyAwarePortlet:178 - Could not get release from request 2017-08-01 12:19:12,088 ERROR FossologyAwarePortlet:146 - no response from backend!

maxhbr commented 7 years ago

@lepokle is this maybe related to https://github.com/sw360/sw360portal/pull/506 (together with caching, unclean deployment, ...)

lepokle commented 7 years ago

This is possible. The release edit page was changed during #506 but all tests did work. Please be sure to have a clean deployment and to throw away any browser cache. If this does not help, please provide console output of the browser (F12).

adrian-evo commented 7 years ago

Tried with clean deployment and cache. When editing a release, the following is displayed. release

lepokle commented 7 years ago

Sorry, I'm still not able to reproduce this issue. May you please tell me your browser version? Thx.

adrian-evo commented 7 years ago

This is from Firefox 52.2. ESR. The next images are from Chrome v59 and IE11. On IE11 only I also get exception when clicking on Programming Languages field. But if these are not relevant and you cannot reproduce the issue, maybe I should try with another branch to see if something was wrong during my deployment. chrome59 explorer11

ChristophNiehoff commented 7 years ago

Also the the "Linked Releases" table and the "Click to add Releases" button on the release edit page appear to be broken. (This was confirmed by @stevinus1 ).

lepokle commented 7 years ago

@adrian-evo Hi Adrian, it seems like your proxy settings are outdated causing a forbidden error: image We've updated the rules in the sw360-chores project. However I've forgot to update the rules in vagrant as well. I'll comment here as soon as this rules has been updated as well.

If you use a custom nginx proxy be sure to change the settings as followed. Old settings:

location ~* /(manager|attachments|bdpimport|components|cvesearch|fossology|layouttpl|licenseinfo|licenses|moderation|projects|schedule|search|users|vendors|vulnerabilities)/ {
        deny all;
}

New settings:

location ~* ^/(manager|attachments|bdpimport|components|cvesearch|fossology|layouttpl|licenseinfo|licenses|moderation|projects|schedule|search|users|vendors|vulnerabilities)/ {
        deny all;
}

Note the ^ to match the beginning of the URL

The old settings did not allow a path fragments like 'manager' or 'component' anywhere in the URL while the new settings only restrict these path fragments to the beginning of the URL.

lepokle commented 7 years ago

The sw360vagrant project has been updated as well. Please let me know if anything works now.

Sorry for the inconvenience!

adrian-evo commented 7 years ago

I can confirm it works now, after changing the settings directly in the file /etc/nginx/sites-available/nginx-liferay.conf.