To do:

Original description

I've ported main functionality of this module to D8: https://github.com/dealancer/computed_field. There are still few things to do.

We need to create 8.x-1.x branch and copy module code to continue development on Drupal.org. Here is also a ticket at D8 porting tracker project: https://www.drupal.org/node/2587493

Comments

dealancer created an issue. See original summary.

dealancer’s picture

Category: Bug report » Task
dealancer’s picture

Status: Active » Closed (fixed)
francewhoa’s picture

Title: Drupal 8 port » Port Computed Field to Drupal 8
Version: 7.x-1.x-dev » 8.x-1.x-dev
Status: Closed (fixed) » Needs work
Issue tags: +Drupal 8

dealancer :) Thanks for the port

I suggest to leave this ticket open while the port from Drupal 7 to 8 is in progress. How does that sound?

We would be happy to contribute testing patch, quality assurance, documentation, and agile project management services if needed

Any additional volunteers interested to join the efforts to port "Computed Field" module from Drupal 7 to 8?

Related pages

I updated this ticket title so it's easier to find with aggregators and searches

francewhoa’s picture

All, the Drupal 8 branch is also at https://www.drupal.org/node/2588719

francewhoa’s picture

Fixed my typo. I meant to just add the link to the branch.

francewhoa’s picture

dealancer’s picture

Francewhoa,

Yes please, we need help. Your work on tests and docs are welcomed! Here is link to the test issue: https://www.drupal.org/node/2588725.

maxilein’s picture

What is the difference between 8.x-1.x and 8.x-2.x?

maxilein’s picture

Here is the answer to my question: https://www.drupal.org/node/2665434#comment-11100507

colan’s picture

Version: 8.x-1.x-dev » 8.x-2.x-dev

I need this module for D8 now so I'm trying to get it organized. The good news is that I'm already a maintainer.

See the first 2.x release for details. but I've deprecated the 1.x branch and marked the 2.x one as supported. I also moved all open 8.x issues from 1.x to 2.x.

Things should be less confusing now.

#4: Your offer to help with documentation and tests are still welcome now that we have a potentially working module again.

colan’s picture

Anyone want to volunteer to change all of the D6 issue states to Closed (outdated)? It would be greatly appreciated!

colan’s picture

Status: Needs work » Needs review

I got a good amount of work done in the last couple of days. Please test the latest alpha, and report any issues. Thanks!

dqd’s picture

@colan: please review #2913014: Not using selected field type's formatters. Not sure, but I assume this is a missing feature from the D7 to D8 port.

colan’s picture

Issue summary: View changes
k4v’s picture

I don't like to spoil your efforts here, but in my view it's not a good idea to execute PHP code from the database with eval() -- in D8 this should be deprecated.

The module for D8 should have the same disclaimer as the PHP filter module, that was removed from core:

https://www.drupal.org/project/php

I'm sceptical if this module can acquire the green shield for the D8 version.

mmjvb’s picture

@colan

Anyone want to volunteer to change all of the D6 issue states to Closed (outdated)? It would be greatly appreciated!

Done

What about 7.x active support request last updated > 2 years ?

colan’s picture

Would probably be better to wait for that just in case someone volunteers to help answer those at some point before Drupal 9 is released.

Thanks for the D6 work!

colan’s picture

Status: Needs review » Fixed

#16: Added to project page. Great idea; thanks!

See the new stable release.

Status: Fixed » Closed (fixed)

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