ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Post Upgrade Site Error

August 17, 2010 9:33pm

Subscribe [3]
  • #1 / Aug 17, 2010 9:33pm

    ioannisk

    6 posts

    This question may be related to a resolved thread.


    I’ve just completed the upgrade process up to EE 2.1. Everything seemed to go fine during the installation, but I now get the following error when I try to access our site.

    ———————-

    Error

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

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

    ———————-

    I can access the control panel fine, but our site is obviously down, and I need some quick help.

    I didn’t understand what to do. Can you please explain me clearly.
    Thanks.

  • #2 / Aug 18, 2010 8:03am

    Sue Crocker

    26054 posts

    Let’s have you manually disable extensions.

    See: http://expressionengine.com/wiki/HowTo_Disable_Extensions_Within_Config.php/

    This should help get the site up, but you’ll need to upgrade your field type to a 2.x version.

    Does that help?

  • #3 / Aug 18, 2010 12:12pm

    ioannisk

    6 posts

    I disabled the extensions.
    But how to upgrade my field type to a 2.x version?

  • #4 / Aug 18, 2010 1:59pm

    ioannisk

    6 posts

    I installed the NSM Morphine Theme and NSM TinyMCE in my site. But it doesn’t help me.

  • #5 / Aug 19, 2010 2:28am

    John Henry Donovan

    12339 posts

    ioannisk,

    What wysiwyg extensions did you have installed in your EE1.x site before upgrade?

    If you have installed NSM TinyMCE then you need to now choose that field type for your relevant custom fields .

    When you think you have them all try turning back on extensions

  • #6 / Aug 20, 2010 9:05pm

    kevinthompson

    3 posts

    I’m having the same problem. I’ve installed NSM TinyMCE to replace LG TinyMCE and changed my custom fields in the CP to use the new field type, which resolves the error in the control panel on the edit page, but the front-end still throws the same error.

    Not sure where to look next.

  • #7 / Aug 20, 2010 10:18pm

    kevinthompson

    3 posts

    Scratch that. I’m all set. I had leftover records in the DB from a multi-site install and multisite is not installed.

  • #8 / Aug 22, 2010 3:09pm

    Greg Salt

    3988 posts

    Hi Kevin,

    Okay. Glad that you are up and running.

    @ioannisk, where are you with this now?

    Cheers

    Greg

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases