Module build problem

[shanff]

I've build modules in the past with version 5.1, but we recently took our installation up to version 5.2.0f. The server is a CentOS 5 server, PHP 5.2.5, MySQL 5.0.45.

Everything on the front end seems to be working fine. When I build a module, however, I'm seeing some problems.

First, drop down lists aren't being created on the fly when creating new fields. I have to create them and then create a new field and link from the already created dropdown. That's not a huge problem, just a minor inconvenience for me.

Second. When I deploy the module, no Tab is visible for the new module. A "blank" tab is created and when I click on it, it brings up my module as expected, but I'm unable to get it to display the title which is correctly listed in /modules/mymodule/language/en.....php.

This is an installation that has been working great since we first installed at 4.5.x and has seen some battle scars, but has always worked for us. I've done repairs and checked permissions. The only clue I can see is something in the sugarcrm.log pertaining to UndeployedMetaDataImplementation but Google searches and forum searches have yielded nothing on this.

Thanks for any help.

[shanff]

Just verified the same behavior on a fresh install of 5.2.0f also. I'm stuck as I can't revert to a previous version at this point.

[shanff]

OK, finally solved my problem. I don't know why my fresh install was exhibiting the same behavior, with a fresh file system and database, but I installed a new copy on my laptop separate of the server it was installed on at the office and it worked. I then exported my customizations from the copy in the office an imported into my local copy. This was less than 100% successful, but after some directory copying, permissions changing and Studio work, I have a "Fresh" copy of 5.2.0f with my customizations and the capability to create modules is restored. I'm not sure exactly what happened to my past copy, but somewhere along the line it must have boinked an upgrade that the upgrade process didn't catch. I don't believe I edited anything outside of the custom directory by hand so I believe everything should have been upgrade safe. Anywho, problem solved, but I still have no idea where the process was breaking.