Closed (fixed)
Project:
Field reference delete
Version:
7.x-1.0-beta1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Jan 2015 at 16:56 UTC
Updated:
11 May 2015 at 14:42 UTC
Jump to comment: Most recent
Comments
Comment #2
David_Rothstein commentedComment #3
David_Rothstein commentedAdding a tag.
Comment #4
David_Rothstein commentedRenaming the tag to be more specific.
Comment #5
David_Rothstein commentedOne more time :)
Comment #6
oadaeh commentedChanging the tag to the recommended one, per the third paragraph of this page: https://api.backdropcms.org/node/28621
Comment #7
David_Rothstein commentedI actually used a different tag on purpose, since this isn't really a port. Maybe we should leave both tags for now.
I have a blog post coming out (probably this week) which raises that as a topic of discussion... I'm curious how best to track or otherwise deal with modules that don't necessarily require a separate Backdrop version on GitHub (because the Drupal.org version can work with Backdrop instead). Not sure how common of a situation it will be.
Comment #8
hass commentedWe support Backdrop on d.o? Really?
Comment #9
David_Rothstein commentedThe blog post mentioned above is now posted here, by the way: http://tag1consulting.com/blog/how-maintain-contrib-modules-drupal-and-b...
Comment #10
hass commentedI have ported GA and this is not possible in one code for sure. A native backdrop port requires tooo many changes.
Comment #12
drupalshrek commentedPersonally, I am against any support for Backdrop on d.o.
If the Backdrop folk want to fork Drupal, fine, good luck to them, but let's not muddy the Drupal waters with Backdrop stuff. Even this issue does that in two ways: