AEM 6.4.3 | Not able to edit any component | Community
Skip to main content
salman18j
salman18j
Level 2
Dec 27, 2018 10:01 AM UTC
Solved

AEM 6.4.3 | Not able to edit any component

Hi,

I am not able to open any edit dialog after installing AEM 6.4.3 service. Is anyone else facing the same issue?

Errors are :

Uncaught TypeError: Cannot read property 'replace' of undefined

    at HTMLDocument.<anonymous> (page.8a9ad83c4b88a00fcbe6bfe0088d80c2.js:7541)

    at HTMLDocument.dispatch (jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:5226)

    at HTMLDocument.elemData.handle (jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:4878)

    at Object.trigger (jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:5130)

    at HTMLDocument.<anonymous> (jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:5860)

    at Function.each (jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:370)

    at jQuery.fn.init.each (jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:137)

    at jQuery.fn.init.trigger (jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:5859)

    at core.d948d0239b13041ea18568bf195d9097.js:21715

    at jquery.5e8d3382f82b03b0bf3fea3024eecd61.js:3411

core.d948d0239b13041ea18568bf195d9097.js:1123 Parsing incoming message failed setImmediate$0.5162372643488027$3

receiveMessage @ core.d948d0239b13041ea18568bf195d9097.js:1123

Regards,

Salman

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Bharath_valse
    Bharath_valseAccepted solution
    Level 4
    Jan 2, 2019 6:46 PM UTC

    Workaround: How to fix the issue

       

        Go to Package Manager

        Reinstall package "cq-ui-wcm-admin-content-1.0.1004.zip"

        Recompile all JSPs (http://<AEM HOST>:<AEM PORT/system/console/slingjsp)

        OR

        Restart the instance

       

       This workaround will documented in the release notes shortly

    View reply

    15 replies

    indranilp975525
    New Participant
    Feb 1, 2019 5:04 PM UTC

    Thanks Bharath. This workaround worked!

    Translate
      Reto_Zigerlig
      Level 2
      Jan 11, 2019 7:44 AM UTC

      The mentioned workaround is now officially documented under https://helpx.adobe.com/experience-manager/6-4/release-notes/sp-release-notes.html#KnownIssues​.

      Translate
        mtremblay33
        Level 2
        Jan 3, 2019 5:58 PM UTC

        We're having the exact same issue. Thanks salman18j for reporting this.

        It is indeed pretty shocking that a bug like this made its way into SP3. Makes me question what else may be broken...

        In any event, the workaround from Bharath valse is valid.

        Translate
          Bharath_valse
          Bharath_valseAccepted solution
          Level 4
          Jan 2, 2019 6:46 PM UTC

          Workaround: How to fix the issue

             

              Go to Package Manager

              Reinstall package "cq-ui-wcm-admin-content-1.0.1004.zip"

              Recompile all JSPs (http://<AEM HOST>:<AEM PORT/system/console/slingjsp)

              OR

              Restart the instance

             

             This workaround will documented in the release notes shortly

          Translate
            smacdonald2008
            smacdonald2008
            Level 10
            Dec 31, 2018 5:56 PM UTC

            We closed this thread as there is nothing more the community can do at this point.

            Translate
            atyaf66
            atyaf66
            Level 2
            Dec 31, 2018 5:52 PM UTC

            I already did, thanks for your reply

            Translate
              VeenaVikraman
              VeenaVikraman
              New Participant
              Dec 30, 2018 6:49 AM UTC

              Please raise a ticket with Adobe as scott mentioned

              Translate
                smacdonald2008
                smacdonald2008
                Level 10
                Dec 28, 2018 8:08 PM UTC

                Please report this to customer Care team so they can report to the Eng team and fix it. Obviously if there is a bug somewhere. Thank you!

                Please note - Adobe is in Winter Shutdown until Jan 2.

                Translate
                atyaf66
                atyaf66
                Level 2
                Dec 28, 2018 3:48 PM UTC

                smacdonald2008​ this is probably one of the worst upgrades I have had to deal with with regards to SP's...

                I am seeing the same issue reported here, and it is only happening if you install SP2 (6.4.2.0) and THEN install SP3 (6.4.3.0)
                If you install SP3 on a base AEM instance (6.4.0.0) then editing dialogs works fine.

                The error is very clear, the file `/libs/cq/gui/components/siteadmin/admin/properties/FilteringResourceWrapper.jsp` is not in the repository. If I copy the file from a clean AEM 6.3 SP2 instance into my SP3 instance, I can edit dialogs in my SP3 instance.

                This suggests to me that proper testing of the scenario described above was not tested before SP3 release (install SP2 -> install SP3). Might be an honest mistake, but I'd love to know if there is a path forward?

                Somewhat related frustration notes

                We upgraded to SP2 and found a major bug which I reported in a daycare ticket and also here: Parsys Limit code prevents adding components in AEM 6.4.2.0 (SP2) · Issue #1545 · Adobe-Consulting-Services/acs-aem-comm…


                Then we upgrade to SP3 yesterday, and this issue happens.. maybe you can understand my frustration

                Hopefully adobe has a path forward for us.

                Ahmed

                Translate
                  manjeets5367412
                  New Participant
                  Dec 28, 2018 2:15 PM UTC

                  the console is clear and there is no error. But found that FilteringResourceWrapper.jsp is missing.

                  Translate
                    Show more replies
                    Terms & ConditionsAccessibility statement

                    Loading footer...