Module error: UndeployedMetaDataImplementation->getFileName()

[rubix]

Hey guys,

After working on the relationships for a couple custom modules, I've started getting Smarty template errors on the GUI and the following error into my sugarcrm.log:

[17106][1][FATAL] UndeployedMetaDataImplementation->getFileName(): view type working is not recognized

I'm working on:
-Sugar 6.0 Community Edition
-Mac OS X 10.6
-PHP 5.2.13

The module with the Smarty errors is based on the "Issue" template.

Any help is muchly appreciated.

Thank you!

Reuben

[rubix]

Bump. Switched to my localhost but still encounter the problem.

Mon Aug 23 14:02:47 2010 [8611][1][FATAL] UndeployedMetaDataImplementation->getFileName(): view type working is not recognized

[kenlyle]

Me too, in 5.5.4, a couple of custom modules, at least one of which is of type Issue. Error messages don't appear to provide enough info to tell which is the problem.

Main symptom is that Studio screen is blank.

The two custom modules are Customers and Jobs, from the People and Issues module templates.

I did seem at one point a folder called working under custom. I tried renaming it and the Studio issue persisted, so I removed it, but the Studio issue remains.

I've also removed the Issues based module, no joy.

Hm, renaming the custom folder brings Studio back. But there's nothing specific or consistent in the sugarcrm.log. I'll have to re-trace to find the error of my ways. I'd appreciate any tips, though.

[josedc15]

I have the same problem.

I create a MemberShip Module by Module Builder.

Then i create the relationship Many to One with Contacts (also by Module Builder).
And my sugarcrm.log show this:
[3939][1][FATAL] UndeployedMetaDataImplementation->getFileName(): view type working is not recognized


Please if you find any solution let me know.

Thanks.

[eitrix]

a lot of errors you will get when you develop from modulebuilder and deploy, make relationships and then delete them, then make another etc.

To make this more easy, stop deploying from module builder but go to package and press publish so you download a zip that you install from module loader and then whenever you want new version installed first uninstall the old one.

[wonder_trout]

I have the same issue but deploying and reloading the module through the module loader does seem to solve it. It seems there must be some bug in the publish routine though the error message isn't enough to try and track it down.