modules broken after upgrade

[garciasanchezdaniel]

Hello friends, I need your help again...

I just upgraded sugarcrm from 4.2.1 to 6.1.7 and now, I have lost a lot of the tabs of my modules, but the modules remain there, because if I introduce in the browser module=mymodule&action=index, sugarcrm goes to my module, but I find some errors:

1. In listview: Fatal error: Call to undefined function get_form_footer() in modules/mymodule/ListView.php on line 140 -> I HAVE SOLVED THIS BY COMMENTING THIS LINE
   
2. After save a record (in detailview): Fatal error: Call to a member function get_summary_text() on a non-object in C:\xampplite\htdocs\sugarsuite421\include\MVC\View \SugarView.php on line 1088

In addition, my modules aren't installed on studio, but all files of these modules remain on /modules directory

Can you help me please?
I need my sugarcrm updated as soon as be possible
Thanks very much, Daniel

[andopes]

In my experience, big upgrades like that (from 4.2 to 6.x) are pretty unstable, so I recomend to:

• recustomize everything;
• dismiss the upgraded system and install an instance from new version;
• configure the upgraded database in the config.php of new instance.

Cheers

[garciasanchezdaniel]

Thanks for your reply

As you say, I updated my old instance in order to get my database updated. By the way, I tested my new instance, and you are right, I tested myself that this new version was very unstable.

Then, I installed a new instance of sugarcrm version 6.1.7, connected with new database, and customized almost everything -this is a work tired, but in this way I will have my sugar updated safely - I still have to clone two modules: documents and bugs. Because in my business's sugarcrm 4.2.1d we had four modules for this: public documents, private documents, internal bugs, external bugs.

What is the safest way to clone one sugar's module?

Excellent forum! Daniel

[andopes]

Thanks for your reply

As you say, I updated my old instance in order to get my database updated. By the way, I tested my new instance, and you are right, I tested myself that this new version was very unstable.

Then, I installed a new instance of sugarcrm version 6.1.7, connected with new database, and customized almost everything -this is a work tired, but in this way I will have my sugar updated safely - I still have to clone two modules: documents and bugs. Because in my business's sugarcrm 4.2.1d we had four modules for this: public documents, private documents, internal bugs, external bugs.

What is the safest way to clone one sugar's module?

Excellent forum! Daniel

The best way is to reimplement the modules through Module Builder.
it should be easier than redo the modules by hand.

Cheers

[garciasanchezdaniel]

Hello andopes

Sorry for my ignorance, but I don't understand you well...could you explain me how should I do this? For example, for the module called documents, what would be the steps?

Thanks in advance, Daniel