Hi. I have been working on a port of css_injector to Backdrop CMS. I have not pushed a branch to github yet but will soon. I am announcing it here, as recommended, to find out if the current maintainers, original author, or anybody else wants to be involved or take it over. I will continue to do my best to maintain this branch in the mean time.

We are looking at migrating some of our web sites to Backdrop and CSS Injector is one of our most used modules. This is my first time porting a module or working with any Drupal code, so I am not sure if I am doing it all correctly, but what I have done so far seems to be working.

Comments

vls created an issue.

kreynen’s picture

I'm not really interested in porting the 7.x-1.x branch or even the 7.x.-2.x branch, but if you want to merge css_injector and js_injector into a single project, I'd be up for helping with that. Backdrop is on our shortlist of options we are considering instead of moving 1000 D7 sites to D8. This is as good as any project to dig in.

vls’s picture

Hi kreynen.

There are a couple of possible options for that route as I see it.

  1. Merge the two Drupal 7 projects, as you mentioned, or
  2. Port asset_injector, which already combines them, from Drupal 8 to Drupal 7, then port it to Backdrop. I don't know how involved that would be. The Backdrop docs recommend porting any other versions to Drupal 7 before attempting a port to Backdrop.

I don't know if I will have the time for the learning curve to combine them or to backport the Drupal 8 module. If possible, that would be a task better suited for one of the existing maintainers or developers. If you are interested in doing it I could still handle the Backdrop porting. I think I have learned enough, so far, to handle that from my experience of porting css_injector.

You could start where I left off with my existing port, or if you want to back port asset_injector or join the other two projects, strictly under Drupal 7, I could re-port the new project once you are ready.

If it looks like it may take a while, I will likely go ahead and continue pursuing the css_injector port myself in the mean time to fulfill our immediate needs.

I have created an issue about it for Backdrop already.

https://github.com/backdrop-ops/contrib/issues/256

vls’s picture

I did some testing and some thinking on it and learned it's easy to combine the two modules into a single module package and have them show as separate modules in Drupal, but I'm not really seeing any advantage to doing so. Most of the time I only need to enable css_injector. Also, I like the ability to upgrade each module independently.

js_injector has a different author and maintainers from css_injector, so I would probably need submit another issue to determine what roles they would want to play in the js_injector port to Backdrop. I don't even know if they would want to be involved in or maintain a port that combines it with a module that they don't maintain.

So, I think I am going to go ahead and complete the stand alone port of css_injector to Backdrop, and, perhaps later, do a separate port of js_injector if nobody else does it and we need it or others start requesting it.

kreynen, after that, if you or any of the other maintainers of css_injector would like be involved or to take over maintenance, I will be happy to oblige.

I will do a followup post here, to let everybody know, once it is available in the Backdrop repo.

vls’s picture

I have completed the css_injector port to Backdrop.

https://github.com/backdrop-contrib/css_injector

If any of the current Drupal maintainers are interested in co-maintaining the Backdrop version, it would be helpful. Just let me know.

I ported the 7.x-1.x-dev branch for stability since the 7.x-2.x-dev branch is a complete rewrite that never had a release and has not been updated in 3 and a half years.

kreynen’s picture

That's really a shame since the 1.x branch still doesn't really work on Pantheon.