Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#2 3536484-1.patch421 bytesbingol@ciandt.com

Issue fork quick_node_clone-3536484

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:

About issue forks

Comments

bingol@ciandt.com created an issue. See original summary.

bingol@ciandt.com’s picture

bingol@ciandt.com commented
StatusFileSize
new 3536484-1.patch421 bytes
dhruv.mittal’s picture

dhruv.mittal commented

I can confirm that NodeForm namespace has changed and moving it to the right state with creating the MR of it and providing
reference link of the changes
https://www.drupal.org/node/3517871

dhruv.mittal opened merge request !61

dhruv.mittal’s picture

dhruv.mittal commented
Status: Active » Needs review
bluegeek9’s picture

bluegeek9 commented
Category: Bug report » Task
Status: Needs review » Needs work

What about supporting earlier versions of Drupal before the namespace changed?

bluegeek9 changed the visibility of the branch 8.x-1.x to hidden.

bluegeek9’s picture

bluegeek9 commented
Assigned: Unassigned » bluegeek9
Status: Needs work » Active

bluegeek9 opened merge request !63

bluegeek9 changed the visibility of the branch 3536484-nodeform-namespace-has to hidden.

  • bluegeek9 committed fdeb35fc on 8.x-1.x 
    Issue #3536484: NodeForm namespace has changed
bluegeek9’s picture

bluegeek9 commented
Assigned: bluegeek9 » Unassigned
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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

weseze’s picture

weseze commented

The comitted solution does not work when installing the module from command line or from initial site setup. (in our experiences)
The .module file is not necessarily loaded so the NodeForm class is unknown.

The suggested fix from the initial patch seems like the only good solution?