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.

Sign up for GitHub

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

Jump to bottom

Production server: edit hardware does not work #71

Open
pbruha opened this issue Apr 24, 2014 · 4 comments
Open

Production server: edit hardware does not work #71

pbruha opened this issue Apr 24, 2014 · 4 comments

Comments

@pbruha
Copy link
Member

pbruha commented Apr 24, 2014

When I wanted to edit hardware in section Lists -> Hardware definitions, I got this warning message:

Timestamp: 2014-04-24 T 2:32 AM

Item is used and therefore cannot be deleted. You need first remove all the usage before deleting.
stebjan added a commit that referenced this issue May 14, 2014
@stebjan
#71 - editing default hardware definition allowed. Commented a block …
53f57b6 
…of code that I think it is not necessary. Need to be tested properly.
stebjan added a commit that referenced this issue May 15, 2014
@stebjan
#71 - Hardware description field - TextArea instead of TextField
b54740d
@rinkesj
Copy link

rinkesj commented May 15, 2014

This logic about editing default values is same for other lists values in list section. Maybe you will have to change others like artifact, ExperimentOptParam, FileMetadata, PersonOptParam, Weather.

@stebjan
Copy link
Member

stebjan commented May 15, 2014

I took a look at it, however, the behaviour of hardware editation needs to be tested. If everything will be OK, I will change the other lists.

@jezekp
Copy link

jezekp commented Jan 15, 2016

Is it done?

@stebjan
Copy link
Member

stebjan commented Jan 15, 2016

It is working in RDB, not tested on Elastic yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pbruha @stebjan @jezekp @rinkesj