Upgrading from EE2 to EE3, ifelse addon trouble
How Do I?
Hello!
I am in the process of upgrading a site from version 2 to version 3, and I’ve run into some trouble with addons. This site has a lot of them, I am trying to uninstall and remove any addon that can’t be carried over to EE3 as they are discontinued. One of these is “ifelse”, the site seems to be using the syntax introduced through this addon heavily, and when I try to remove it that naturally causes a problem with the templates. I get an error that goes like this:
“The following tag has a syntax error:
{exp:ifelse}
Please correct the syntax in your template.”
My question is this: How do I handle this addon during the upgrade process? As the EE2 to 3 document goes, having out-of-date addons in the system while upgrading can cause trouble. So I can’t keep it in, and right now I’m having trouble getting it out. Does anyone have a good solution to this problem?
I am also trying to remove other addons, freebie being one of them, and I get a very generic error message in the CP when I hit “remove” that goes:
“An error occured while trying to remove plugin: Freebie” - with no further explanation or suggestions. What can I do here? If I try to simply rename the folder or delete it, the entire CP crashes as it is unable to locate the addon.
Any help here would be much appreciated.
Thank you!
If your templates have dependencies on existing addons/plugins, and you can’t upgrade them, then you have to modify your templates to no longer reference them. By no means an easy task, of course, depending on the functionality they provide.
But you have, it seems, intermixed 2 problems in your statement above:
One - that IfElse is not available for EE3 and your have dependencies. Though you may be able to replace it’s use with native conditionals in your templates.
Two - that your wish to remove an addon but get an error. But you don’t specify why. Freebie is available for 3, so do you just not wish to use it at all? You can likely just use native template routes to achieve the functionality anyway.