Fatal error when using on entity types created with ECK

Created on 2 November 2023, about 1 year ago
Updated 6 November 2023, about 1 year ago

Problem/Motivation

No apparent compatibility with ECK module.

Steps to reproduce

-) Create a custom entity type X with ECK.
-) Go to /admin/config/content/easy-entity-field
-) enable the status for X and save
The Easy Entity Fields breaks and the php log shows

Proposed resolution

A fix to make it compatible unless it is an ECK bug.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report
Status

Closed: outdated

Version

1.0

Component

Code

Created by

🇮🇹Italy giuse69

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @giuse69
  • First commit to issue fork.
  • @viren18febs opened merge request.
  • Status changed to Needs review about 1 year ago
  • 🇮🇳India viren18febS

    Hi @Giuse69
    I have fixed the issue & added MR, please review,

  • 🇮🇹Italy giuse69

    Hi, with the fix the fatal error does not appear anymore but using this module on a custom entity type (created with ECK) still does not work:
    -) first time that the status module is enabled in the configuration / content authoring, after hitting save the select base route radio options disappear.
    -) saving again the select base route re-appear (first problem).
    -) clicking on the "manage base fields" does not open a page to add custom base fields but redirects to ECK administration page where you can just enable/disable the standard base field.
    thanks

    Giuse

  • Status changed to Needs work about 1 year ago
  • Status changed to Closed: outdated about 1 year ago
  • 🇨🇳China qiutuo

    Please update to version 2.0.1 to solve all the above problems.

Production build 0.71.5 2024