Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
This module's status is currently beta, which means the module is not supported by the security team and it is unclear to users whether the module is safe to use in production.
Proposed resolution
Tag a stable 1.0 release.
Remaining tasks
- Define a roadmap of release-blocking issues/tag them with "D7 stable release blocker" in the issue queue.
- Solve those issues
Current open issues tagged with "D7 stable release blocker".
User interface changes
Will follow from release-blocking issues.
API changes
Will follow from release-blocking issues.
Data model changes
Will follow from release-blocking issues.
Original report by Babymaggie
Is this module now abandoned?
Comments
Comment #1
Balbo CreditAttribution: Balbo commentedLast release is from December '12. Is this a production stable release?
Comment #2
jlea9378 CreditAttribution: jlea9378 commentedIf it isn't abandoned can anyone help with my issue?
#2030011: Permissions not being saved.
Comment #3
zilla CreditAttribution: zilla commentedit seems to be abandoned since last winter, which is a bummer.
what is even more surprising to me that this is not a standard configuration option in core when creating or managing content types! confounding.
this is one of the most commonly requested tips on forums, how to remove formatting guidelines and get rid of the clutter.
Comment #4
mgiffordThis issue has been sitting here for a while now. I opened:
#2212129: Better Formats Seems Abandoned - Please Change Status
There was activity in September. Perhaps it's just a matter of the maintainer (like so many others) needing help maintaining it.
Comment #5
dragonwize CreditAttribution: dragonwize commentedI have not abandoned this module, however, it is true I have not had time for it lately.
I monitor the messages as they come through and there are not currently any issues marked RTBC. Nor has anyone come forward requesting to help with the module. So it would seem to me from that evidence, that either the module is fine as it is, or the community doesn't have time for it either.
All patches and serious maintainer requests will be considered.
Comment #6
mgiffordThanks @dragonwize!
I closed that other issue.
Can you change the maintenance status if you want help maintaining it? Having it set as Seeking co-maintainer might help.
We really don't have a means to draw new folks in as maintainers....
#42232: Help Maintainers Manage Issue Priority by Encouraging Voting or #2207949: Inspire New & Less Active Users to Become More Engaged with Drupal.org might help.
Is it possible to have a new stable release?
Comment #7
mengi CreditAttribution: mengi commentedOn the project page it reads;
According to the usage statisics 28,000 sites are using 7.x of this module. Seems like it is stable and there aren't any open stable release blockers.
A 1.0 release would be great.
Comment #8
Gabriel R. CreditAttribution: Gabriel R. commentedA release would be appreciated. I'm hesitating between using the dev or beta releases.
Comment #9
tille CreditAttribution: tille commentedjust confirming and cheering: would be very nice to have a stable release :/
Comment #10
Alan D. CreditAttribution: Alan D. commentedI think the query "Module abandoned?" was really a not so polite way of asking for this.
Large dev user base seen, but it is difficult to tell where these are from since the developmental roadmap has been so protracted out...
However: 30,411 users with 7.x-1.0-beta1, and the current diff between the last tag & the 7.x-1.x branch contains a singular typo fix and a fix for a really irritating PHP notice. (patch below)
Happy to tag and release this myself if required, but I am not putting my hand up to maintain anything other than any negative side effects of the above (aka, nada).
Comment #11
dragonwize CreditAttribution: dragonwize commentedThe current beta release has a couple major issues, refer to the issue queue. Meaning that the current state is not in stable release shape.
Beta is a correct tagging and users should be have to be ok with that tag to use the module. The number of people is not the only factor that goes into tagging something stable, if it was we would have a lot of unstable dev code being tagged. Once stable it is a contract that we have tested and know it to be good and it then subjects it to all of Drupal's standards, including security checks.
I will not tag a stable release as is, and if you are not going to support it then you should not as well because if you do tag it you will be responsible for it .
Comment #12
Alan D. CreditAttribution: Alan D. commentedlol, your standards are higher than many projects... I could easily point to some from core ;)
Comment #13
CD CreditAttribution: CD commentedJumping on board here and following.
Re: Mengi's comment #7
Is this module safe to use? Yes/no?
All I want to do is remove:
Web page addresses and e-mail addresses turn into links automatically.
Allowed HTML tags:
I tried string overides but I can't get rid of the bullets and the second line.
There is a piece of code for template.php https://www.drupal.org/node/35122#comment-9433771
Not sure which direction to take.
Ideally, I'd get rid of everything, so no choice of filtered of plain text, just make it an admin choice. My client hates that there is a choice there and the techie html info under it. Why is it there, just get rid of it as it confuses us ...
Anyway, please let me know.
Comment #14
eelkeblokCan we use this issue to define a roadmap as to what is needed to get a stable release? (Or in other words, what would be needed to get to a stable release?)
Comment #15
eelkeblokUpdate summary with issue template.
Comment #16
eelkeblokComment #17
eelkeblokComment #18
Alan D. CreditAttribution: Alan D. commentedUpdated the title only. It makes it easier to track what this issue is from places like https://www.drupal.org/dashboard :)
Comment #19
rooby CreditAttribution: rooby commentedThere are no issues with the "D7 stable release blocker" tag currently.
Based on #11, maybe we should make the list all major and critical bugs?
I will put some time into progressing the bug issues ASAP.
Comment #20
rivimeyIt would be good to close out this request -- 5 years is a while after all -- and I guess simply merging any easy RTBC and tagging the results might be a good enough response.
Comment #21
joseph.olstadComment #22
joseph.olstadReleased this:
https://www.drupal.org/project/better_formats/releases/7.x-1.0-beta3
And for those using PHP 8.0, PHP 8.1, PHP 8.2, use the latest 2.0 release (currently 7.x-2.0-beta1)
https://www.drupal.org/project/better_formats/releases/7.x-2.0-beta1
Comment #23
joseph.olstad1 Fix since 7.x-1.x-beta3
#2832330: Removing the format field breaks other modules
2 Fixes since 7.x-1.x-beta2
#2896131: XSS issue in the codebase
#2118951: Fix for a notice: index not found "fieldable'
2 new features since 7.x-1.x-beta2
#2845424: Allow FAPI forms to trigger Better Formats programmatically
#1689630: Change default text processing to filtered text
Comment #24
joseph.olstadhttps://www.drupal.org/project/better_formats/releases/7.x-2.0-beta3
and
https://www.drupal.org/project/better_formats/releases/7.x-1.0-beta5
Comment #25
steinmb CreditAttribution: steinmb as a volunteer and at University Of Bergen commentedLooking at the activity for this module. Will we ever have a 7.x-1.x stable version? And why do we want that when 7.x.2.x already have first RC out?
Comment #26
joseph.olstad7.x-2.0-rc1
and 7.x-1.x-beta6 are tagged
afaik, they should both compatible with PHP 8.2
7.x-1.x is by far the most installed
Comment #27
joseph.olstadhttps://www.drupal.org/project/better_formats/releases/7.x-1.0
tagged and released
Comment #28
joseph.olstadComment #29
steinmb CreditAttribution: steinmb as a volunteer and at University Of Bergen commentedI stand corrected. Thank you for blowing through the issues and pushing a new version.
Comment #30
skylord CreditAttribution: skylord commented#3262304: [PHP 8] Returning bool from comparison function is deprecated was not backported to 1.x and version 1.0 still shows warning on php 8.1