In the docs, it informs that if you have the forum add-on enabled, then legacy profiles are enabled in the config.
Can they eventually be disabled or this will break the forum module functionality completely? Assuming you don’t allow for profile changes in the forum or direct the links to your own custom profile templates.
I want to keep the forum module enabled, but I prefer not to maintain 2 pages for each feature, like login, sign up, etc., if I have them migrated to my own templates it seems I still have to redirect the legacy old pages or disable them manually.
My question is basically if I can turn the legacy profiles off in EE but still use the forum module. I don’t require people to log or change profile things from the forum side, as I have those fields on my own templates.
I understand those pages in the forum would not work anymore, but I would redirect them to my own URL when someone clicks on them. Or will the forum give errors if it cannot find that setting as on?
Untested, but I wouldn’t expect it to give errors as long as you removed any member based forms. So like the login form is in one of the headers. I wouldn’t be surprised if there was a problem there if the legacy templates were turned off. But if there isn’t a member theme related tag on a template, I wouldn’t expect a problem. And something like username/screen name wouldn’t be an issue. But the member list or login forms and such, there I would expect things to not parse and/or give warnings.
Again, not tested, but that would be my bet.
That is also what I was thinking as well, the errors should not be critical but just some missing deprecated tags and I expect just to edit them out. From what I see, only the Forum and Wiki module still use the legacy profile templates, but I don’t think those file templates are that critical if you already have the same functionality on regular templates for member or user actions and can just redirect them to the proper url.
Using regular templates is much better than the legacy profile since you can use regular EE variables on them as well, which makes them better integrated into a website and more consolidated with developing. I never edited the old legacy templates that much, but being able to discard them would be great as I move the functionality to regular templates.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.