Thread

Hi

We just recently upgraded our site to EE 2.0 with the kind help of EE support staff, but now we are faced with a new error while viewing the site.

Error

Unable to load requested field type file:  ft.multiselect.php.

Confirm the fieldtype file is located in the expressionengine/third_party/ directory

After doing a search on these forums for similar issues, it seems to me that it has to do with third party add-ons. Many of our third party add-ons are not compatible with EE 2.0 though.

This error most likely comes from the extension: Multi Drop-down List (v.1.1.1) by Mark Huot

This is not compatible with EE 2.0 I understand, which is fine, we don’t need to use it anymore anyway. But I don’t know what to do remedy the situation. I understand that all add-ons were turned off with the EE 2 upgrade. How do I get rid of it completely so I don’t generate that error. Every post in the forums recommends getting an upgrade from the developer but if that is impossible, how do we get our EE 2 site to work without it?

I would like to keep the data but we have far to many entries to check through each individually to find out where it resides.

What would be the best course of action for me in this case?

Hi aquaadmin, you’d need to convert over the field type to something else before you attempt to upgrade. I’d probably make it a text field.

Does that help?

Hi Sue.

I found all the fields that used that extension, as well as those that used another outdated extension - md_notes. I converted all those fields over to a text area field.

I thought that would solve the problem but it did not. We still get this error on the home page.

Error

Unable to load requested field type file:  ft.md_notes.php.

Confirm the fieldtype file is located in the expressionengine/third_party/ directory

We have already upgraded to EE 2.0 and I can access the control panel just fine. It’s just the site is not working.

Hi, aquaadmin - did you uninstall the fieldtype prior to updating? If not, it still has a line in exp_extensions trying to call that add-on; and you’ll need to manually remove it.

Do you need help with figuring that out?

Hi Lisa,

Removing the line in exp_extensions must have been what the tech from EngineHosting did for us. He went into the database and fixed whatever the problem was that caused the error to generate. I don’t quite know what he did, but in the interim between this post and the email I sent to him, the problem was resolved. Thanks for clueing me into what the fix might have been. Hope it will help someone else out too.

Hi, aquaadmin - glad you got this one fixed and working.  If anything else comes up, please do let us know so we can help out.