Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Page publishing not working in Page Editor after upgrading to Service Pack 18 (6.5.18.0)

Avatar

Level 2

This is a question if I have found a good solution to the issue and maybe someone will find it also helpful.

Error Message when using AEM Publish Workflows:
404 RESOURCE AT '/CONTENT/DE/STARTSEITE/TEST/DEVTEST/COMPONENTS/PAGE//LIBS/WCM/CORE/CONTENT/SITES/PUBLISHPAGEWIZARD.HTML' NOT FOUND

 

Spoiler

experience-manager-65/release-notes 

Known issues

  • Page publishing not working in Page Editor after upgrading to Service Pack 18 (6.5.18.0)

    After you upgrade an instance of AEM 6.5.0.0—6.5.17.0 to AEM 6.5.19.0, when you click **Publish Page** inside the Page Editor, you are redirected to a URL that does not exist.

    To work around this issue, do one of the following:

 

 

 

 

Code with AEM 6.5.18 SP
/libs/cq/gui/components/authoring/editors/clientlibs/core/js/actions/publish.js

    function navigateToPublishWizard(activator, path, editMode, schedule) {
        var params = "";
        if (path && typeof path === 'string' && path.length > 0) {
            params += "item=" + path;
        }

        if (params.length > 0) {
            location.href = encodeURIComponent(activator.data('url')) + "?" + params + (editMode ? ("&editmode") : "") + (schedule ? ("&later") : "");
        }
    }

 

 

 

 

 

 

 

// Replace OLD
            location.href = encodeURIComponent(activator.data('url')) + "?" + params + (editMode ? ("&editmode") : "") + (schedule ? ("&later") : "");

// Working NEW
            location.href = activator.data('url') + "?" + params + (editMode ? ("&editmode") : "") + (schedule ? ("&later") : "");

 

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @Anselm_H_,

If I good understand, you want to apply some changes under /libs. If so, then this is not a proper approach, and it's against Adobe best practices.

To get rid of this issue you have few options:

If you want to go with your solution, you should use overlay mechanism. Which means you should create following structure

/apps/cq/gui/components/authoring/editors/clientlibs/core/js/actions/publish.js

that will reflect structure from /libs, and apply your changes under /apps.

Regarding implementation itself, if it works for you, then it should be acceptable change.

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Hi @Anselm_H_,

If I good understand, you want to apply some changes under /libs. If so, then this is not a proper approach, and it's against Adobe best practices.

To get rid of this issue you have few options:

If you want to go with your solution, you should use overlay mechanism. Which means you should create following structure

/apps/cq/gui/components/authoring/editors/clientlibs/core/js/actions/publish.js

that will reflect structure from /libs, and apply your changes under /apps.

Regarding implementation itself, if it works for you, then it should be acceptable change.

Avatar

Level 4

For anyone in the future running into this issue as well, what I've found from here and elsewhere is:

1. We're currently on 6.5 SP18. According to the patch notes, 6.5 SP19 fixes this (see "Fixed Issues" -> "Page Editor")

 

Just going to paste the change log here as well to future-proof, since Adobe loves to kill entire sections of their site and leave dead links:

  • After upgrading an instance from AEM 6.5.17 and AEM 6.5.18, from inside the Page Editor, if you selected Publish Page, you are redirected to a URL that does not exist. The user should be redirected to the Publish wizard. (SITES-15856)

 

2. As an additional temporary workaround, authors are able to publish from the site admin, rather than within the page editor.

 

Otherwise, the accepted answer is a fine solution if you must stay on SP18 for some time instead.