[MGNLCDEP-27] Javascript confirmation messages do not respect other repositories than dms and website Created: 11/Dec/12  Updated: 25/Jan/13  Resolved: 23/Jan/13

Status: Closed
Project: Content Dependencies
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Type: Improvement Priority: Major
Reporter: Zdenek Skodik Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3946 Wrong confirmation message by disable... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

contentDependencies.js hardcodes the website and dms repositories for "mark as deleted" node feature.



 Comments   
Comment by Jan Haderka [ 14/Jan/13 ]

Why is doGet() now different then doPost()?

Comment by Jaroslav Simak [ 22/Jan/13 ]

By using ajax get request i ask servlet if node users wants to delete should be marked as deleted.

By using ajax post request i ask servlet to give me contents of confirmation message.

Should i handle both requests in doPost() method?

Comment by Jan Haderka [ 22/Jan/13 ]

I think you should be able to arrive at proper result irrespective to method used to issue request (you don't have control over what method caller will use to call the servlet).

Comment by Jaroslav Simak [ 22/Jan/13 ]

I see. I will use post request and move it to doPost() method.

Generated at Mon Feb 12 00:11:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.