Posted by lolmaus on August 12, 2010 at 11:41am
25 followers
| Project: | Automatic Nodetitles |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
| Issue tags: | Features integration |
Issue Summary
Features is getting more and more actual.
I'm trying to make use of Features in my development→production workflow.
Automatic NodeTitles is one of modules that won't preserve its settings in a feature.
Please don't fall behind.
Comments
#1
As a workaround, Strongarm module can be used to make Automatic Nodetitles settings to be Features; this is because Automatic Nodetitles settings are Drupal variables (all beginning with "ant_"), and Strongarm makes these usable in Features.
#2
Can Strongarm be used by end user? Or it is an API provider that requires module's modification?
#3
Yes it can be used by an end user, without modification of code in Automatic Nodetitles or Strongarm.
#4
Features support would be valuable to my work. Thanks,
#5
There's a patch (that need update?) in #728004: Allow abitrary modules to alter the pipeline where auto node title can tell features to automatically export variables when the node type is.
#6
Uploading here to speed the process. Note that this patch needs some tweaks
#7
#8
Subscribing.
#9
subscribing
#10
subscribe
#11
I tested the patch in #6 and was able to encapsulate my Automatic Nodetitle settings into a Feature. I fixed a typo and rerolled using git.My apologies, I got my dev environments confused while testing this. As mentioned in #1, this patch is unnecessary if you use Strongarm to capture your Auto Nodetitle settings.
#12
Rerolling for D7.
The hook has changed some since the last couple patches, in both name and parameters.
#13
Here's the D6 version. Same thing, but "Implementation of" instead of "Implements" to match.
#14
Both Tim's D6 and D7 patches are clean and tested.
#15
...because every time this thread pops back up I forget what module it's for! :)
#16
Subscribing !
Need this !
#17
subscribing
Works with strongarm, but would be nice if either the variables were named "auto_nodetitle_***" or if the settings were automatically saved with the content type to the feature.
#18
After running into #1078478: Multiple features and strongarm conflicts and #904558: Multiple features and strongarm conflicts, this needs to follow their lead.
This is for D6, I'll see if I can do a D7 version later.
#19
subscribe
#20
patch in #18 looks good to me, any testers?
#21
Subbing
#22
I've just done some testing, and the variables seem to be exported fine (using php code on two content types in the same feature, both got into the feature strongarm file).
I haven't tested pushing the feature around nor installing it on a new installation, but I suppose it should work fine since then strongarm/features would take care of that.
Looks good to me!
[edit]
I also just checked and the vars got into the features[variable][] array in the .info file as well.
[/edit]
#23
I tried the patch in #18, but for whatever reason it is not working for me. When I put some logging into the features module, I can see the variables get added to $pipe, but the export does not contain the data. Any ideas on where to look?
#24
@HitmanInWis did you enable Strongarm?
#25
Ah - nope - I didnt realize it was a requirement/dependency. I'll try that.
#26
Just another data point, patch in #18 works great (it does require strongarm to be enabled) and the node titles are created properly on the feature enabled site.
Any chance this can be committed to the dev?
#27
Patch #18 is dependent on another issue, which needs work
#28
So should we postpone committing #18 until strongarm is fixed?
#29
Subscribing
#30
#18 is working fine for me as well.
I'm not sure what the dependency on #1078478: Multiple features and strongarm conflicts is? If this is still the case, it would be great if someone could summarize it and mark this issue as postponed.
#31
How this ticket is done, whether the first simple patch, or the more complex patch is, depends on which patch gets in, so postponed sounds appropriate
#32
Postponed on #904558: Multiple features and strongarm conflicts
#33
Un-posponing due to a fix on the above issue.