Are there any plans to port the module to D8?

CommentFileSizeAuthor
#2 2597053-aet-d8_port-2.patch38.11 KBbgilhome

Comments

matsbla created an issue. See original summary.

bgilhome’s picture

StatusFileSize
new38.11 KB

Here's a port that seems to be working fine, based off current 7.x-1.x-dev.

As a WIP, I've removed the aet_insert submodule since I don't need that functionality.

geek-merlin’s picture

Title: Drupal 8 » Port Advanced Entity Tokens to Drupal 8
geek-merlin’s picture

steveoriol’s picture

the patch of bgilhome works very well for me !
Formidable ;-)
I think this version can really make a great start dev version for aet For D8 (8.x-1.x-dev) ?

colan’s picture

I hope to get this rolling with #3161982: Offering to maintain Advanced Entity Tokens.

Plan:

  1. Create a D8 branch. It's actually called "2.x" for Drupal 8+
  2. Make it the default.
  3. Create a release node for it.
  4. Commit the above patch.
  5. Enable commit & issue testing
  6. Add tests
  7. Refactor code to make it object oriented with small methods
  8. Make any other necessary changes (e.g. remove deprecated code, fix DrupalCI coding standards errors).
  9. Release alpha1.
  10. #3051573: [NO PATCH] Add this module to ecosystem list of Token, Entity , Entity Token modules
  11. Move all feature requests to the new queue.
  12. Re-add UUID support (as this was removed in the above patch).
  13. Release another alpha.

  • bgilhome authored fd4065f on 2.x
    Issue #2597053 by bgilhome: Drupal 8 port.
    

  • colan committed 98e6bca on 2.x
    Issue #2597053 by colan: Added Drupal 8+ compatibility...
  • colan committed ac50adf on 2.x
    Issue #2597053 by colan: Deleted outdated non-markdown README.
    
  • colan committed f3d0bd1 on 2.x
    Issue #2597053 by colan: Added README in markdown format.
    
colan’s picture

Title: Port Advanced Entity Tokens to Drupal 8 » Port Advanced Entity Tokens to Drupal 8+
Version: 7.x-1.x-dev » 2.x-dev
Status: Active » Fixed

Thanks all. This is now done; I've released a couple of alphas. For follow-up issues, see #3162284: Stable release roadmap.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.