Quickform Error Element Already Exists
Contents |
already exists'Agile Board ExportXMLWordPrintable Details Type: Bug Status: Closed Priority: Minor Resolution: Won't Fix Affects Version/s: 4.4.6 Fix Version/s: 4.7 Component/s: Core CiviCRM Labels: None Documentation Required?: None Funding Source: Needs Funding Description Steps to reproduce:
Http Status Code Resource Already Exists
1. Create a custom data group (CDG) with any label (our example: "Language http status code duplicate resource options") with display style "Inline". 2. To this CDG, add a custom data field (CDF) with any label (or example: "Preferred
Http Status Code 409
Language"), data type 'Alphanumeric', field type 'CheckBox'. 3. To this CDF, add any number of option values, including one option value with any label (our example: "Tagalog") and the value "tag" (OR the 422 - entity already exists value "group"). 4. Edit or create a contact for which this CDG is applied. 5. Observe fatal error: QuickForm Error: element already exists Possible other ways to reproduce: I'm guessing that any other existing field name used as a checkbox value will have the same problem; for example, I tried 'first_name' and found that it does yield the same error. Workaround: Don't use 'tag', 'group', 'first_name', or 409 conflict rest any other existing field name as a checkbox value for a CDF appearing in an "inline" CDG (assuming that you know what all those field names are, that future versions don't add a core contact field with a name that collides with one of your custom checkbox values, etc.). Activity Ascending order - Click to sort in descending order All Comments Work Log History Activity Hide Permalink David Greenberg added a comment - 27/Aug/14 10:17 PM Allen - a PR against master would be much appreciated. Show David Greenberg added a comment - 27/Aug/14 10:17 PM Allen - a PR against master would be much appreciated. Hide Permalink Coleman Watts added a comment - 02/Aug/15 8:38 PM Closing due to lack of activity. Incidentally, I think this problem is much less likely to manifest now that we automatically set option values to a numeric sequence. Show Coleman Watts added a comment - 02/Aug/15 8:38 PM Closing due to lack of activity. Incidentally, I think this problem is much less likely to manifest now that we automatically set option values to a numeric sequence. People Assignee: Unassigned Reporter: Allen Shaw Votes: 0 Vote for this issue Watchers: 2 Start watching th
a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings
Http 208
and policies of this site About Us Learn more about Stack Overflow http status code 422 the company Business Learn more about hiring developers or posting ads with us Magento Questions Tags Users
Http Status 422
Badges Unanswered Ask Question _ Magento Stack Exchange is a question and answer site for users of the Magento e-Commerce platform. Join them; it only takes a minute: Sign https://issues.civicrm.org/jira/browse/CRM-15194 up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Element with id “path” already exists error up vote 0 down vote favorite After upgrading magento to 1.9.2.2, I get this error when clicking on the category management page in admin. I was able http://magento.stackexchange.com/questions/96376/element-with-id-path-already-exists-error to find this thread "Element with id "path" already exists" and followed the advice on the answer listed, and searched for all instances of "addField('path" and found the same 6 that the person who answered the question on that thread did. The code is the same for mine. It's all updated and current. I can't find the source of this error and I am at a loss as to where to start looking for it. I understand I should be looking at extensions to find the answer. But I only had a few installed, and they didn't have anything to do with category management. I deleted them anyways and flushed the cache and updated indexes and everything, same error. Does anybody know where I should be looking to solve this error? The trace log that is spit out when I generate the error is as follows: #0 /home2/mysite/public_html/lib/Varien/Data/Form/Element/Abstract.php(58): Varien_Data_Form->checkElementId('path') #1 /home2/mysite/public_html/lib/Varien/Data/Form/Abstract.php(148): Varien_Data_Form_Element_Abstract->addElement(Object(Varien_Data_Form_Element_Text), false) #2 /home2/mysite/public_html/lib/Varien/Data/Form/Element/Fieldset.php(135): Varien_Data_Form_Abstract->addField('path', 'text', Array, false) #3 /home2/mysite/public_html/app/code/core/Mage/Adminhtml/Block/Widget/Form.php(195): Varien_Data_Form_Element_Fieldset->addField('path', 'text', Array) #4 /home2/mysite/public_html/app/code/core/Mage/Adminhtml/Block/Catalog/Category/Tab/Attributes.php(113): Mage_Adminhtml_Block_Widget_Form->_setFieldset(Array, Object(Varien_Data_Form_Element_Fieldset)) #5 /home2/mysite/public_html/app/code/core/Mage/Adminhtml/Block/Widget/Form.php(144): Mage_Adminhtml_Block_Catalog_Category_Tab_Attributes->_prepareForm() #6 /home2/mysite/public_h
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads http://stackoverflow.com/questions/3825990/http-response-code-for-post-when-resource-already-exists with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign https://github.com/moodle/moodle/blob/master/lib/pear/HTML/QuickForm.php up HTTP response code for POST when resource already exists up vote 308 down vote favorite 51 I'm building a server that allows clients to store objects. Those objects are fully constructed at client side, complete with object IDs that are http status permanent for the whole lifetime of the object. I have defined the API so that clients can create or modify objects using PUT: PUT /objects/{id} HTTP/1.1 ... {json representation of the object} The {id} is the object ID, so it is part of the Request-URI. Now, I'm also considering allowing clients to create the object using POST: POST /objects/ HTTP/1.1 ... {json representation of the object, including ID} Since POST is meant as "append" operation, I'm not sure what to do in case http status code the object is already there. Should I treat the request as modification request or should I return some error code (which)? http rest share|improve this question asked Sep 29 '10 at 21:26 vmj 1,63921012 4 As of June 2016 FB blatantly sets 200 on registration when email exists –Green Jun 21 at 11:50 add a comment| 8 Answers 8 active oldest votes up vote 375 down vote accepted My feeling is 409 Conflict is the most appropriate, however, seldom seen in the wild of course: The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the entity being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might use the 409 response to indicate that it can't complete the request. In this case, the response entity would likely contain a list of the differences between the two versions in a for