Posted by NancyDru on September 22, 2009 at 2:23pm
| Project: | Util |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | reviewed & tested by the community |
| Issue tags: | D7 porting, d7 ports, port to d7, Roadmap |
Issue Summary
When we get around to starting this (I may soon), we need to consider the complaints in #583632: Clear log description needs clarification when updating log_clear.
Comments
#1
#2
if dblog_ext gets into core #582622: provide hook for dblog_filters
then a rewrite of log_clear would be needed
also, for current 6.x-3.x-dev there is pending #623736: merge log_clear & dblog_clear
#3
marking as roadmap
#4
subscribe. surprised more folks haven't asked about this since last year! any progress?
#5
I am still alive. But no, I haven't done any D7 coding on this yet.
#6
Subscribing
#7
...coming from #1007636: Provide means to set defaults for new content types' settings + mass edit & overview of existing content type's settings
#8
subscribe
#9
Subscribe; chances are I'll be doing a direct port of this as it is by mid-day tomorrow (that is, my mid-day), and posting it here.
#10
This is only a basic conversion, running it through coder_upgrade. I have not tested it yet, but thought it might be helpful to those wanting it, or as a start for the upgrade for the developers.
I used Coder-7.x-1.0-beta6, and the util-6.x-3.x dev build from Jan 17, 2011.
I also altered the filename to allow uploading. Remove the '.jpg' and the underscore from the end of the file name, and extract like any other module (the patch doesn't seem to be created and I don't have the time to diagnose the problem with it at the moment).
#11
Thanx for you time and effort Travis.
PS: Changing the issue's title since we now have something to test ;)
#12
subscribing
#13
#14
subscribing
#15
#17
sub
#18
There must be something wrong with my brain. I keep getting a page not found.
#19
sub
#20
subbing
#21
sub, marked as postponed for almost 2 years? Are there other modules with similar functionalities? I haven't been able to find anything but maybe someone knows something I don't. I'm new to Drupal and php, so the programming part is largely over my head. Thanks so much.
edit: (more specifically, the Permissions Fieldset Manager feature)
#22
There are similar functions here and there - some even in core.
#23
subscribe
#24
Certainly this should be an active issue and the community priority is at least "normal." :)
#25
I needed some Util features in D7 (actually, I only needed the module and permission fieldsets and the module weight field) so I rewrote those into a single D7 module. As I don't want to fork or undermine the original work by any means, I'm rather willing to contribute it.
It is, however, more of a rewrite than a port. Although I retained the original idea, I changed the implementation quite a bit. There is no config page for the module, the checkbox lists governing the open-closed state of the fieldsets appear directly on the modules and permissions pages themselves, in front of the actual data. Also, the placement of the weight field is different from the D6 version: instead of gluing it to the end of the description field of the module tables, it got its own column all right (something that should have been done already in D6, I guess :-) ).
#26
If you are willing to share, please post your version here for comment. There are also some themes that implement the open/closed features in D7, so separate modules are more flexible. In reality, the base module was really more a packaging formality, but some really simple functions could reside there. I can't remember whether I committed it or not, but I do have a version with a small PHP error level report in the base module.
#27
In my own case, combining them into a single module seemed more logical because I happen to use them together. The two parts are actually quite separate still, so pushing them apart into different modules again wouldn't be a problem at all.
Anyway, as you will see, this one has a simpler approach now. Only partly because I removed one feature, the all open/all closed options (would be easy to add back but frankly, I didn't consider it important enough, I tend to leave the state checkboxes in the same position for a long time, this is not something I modify often) but mostly because of the simplified approach of not providing a separate settings page and also due to the different solution of not replicating the whole form routines but only using override theme functions.
Oh yes, I renamed the module itself but the name isn't registered or anything, it's just what I used on a site of mine in the /custom directory. I don't want to suggest anything like a compulsory name change... :-))
#28
thanks djg_tram this is working great for me-
on both drupal 7.7 and drupal 7.9 installs.
vincent, in buffalo
http://basicmagic.net
#29
Please, whoever has permissions, just make the following:
I tried and it works, of course, it needs more testing, patches, etc That should be done in dev version.
Thanks in advance.
#30
djg_tram is now a maintainer.
#31
Head 7.x-1.x has been created. The module is renamed back to perms_fieldsets and marked as belonging to the Util package. Sibling projects will be added for sure but what's your current stance about Util.module itself? Should it be ported (not that it would be hard to do so) or simply leave them as loosely related modules in the same package?
#32
The main Util module is there for really small things that only need a form skeleton. The only one using it is the error reporting level, I think. But, if for no other reason, it is the raison d'etre for the package, so should remain for political sake.
As for collapsing the permissions and modules, I would deprecate those in favor of the Admin_Menu module which does that too, maybe not as nicely, but it does that.
I have another function to add (profile date limiter) to add whenever I learn Git.
#33
About collapsing, do think of us who are satisfied with the new Admin UI of D7 and don't install the separate Admin Menu... :-)
I've moved from plain vanilla msysgit to SmartGit recently, about a week ago, and have no problems whatsoever. Can I be of assistance?
#34
Well, there are 34,570 known users of the 7.x version of Admin_menu, including every site I have created. I wouldn't mind the core version if it included the cache clearing.
--------------------------------------------------------------
Yes, I would like to use SmartGit (even though msysgit wouldn't uninstall). Use my contact form and let's see if we can overlap times (UTC - 5) at all. I appreciate the offer.
#35
Well, then, it's easy. A challenge. A module for Util that allows us to keep the stock admin menu but adds cache clearing... :-)
I send a PM.