Worklog for task "Re-implement forms and current public integrations from scratch"

Legacy Defect: Social Authorization in Feedback Form Does Not Work

The feedback form interface offers users four social authorization options:

• Google+ (/auth/gplus)
• Vkontakte (/auth/vkontakte)
• Twitter (/auth/twitter)
• Facebook (/auth/facebook)

In fact, none of these scenarios currently work.

Why It Matters

This is another clear example of legacy functionality degradation: the interface continues to promise users features that technically no longer exist or are unsupported. To a visitor, this looks like a broken website, and for maintenance teams, it creates a false scope of functionality that has to be investigated separately.

It is especially noteworthy that Google+ is present — a service that was shut down for consumer use long ago. The very fact that such an item remains in the current interface shows how easily external integrations turn into technical debt if they are not reviewed regularly.

Conclusion for the New Version

Social authorization should not be migrated just because it was present in the old interface. For haih-cms, it is necessary to redefine whether authorization is needed by the user at all, and if so — to implement only relevant and truly supported scenarios.

It is better to have a simple, working feedback path than a set of visually attractive but non-working login methods.

Practical Impact on Migration

Legacy OAuth routes should be treated as historical functionality rather than a mandatory requirement for the new implementation. Their presence must be accounted for during the inventory process, but they should not be reproduced without confirmed user value.