Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving a site instead of hitting Save/Activate deactivates the site entirely #28362

Closed
swicken-dotcms opened this issue Apr 25, 2024 · 3 comments · Fixed by #30358
Closed

Saving a site instead of hitting Save/Activate deactivates the site entirely #28362

swicken-dotcms opened this issue Apr 25, 2024 · 3 comments · Fixed by #30358

Comments

@swicken-dotcms
Copy link
Contributor

swicken-dotcms commented Apr 25, 2024

Parent Issue

No response

Problem Statement

When you save a currently active Site without hitting Save/Activate, it deactivates the site. This is not clear to the user at all, and the history tab still shows a published version.

Steps to Reproduce

  1. Save a site
  2. Try to access the site

Acceptance Criteria

Either
1. The Save action should make it clear that the currently published site will be deactivated
2. The history should not show a published version
Or

The published version should continue to be served and the site must be shown as active.

dotCMS Version

Master, 23.10, 23.01

Proposed Objective

User Experience

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

https://dotcms.zendesk.com/agent/tickets/116052
https://dotcms.slack.com/archives/C04UKBYG7SA/p1727116641308499

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

@erickgonzalez erickgonzalez moved this from New to Next 1-3 Sprints in dotCMS - Product Planning Apr 25, 2024
@erickgonzalez erickgonzalez moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning May 6, 2024
@erickgonzalez erickgonzalez moved this from Current Sprint Backlog to Next 1-3 Sprints in dotCMS - Product Planning May 17, 2024
@erickgonzalez erickgonzalez moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning May 17, 2024
@erickgonzalez erickgonzalez moved this from Current Sprint Backlog to Next 1-3 Sprints in dotCMS - Product Planning May 17, 2024
@erickgonzalez erickgonzalez moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning May 30, 2024
@erickgonzalez erickgonzalez moved this from Current Sprint Backlog to Next 1-3 Sprints in dotCMS - Product Planning Jun 17, 2024
@dsolistorres dsolistorres self-assigned this Sep 19, 2024
@dsolistorres dsolistorres moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Sep 19, 2024
Copy link

github-merge-queue bot pushed a commit that referenced this issue Nov 12, 2024
…sions (#30358)

#Closes #28362

### Proposed Changes
* For the sites portlet, if a site has live and working versions, the
live version is shown.
* When resolving a site by name, id or alias, the live version of the
site is retrieved for front-end users.

### Checklist
- [x] Tests

---------

Co-authored-by: Kevin Davila <[email protected]>
Co-authored-by: Jalinson Diaz <[email protected]>
Co-authored-by: Jonathan <[email protected]>
Co-authored-by: Will Ezell <[email protected]>
Co-authored-by: erickgonzalez <[email protected]>
Co-authored-by: Humberto Morera <[email protected]>
Co-authored-by: Jonathan Gamba <[email protected]>
Co-authored-by: Nicolas Molina Monroy <[email protected]>
Co-authored-by: Rafael Velazco <[email protected]>
Co-authored-by: freddyDOTCMS <[email protected]>
Co-authored-by: Fabrizzio Araya <[email protected]>
Co-authored-by: Daniel Enrique Colina Rodríguez <[email protected]>
Co-authored-by: Jose Castro <[email protected]>
@github-project-automation github-project-automation bot moved this from In Review to Internal QA in dotCMS - Product Planning Nov 12, 2024
@erickgonzalez
Copy link
Contributor

Working as it should now, when having different live and working versions of a site, the site still renders successfully.

Screenshot 2024-11-13 at 2 47 46 PM

@erickgonzalez erickgonzalez moved this from Internal QA to QA - Backlog in dotCMS - Product Planning Nov 13, 2024
@bryanboza
Copy link
Member

Fixed, unable to reproduce after this fix.

@erickgonzalez erickgonzalez added the LTS: Needs Backport Ticket that will be added to LTS label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants