Problem/Motivation

In 3.0.x we require extra_field_plus 8.x-2.x. As there are breaking changes in extra_field_plus 3.x we have to create a new 3.1.x release to update our implementation and before lock 3.0.x on extra_field_plus:^2

Steps to reproduce

Proposed resolution

See above

Remaining tasks

User interface changes

API changes

Data model changes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

Anybody created an issue. See original summary.

anybody’s picture

Title: [3.1.x] Require extra_field_plus 3.x and lock 3.0.x on extra_field_plus:^2 » [PP-1][3.1.x] Require extra_field_plus 3.x and lock 3.0.x on extra_field_plus:^2
Status: Active » Postponed

Postponed on the official release of readmore_extrafield_plus:3.0.x-alpha0

anybody’s picture

@Grevil once the other issues are fixed here and readmore_extrafield_plus:3.0.x-beta0 is out, you may create the 3.1.x branch!

I think it's better to fix all other things before so we have the fixes in both versions.

Ping me then :)

anybody’s picture

Assigned: Unassigned » anybody
anybody’s picture

Status: Postponed » Active

3.0.0-beta0 of extra_field_plus is out :)

  • Anybody committed f1c860b on 3.0.x
    Issue #3305929 by Anybody: Limited compatibility with specific versions...

  • Anybody committed 8c6bc49 on 3.1.x
    Issue #3305929 by Anybody: [PP-1][3.1.x] Require extra_field_plus 3.x...
anybody’s picture

Status: Active » Reviewed & tested by the community

I made the changes, let's see what the tests say...

  • Anybody committed 0760497 on 3.1.x
    git commit -m 'Issue #3305929 by Anybody: [PP-1][3.1.x] Require...
anybody’s picture

Version: 3.0.x-dev » 3.1.x-dev
anybody’s picture

Assigned: anybody » Unassigned
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

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