Skip to content

unexpected getsummary calls #105

Description

@wsxiaolin

Pages were directly reading route.params.category (which can be aliased or missing), causing inconsistent behavior when the router allows multiple category aliases.
The goal is to normalize category input to a stable set (Experiment/Discussion/User) so API calls, comment posting, editor deep links, tags and logging all use the canonical category.
pls avoid reading route,using interface getRouteCategory instead(already exit)
also sometimes plweb trigger too many /Contents/GetSummary

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions