dotnetic Posted April 10, 2014 Share Posted April 10, 2014 Install Process Why not try to create a database automatically if it does not exist? When I entered HTTP Host Names and the DB Auth failed, I had to enter this information again. Please do not delete data in input fields if something was entered incorrectly. Adding fields When I add a field, I want to add it directly to one or more templates. This is solved very cumbersome. It would be better if I get a list of all templates and select in which templates the field should be added. Deleting fields "This field can not be deleted because it is used by one or more template ( s ) ." It should be displayed, in which templates the field is used. New Option: Force delete field There should be an option to force delete a field. "The field $fieldname is going to be removed from the following templates a b c Are you sure to delete it? (yes)(no)" New Option: Force delete template This Template is used by 3 pages: Page 1 Page 2 Page 3 Are you sure to delete it? (yes)(no)" What should happen with pages that have this template currently assigned after removal? ( ) Delete them too (X) Assign a new template Creating new templates When i created a new template with template->new from the dropdown-menu i don´t want to get back to the overview page for templates. I want to edit my newly created template directly. So please redirect to the edit page instead. This is a different behavior to adding fields, which works as intended. What was that fieldname again? Please show the name of the field after the label if debug mode is on (or always?) Easier select field The option/label should be only divided by = If no label is assigned, display the option as label What do you think of these improvements? 5 Link to comment Share on other sites More sharing options...
kongondo Posted April 10, 2014 Share Posted April 10, 2014 What was that fieldname again? Please show the name of the field after the label if debug mode is on (or always?) Uh, this is already available when debug=true ...though a bit wonky in a few use cases...You need to hover on the arrow on the right of the field when editing a page. Otherwise, some of your suggestions are neat Link to comment Share on other sites More sharing options...
pwired Posted April 11, 2014 Share Posted April 11, 2014 PW is as good, fast and easy as you are. Link to comment Share on other sites More sharing options...
teppo Posted April 11, 2014 Share Posted April 11, 2014 +1 for some of these, especially the force delete field/template ones. It's apparently a safety feature to make it harder to lose important data, but also very, very annoying at times. IMHO a proper warning would be quite enough: "this will remove [the field from following templates / following pages using this template], are you sure you want to continue?" Link to comment Share on other sites More sharing options...
apeisa Posted April 11, 2014 Share Posted April 11, 2014 I agree that most of these are good timesavers. Some of them already solved by modules, but I agree, that there is no need for too strict safety nets for developers/superusers. 2 Link to comment Share on other sites More sharing options...
Craig Posted April 11, 2014 Share Posted April 11, 2014 Deleting fields "This field can not be deleted because it is used by one or more template ( s ) ." It should be displayed, in which templates the field is used. This functionality already exists as well - albeit not at that stage of the process On the Fields page, there is a column in the table for "Templates", which has a number in it next to the fields. Click the number and it will show you the templates that are using it. This actually goes to the templates page and activates the "Filter" menu at the top. Link to comment Share on other sites More sharing options...
cstevensjr Posted April 11, 2014 Share Posted April 11, 2014 +1 for some of these, especially the force delete field/template ones. It's apparently a safety feature to make it harder to lose important data, but also very, very annoying at times. IMHO a proper warning would be quite enough: "this will remove [the field from following templates / following pages using this template], are you sure you want to continue?" I'm actually glad that ProcessWire has a lot of this type of safety features. This particular one has saved me many times. Sometimes I'm very bull headed about things. Even with a warning I would have deleted a template (because of course I know what I'm doing). Whenever I get that error, I have to stop and think "Oh yeah, I forgot about that" and then to proceed to delete the template where it won't affect what I have spent hours working on. I can't speak for everyone, but sometimes I think I'm smarter than I am. The safety feature makes me smile because I know that ProcessWire is a development platform that protects me from myself. Maybe there could be an option to turn off some of these safety features for anyone else. I just hope that one doesn't change anytime soon. As stated earlier, some of these suggestions have merit. 6 Link to comment Share on other sites More sharing options...
horst Posted April 12, 2014 Share Posted April 12, 2014 +1 for a config option to lower the security for people feeling like heros seriously: It should be configurable in $config but for superusers only. not seriously: Then I wish to have a module that tests me on login as superuser to check my reactions and according to that enable or disable it. (Or even don't let me login if the testresult is to bad ) Link to comment Share on other sites More sharing options...
benbyf Posted April 23, 2014 Share Posted April 23, 2014 +1 adding fields, or bulk adding? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now