Revolution: [3.x] Add support for legacy components

[CrazyBoy49z]

Feature request

Summary

I plan to add support for legacy components to the MODX kernel as class_alias deprecated https://github.com/modxcms/revolution/blob/3.x/core/include/deprecated.php

Do you offer this PR, is it not worth the time to spend it?

[JoshuaLuckers]

Do you have a list of the legacy components that (might) not work in 3.x?

[CrazyBoy49z]

https://docs.google.com/spreadsheets/d/1HyKwqz1qdCW6C46eH8PcWZLZNllI2HB8yAwkhkVPbX8/edit#gid=0

[Jako]

What do you mean with 'Partly support'? What is the difference to 'Support'?

[Mark-H]

I think we want to avoid adding every single change - but adding classes that people have been told to extend over the years (like resource processors, required for custom resources) or certain services (modMail, modParser, etc) would probably be quite useful.

[DetaliDigital]

@Jako

[CrazyBoy49z]

I think we want to avoid adding every single change - but adding classes that people have been told to extend over the years (like resource processors, required for custom resources) or certain services (modMail, modParser, etc) would probably be quite useful.

This is what I want, just using these classes will be easy to create simple sites at the beginning in MODX that will speed up testing ...

[JoshuaLuckers]

Can you share a list of the classes you would like to add?

[CrazyBoy49z]

@JoshuaLuckers

modMail,
modDashboardWidgetInterFace,
modTemplateVarInputRender,
modSystemEvent,
modManagerController

[CrazyBoy49z]

You will then be able to build sites and actively test the kernel

[JoshuaLuckers]

I propose to add modPHPMailer as well.

[Ibochkarev]

Added #14964

Thanks for taking time to report this issue and help make MODX better.
Please reopen if you still encounter this issue.

@modxbot close