Closed (won't fix)
Project:
Strongarm
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
11 Oct 2009 at 21:04 UTC
Updated:
25 Mar 2017 at 20:42 UTC
Jump to comment: Most recent file
Comments
Comment #1
dmitrig01 commented1.x isn't supported apparenlty
Comment #2
drewish commentedSeems silly not to apply this especially considering they still haven't got a final 2.x release out. I'd similarly came to this patch.
Comment #3
jmiccolis commenteddrewish, yea we're not maintaining the 1.x code at all or advising anyone to use it. We came to the conclusion that the approach we took in that series wasn't the right one, and have abandoned it. The 2.x branch has an RC now, and should be going stable very soon.
Or is there something preventing you from moving to 2.x?
Comment #4
drewish commentedjmiccolis, well aside from the fact that there's no upgrade instructions? ;)
Comment #5
jmiccolis commentedouch.
:)
Ok, off the top of my head:
fin.
PS let me know if this works for you and we should probably add something like this to the README.txt or similar.
PPS Strongarm 2.x works differently than Strongarm 1.x - it's less strong now. It won't override values that are in the database, just ones that module authors thought were good ideas.
Comment #6
drewish commentedOkay well that much was on the project page. But we're not using features, does it even make sense to use the module without?
Comment #7
jmiccolis commentedNot using features you say? Ctools does the lifting here, so you can still use strongarm. The hook is a bit more verbose now (the particulars of the format are handled via ctools), but pretty straight forward still. For example:
I know that ctools has a bulk exporter that could work here, but I haven't tested that with strongarm at all.
Comment #8
yhahn commented