Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

AEM as Cloud Service Sites da.live Author navigation caching issue

Open
#1,353 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start at the da.live landing page and follow the Apps → Translate navigation using the reproduction steps. Compare the expected return to the base dashboard with the redirect to /apps/loc#/translate/abc-ab, and verify that navigating back no longer shows an Empty or restricted state.

Written by the indexing model from the issue text.

Description

We are experiencing a persistent navigation issue within the da.live Author interface. The system appears to be incorrectly caching or redirecting our session state when moving between apps.

Expected Behavior:
Navigating back to the home page or the application root should consistently return the user to the base dashboard without carrying over state-specific pathing that results in empty/restricted states.

Impact:
This requires constant manual URL correction and prevents efficient navigation between different project environments (e.g., blog, blog-stage, blog-dev).


Is this issue reproducible?: Yes
Steps to reproduce: Navigate to https://da.live/ (The base landing page).

Select the "Apps" section and navigate to the "Translate" tool.

Access a specific project (e.g., "abc-ab").

Attempt to return to the home page or navigate back through the UI.

The application redirects to an incorrect or restricted URL path: https://da.live/apps/loc#/translate/abc-ab.

Result: The page displays as "Empty" or indicates a lack of permission, preventing further navigation or site management.

Dominant language
JavaScript
Stars
36
Forks
74
Avg merge
3d 17h
Merged PRs (30d)
42

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adobe/da-live

All issues in adobe/da-live

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.