How are we doing so far? (top 125 Drupal modules) #34
Comments
|
Webform? Nobody uses Webform. |
|
@oadaeh 😉 I'll work on porting it after we get some of these critical infrastructure modules fully converted. I'd like to get our main site off of Drupal 7 asap, so I'll probably prioritize that first. CTools I think we could mark off. We have the following pieces of CTools in core:
The primary piece of CTools we do not have is the concept of a plugin, which means combining the "discovery" mechanism with the code implementation. Instead we've standardized on using _info() hooks for discovery. e.g. So... crossed off CTools. 😄 |
|
Entity API is also an interesting one, because we've converted Entities into "real" objects. We integrated about as much of it as we'd want in core. I'm not sure a contrib version of that module should even exist for Backdrop in the first place. See the meta at backdrop/backdrop-issues#49. Crossed off Entity API. |
|
Is there a list of the current status of Backdrop versions? Are they all 'under development' at the moment? |
|
I think most all of them are "under development". I tagged a few stable releases for External Links and Devel module, but I don't think many projects have releases yet. I don't think Github makes it easy to get a list of official releases within an entire group. Yet another reason why we need to get backdropcms.org up and running with a contrib listing. |
|
@quicksketch, you definately are going to need some help with this. Between your day job, keeping up with Backdrop core and the contrib requests that seem to be coming in fairly quickly, you are going to be stretched thin. I suspect your wife might want some of your attention, too. |
|
Hi @oadaeh! Ha, I completely agree. No one could manage a Drupal-sized project alone. We added an additional contrib reviewer (klonos) just yesterday: #45 The contrib group itself is a great way to spread out responsibility. Already with all these new developers coming in, it'll reduce the effort Jen and I have to spend on individual modules. I'm not sure what we'll do about Webform in the short term. I'd love if another developer were to make the initial port but add me as a maintainer (as happened with Insert in #37). @oadaeh if you're interested in helping review applications as well, I'd be more than happy to add you to the contrib management group as well. 😄 |
I propose changing your nickname to "quickstretch" then :p Naughty me! Don't have enough time in my day and still find time to post silly things. Sorry, couldn't help it. |
|
@klonos Ha! |
|
😉 Well ports are still moving on. The folks at CivicActions apparently have taken a stab at porting CKEditor: @docwilmot also is 90% through porting Link module: https://github.com/docwilmot/link. There's just a caveat that it's not actually saving data yet. 😉 No one is working on Date yet that I know of. Libraries API we should work on integrating in core (or parts of it), see backdrop/backdrop-issues#159. Also looks like @oadaeh has filed an issue at https://www.drupal.org/node/2417985. For the time being, it looks like several contrib projects have just started bundling the libraries with their modules, since we're not bound by Drupal.org's licensing restrictions. I think that's fine for most projects honestly. Bundled libraries are so much easier for end-users, though it requires more effort for contrib modules to be updating the bundled libraries all the time. |
|
See #50. Link seems to be working there. |
|
Hey, I just wanted to update the issue summary with links to respective projects in backdrop contrib etc., but it seems I don't have the permission to do so. Hate to be busting people's b@@ls, but this was so much easier on d.org. Do you think it would be a good idea to have this summary some where in bd.org? I like the title: "Porting the most popular Drupal modules to Backdrop - How are we doing so far?" I think it would be good for publicity + it would get people to try them out and report any issues. |
|
Helping to publicize this one on the forum: http://www.reddit.com/r/backdrop/comments/2xx6ix/porting_the_most_popular_drupal_modules_to/ |
|
Hey, don't forget about https://github.com/biolithic/backdrop_colorbox :) |
|
I would like to tackle Views Slideshow and XML Sitemap this Sunday (if no one else), leaving Rules and Date as the only real modules left on this list. Where's the second page list? |
|
I am currently working on a port of Rules. I have done a port of CKEditor for use until it is in core, so perhaps the list could be updated? |
|
Sure, this list is pretty informal anyway. Updated. :) |
|
I added the second page, now this is a list of top 50 modules. Still looking pretty good. 😄 |
|
Can Drupal Commerce be ported ? |
|
I am proposing to start porting Date in the next day or so. |
|
I am starting to work on porting Webform today now that I'm waiting on On Wed, Mar 11, 2015 at 12:42 PM, Graham Oliver [email protected]
|
|
Gee, that was sure an easy port of Webform - nothing broke after making two webforms with random options. I know I have to do lots of testing of the options but I wonder if there is a connection between the owner of the module and Backdrop. |
|
What about Metatag module? |
|
@pablo-romero this was probably missed in the cutting and pasting. I've added it. |
😉 @quicksketch Hey Nate, still don't have enough time in my life, but I can still contribute small things when I find the energy. Can you look into allowing me to edit issues in this repo so I can edit issue summaries? Thanx. |
Sure, I resent a group invitation. |
|
Thanx, Just joined. Going straight to bed though. Will contribute once I make some time. 😴 |
|
Just updated the issue summary with links to the roadmap page and what was done in 1.2.0. Perhaps there's a few issues here and there filed about getting some things in core, but don't have more time now. |
|
I've been posting in gitter, but thought I'd copy my post in here as well: I’m going to try to port the IMCE Mkdir module. I also created an issue in the project's issue queue for it. Hopefully that looks ok. I think this would be a good one to get my feet wet so to speak. |
|
@richie-harris-smc ++ on this matter. There is a lot of documentation out there for Commerce and also a big audience of people that would possibly need a Backdrop version (all the current D7 Commerce users actually). These people have invested a lot of time, energy and resources and I am sure that they would like to have some continuation. It is within the spirit of the Backdrop philosophy to provide a solution that would minimize cost for them. One of our long-used motos was "There is a cost that comes with change..." |
|
@richie-harris-smc @klonos Ok I understand your motivations. I do not know more about Backshop just what is published on its project page. I also understand that while you are working actively Backshop development stagnates. I just wanted you to know about it because I could imagine that there would be a simple upgrade path from D7 Commerce to Backshop too. Also I thought it is possible that there are work done in both projects which would be useful for each other. (These are all supposition I did not check the code.) |
|
Thanks for the ping. I wouldn't currently support a straight port of Commerce 1.x, but obviously don't mind anyone doing it for their own sake. My goal w/ Backshop is to combine the best of Commerce 1.x and 2.x with a philosophy that fits Backdrop's target audience. We can always advise on a Commerce port, though. (Yes, I'd expect to support a migration path into Backshop; but alas, my time is limited. ; ) |
|
Thanks for the answer and for the info @rszrama! |
|
Hi all, I'm new to Backdrop and I'm working on a project that requires Field Collection. If no one else is working on it, I will attempt a port. It's my first. |
|
Can someone point me to a forum or channel where I might be able to get some mentoring on porting D7 modules? I'm trying to port Field Collections and I have a couple of others that I will work on if I get that one, but I'm hitting a wall. All the documentation I've been able to find so far has sort of a 'now make it work' step in the middle. I don't want to clutter this thread with my newby questions. |
|
You may use the Gitter chat for newby question: https://gitter.im/backdrop |
|
https://gitter.im/backdrop/backdrop-issues ? On Thu, May 19, 2016 at 2:03 PM, vonnnew [email protected] wrote:
|
|
@richie-harris-smc how are you doing with the commerce backport to backdrop (back back back :-p). We are considering using backdrop for a proyect, but we need commerce and we could help with the porting. |
|
Joaquin, did you check out Ryan's work at https://github.com/codewombat/backshop ? |
|
fwiw, I haven't touched that in a long while - taking over Commerce Guys became my nights / weekends hobby project. I haven't lost hope, but it's back burner atm and was dependent on ongoing contribution to the core Entity API. (I also didn't really want to port Entity Reference myself, but that's what it needs. ; ) |
|
Looks like this list needs to be updated. I saw releases for Profile and Better exposed filters in backdrop-contrib. Probably there are ports of other modules from this list too. |
|
Pinging @richie-harris-smc |
|
Has anyone thought of tackling (or begun tackling) Apache Solr and Facet API modules? |
|
Views Data Export can be checked off this list. I think there are several others listed here that have been ported. |
I also think some of them should be put back on the list, like Webform. Porting is only the start, maintaining is mandatory. For example, I've built a website this weekend which evolves around 2 forms, so I installed Backdrop + Webform. I built one form which has around 20 fields and fieldsets, and started working on the conditionals. I soon had Javascript errors when conditionally showing a fieldset. After some searching, this is fixed in Drupal's Webform, as well as many other fixes, around 4.5/4.6. So I deleted Backdrop and installed Drupal 7. Which feels like a big step back in time, but Webform works perfectly. Backdrop's Webform is a fork of 4.4, according to it's readme. I installed 4.14 on Drupal, which is also a half year old. This even made me rethink using Backdrop. |
|
@MrHaroldA I understand that when things need to get done they need to get done, so building something with D7 is unavoidable, but I have to also point that maintaining is as mandatory as reporting issues and helping getting them fixed. |
This is the backlog for Webform: backdrop-contrib/webform#39 That's not something I can do with my very limited spare time. In fact, it might be quicker to port D7-4.14 instead of merging all patches separately. But this is only Webform. I believe that all projects merged into Backdrop are in great shape, but I doubt that the ported contribs are. |
@richie-harris-smc have you made any more progress on a 1:1 port of commerce 1? |
|
@TonyTheFerg I passed Commerce through Coder Upgrade and fixed a few basic things just to get it to install without error. Its here: https://github.com/backdrop-contrib/commerce I had reached out to @rszrama here https://github.com/codewombat/backshop/issues to let him know. Thats about as much as I intended to do there. I dont feel confident I know enough about something as touchy as ecommerce to finish this., but very happy to help anyone who wants to take it up again and get the bugs squashed. |
|
I've checked Localization update which is ported but without official release. Does it matter for the status if there is a release? |
|
What about porting the advanced forum module? I think 3 people already requested this almost a year already. Tried to use forum-ng but is not in production state. Other person tried to build a forum with views. Personally I'm still in development. This lack of advanced forum module got me several delays in my dev. Currently I'm using the existing forum module but I think is not sufficient for a respectful forum. |
jenlampton
changed the title
and others
Drupal 7.x modules list by most installed (top 125):
(thought it would be nice to see what's missing - we're not doing too bad!)
Key:
In core or replacedModules:
Views(part of core)Chaos tool suite (ctools)(part of core)Token(in core since 1.1.0)Pathauto(in core since 1.1.0)Entity API(mostly in core)Administration menu(part of core)Date(in core since 1.2.0, Add date (field) module to core backdrop/backdrop-issues#478)CKEditor - WYSIWYG HTML editor(in core since 1.2.0, [UX] Add Rich Text editor (WYSIWYG) to core backdrop/backdrop-issues#101)Link(in core since 1.2.0, Add link (field) module to core backdrop/backdrop-issues#240)Email(in core since 1.2.0, Add email (field) module to core backdrop/backdrop-issues#476)jQuery Update(latest jQuery in core available)Module Filter(in core)Panels(Layouts in core)Features(could still exist but CMI handles most of it)Views Bulk Operations (VBO)(in core)Media(we have file entity + media browser in core)CCK(ha! In core obviously)IMCE Wysiwyg bridge(images in ckeditor in core)Variable(CMI in core)Context(Layouts handle context in core)Advanced help(we encourage inline or online help instead of bundled documentation)ImageAPI(in core since D7)FileField(in core since D7)Strongarm(CMI in core)Superfish(smartmenus in core)ImageField(in core since D7)Block ClassLayout builder allows custom block classesFile entity (fieldable files)(in core)MollomThe service has been discontinuedSite verification(part of metatag)Features Extra(config in core)Elements(part of core)WYSIWYG Filter(rich text editor in core)The text was updated successfully, but these errors were encountered: