Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Could we have a new release please? :-)
The current 1.x release is quite out-dated and the dev version includes important fixes such as the working features integration.
Comments
Comment #1
Stalski CreditAttribution: Stalski commentedYes, time to change priorities. Sorry for the delay
Comment #2
dasjothis would be great, the last version is from october 2011 :)
Comment #3
gerontas CreditAttribution: gerontas commentedAny progress please?
Comment #4
nils.destoop CreditAttribution: nils.destoop commentedA new release will be done when following patch is committed. Calling for testers :) #2057943: Merge fieldgroup 2.x features into fieldgroup 1.x
Comment #5
tsvenson CreditAttribution: tsvenson commentedI hear the call, but the patch is really big so hard for me to know all it does. See comment I just posted in that issue.
Comment #6
kscheirerjebus yes we need a new release! just what you have right now in 7.x-1.x-dev would be fine, that contains a ton of fixes from the 2-year-old recommended release.
Latest is 7.x-1.1+68-dev!
Comment #7
geerlingguy CreditAttribution: geerlingguy commentedI've been using 7.x-1.1+68-dev for some time now, on a few different sites, without issue. I'd love to see a 1.2 release soon!
Comment #8
nils.destoop CreditAttribution: nils.destoop commentedRelease can be done because #2057943: Merge fieldgroup 2.x features into fieldgroup 1.x has been committed yesterday. However, git is currently down for pushes, so can't push tags to drupal.org.
Comment #9
nils.destoop CreditAttribution: nils.destoop commentedrelease has been done
Comment #10
tsvenson CreditAttribution: tsvenson commentedAwesome, thank you so much guys.
Comment #11
ParisLiakos CreditAttribution: ParisLiakos commentedso, did anyone tested upgrading sites from 1.1 to 1.2?
this release brought markup changes which is not cool..why not keep them in a separate branch and release a 2.0 version?
not only that, but the 1.2 release notes have no info on how or what changed, just a general, many bug fixes and feature additions. at least it says that the 2.x branch merged so it helps you be suspicious a bit
Comment #12
nils.destoop CreditAttribution: nils.destoop commentedThe 1.2 does not add any markup changes that where not yet in 1.x dev. The only big change is that css classes went from underscores to dashes. This is because classes with underscores are no valid css classes.
There used to be a 2.x branch, but we merged that one into 1.2 because the only big chance, was the moment of rendering (now in preprocess, used to be in pre render). This was necessary because some bugs could never be fixed, if we didn't do that major change.
Comment #13
ParisLiakos CreditAttribution: ParisLiakos commentedShouldnt this be at least mentioned to the release notes?
Classes with underscores are perfectly valid. maybe not inline with drupal standards but not a reason for a BC break..They should be kept there since the cycle is on the stable phase..Tens or hundreds of selectors may be depending on them and updating them all is not really viable if you maintain multiple sites.
I know i sound like a d*k here, but can we get some docs in release notes for this change, and how can people restore those classes if they depend on those?
Comment #14
gerontas CreditAttribution: gerontas commentedI think I agree with ParisLiakos - IF the css changes mean that changes need to be made in theme css then this is a major change. I have not had time to test the latest version (I was using the dev version so there may not be changes in my case) but if someone updates their site and the css breaks, then they need some info about what to do. A list of the classes that were changed perhaps? That would make it easier to do a search and replace.
Comment #15
arx-e CreditAttribution: arx-e commentedI was lucky enough to find out about those underscores after only a few minutes of anxious frustration and even luckier to have only one site with filedgroud implemented but please:
Place a BIG FLASHING NOTE out there in the module page and in the release notes!
I don't want to be rude but this as release note "A lot of bugfixes and new features" is not worthy of such a great effort and project.
Comment #16
ParisLiakos CreditAttribution: ParisLiakos commentedi posted a fix to restore css classes on #2077695-9: field group entity display bug after update
i suggest including it in release notes
Comment #17
hass CreditAttribution: hass commentedSearch *.css for "_" and replace with "-", Save, Done, Forget it.