Closed (fixed)
Project:
Profile 2
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Jun 2011 at 21:14 UTC
Updated:
1 Sep 2011 at 08:31 UTC
Jump to comment: Most recent file
Comments
Comment #1
roam2345 commentedAs a side note some of the fields were still there, but others had been removed... (as I added a new profile with the same machine name as the old one)
Comment #2
fagoI cannot reproduce this, e.g. by cloning the "main" profile and putting in the machine-name "main" in the clone, I get a validation error. Can you reproduce it? If yes, what are the exact steps?
Comment #3
roam2345 commentedHere are the steps.
1. select clone on a profile. (screen shot 1)
2. select delete profile type (screen shot 2)
3. select confirm (screen shot 3 error in that shot off another module ignore that)
4. I then get the error (screen shot 4) with the error below.
remember what has happened here is I have chosen to clone the form presented is full of the clone information and I have then chosen to delete that (maybe that should be cancel not delete). After getting the error I return to the profile list screen and the profile I have cloned from originally is now removed (this is bug).
also to note is that I am on Drupal 7.2 and dev version of profile.
Comment #4
ericbroder commentedHi jucallme, it looks like there are two separate issues you're dealing with here.
First, when you go to clone a profile type, there are two buttons marked "Save profile type" and "Delete profile type". This is confusing because the first button means you will save the new clone-copy profile type, but the second button means you will delete the original cloned-from profile type. Adding to the confusion is that there is no "Cancel" or "Go back" button, which is actually the option you were looking for.
So we may want to consider this issue as a UI bug, and maybe a patch that just clarifies the two buttons better is sufficient. Another option is to add a Cancel button, and/or remove the Delete button.
The second issue you're dealing with is an error message that I can't replicate. I did a quick search though and you may want to look at some related discussions:
- Creating field instance during hook_insert() causes PDOException: http://drupal.org/node/1182010
- #687180: Deleting a taxonomy vocabulary leaves term reference fields still pointing to it, and a PDO Exception when creating content
- #1007830: Nested transactions throw exceptions when they got out of scope
Thanks,
Eric
Comment #5
ericbroder commentedGiven the extra confirmation page that clearly tells you which profile type is going to be deleted, this doesn't seem like a major issue.
Comment #6
ericbroder commentedAnother option is to just remove the delete button from the clone page, so it's more like the add page:
Comment #7
ericbroder commentedHere's a patch to remove the delete button from the clone page, so it's more like the add page.
Comment #8
roam2345 commentedWhat about a button to cancel the current clone?
Comment #9
ericbroder commentedA cancel button would probably be nice too, but it's not necessary. When you add a new profile type, there is no cancel button, you either save the new profile type or you don't. The clone process could be the same way. I think the more important problem is that the delete button is confusing.
Comment #10
fagothanks, committed.