Page MenuHomePhabricator

"Make Editable" for any (non-task) form causes exception: "Unable to resolve method 'newEditEngineSubtypeMap'."
Closed, ResolvedPublic

Description

Bug Description

When clicking on any "Make Editable" button (and confirm the action in the shown dialog), all I get is a dialog showing the message:
Unable to resolve method 'newEditEngineSubtypeMap'.

Components/Versions

How to reproduce

  • Create Project
  • Configure Form
  • Edit Form Configuration
  • Make Editable
  • Confirm "Make Editable"

Additional information

error.log
[03-Mar-2017 21:03:39 UTC] [2017-03-03 21:03:39] EXCEPTION: (Exception) Unable to resolve method 'newEditEngineSubtypeMap'. at [<phabricator>/src/infrastructure/storage/lisk/LiskDAO.php:1775]
[03-Mar-2017 21:03:39 UTC] arcanist(head=master, ref.master=3b6b523c2b23), phabricator(head=master, ref.master=d2a420d13abd), phutil(head=master, ref.master=81494451f9be)
[03-Mar-2017 21:03:39 UTC]   #0 <#2> LiskDAO::call(string, array) called at [<phabricator>/src/infrastructure/storage/lisk/LiskDAO.php:1725]
[03-Mar-2017 21:03:39 UTC]   #1 <#2> PhabricatorProject::newEditEngineSubtypeMap() called at [<phabricator>/src/applications/transactions/editengine/PhabricatorEditEngine.php:227]
[03-Mar-2017 21:03:39 UTC]   #2 <#2> PhabricatorEditEngine::newSubtypeMap() called at [<phabricator>/src/applications/transactions/editor/PhabricatorEditEngineConfigurationEditor.php:62]
[03-Mar-2017 21:03:39 UTC]   #3 <#2> PhabricatorEditEngineConfigurationEditor::validateTransaction(PhabricatorEditEngineConfiguration, string, array) called at [<phabricator>/src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php:849]
[03-Mar-2017 21:03:39 UTC]   #4 <#2> PhabricatorApplicationTransactionEditor::applyTransactions(PhabricatorEditEngineConfiguration, array) called at [<phabricator>/src/applications/transactions/controller/PhabricatorEditEngineConfigurationSaveController.php:38]
[03-Mar-2017 21:03:39 UTC]   #5 <#2> PhabricatorEditEngineConfigurationSaveController::handleRequest(AphrontRequest) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:269]
[03-Mar-2017 21:03:39 UTC]   #6 phlog(Exception) called at [<phabricator>/src/aphront/handler/PhabricatorDefaultRequestExceptionHandler.php:41]
[03-Mar-2017 21:03:39 UTC]   #7 PhabricatorDefaultRequestExceptionHandler::handleRequestException(AphrontRequest, Exception) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:678]
[03-Mar-2017 21:03:39 UTC]   #8 AphrontApplicationConfiguration::handleException(Exception) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:274]
[03-Mar-2017 21:03:39 UTC]   #9 AphrontApplicationConfiguration::processRequest(AphrontRequest, PhutilDeferredLog, AphrontPHPHTTPSink, MultimeterControl) called at [<phabricator>/src/aphront/configuration/AphrontApplicationConfiguration.php:181]
[03-Mar-2017 21:03:39 UTC]   #10 AphrontApplicationConfiguration::runHTTPRequest(AphrontPHPHTTPSink) called at [<phabricator>/webroot/index.php:17]

Event Timeline

I can't reproduce this. Did you recently update and forget to restart the webserver/PHP?

Although our deployment mechanisms should take care of this on their own, I specifically made sure everything is restarted etc. for reproducing this issue and producing the error logs.

Is it possible that symlinks could cause this issue?
libphutil and arcanist are symlinked from their current builds to the location where Phabricator expects to find them.

Whoops, no my mistake. I tested Task forms, not Projects.

I assume this is broken for any EditEngine not tasks

chad renamed this task from "Make Editable" for any form causes exception: "Unable to resolve method 'newEditEngineSubtypeMap'." to "Make Editable" for any (non-task) form causes exception: "Unable to resolve method 'newEditEngineSubtypeMap'.".Mar 3 2017, 9:36 PM
chad added a project: EditEngine.
chad added a subscriber: epriestley.

Is it possible that symlinks could cause this issue?
libphutil and arcanist are symlinked from their current builds to the location where Phabricator expects to find them.

And also just verified it is not caused by symlinks.

I was able to reproduce it, sorry for mis-reading.

This should be resolved at HEAD of master, thanks for the report!

Thanks a lot for this ultra-fast reaction & fix.