Missing Page Builder scripts

Jim Piller asked on June 26, 2020 16:39

Hello,

I am creating a new site and trying to implement the page builder functionality which I have done several times now, but I'm hitting a roadblock. I've setup my page type, added all the necessary references in the code and the Layout page, but when I go to the page builder page in the CMS, it can't find the the pageBuilder.js and related files, like the CSS files. I've checked the site folder and all the scripts and style sheet files are where they're supposed to be.

Further, I've compared all my code to another site that I have running locally where page builder is working just fine, and I can't see a difference.

My question is, where are the page builder javascript and style sheet files supposed to be in relation to the MVC site? Should they be in just the MVC site folder or the CMS folder as well?

Any help on this would be greatly appreciated.

Correct Answer

Jim Piller answered on July 17, 2020 21:15

So after a lot of trial and error, I finally think I figured out what was going on to break the Page Builder feature in my project. When I setup the site in IIS, typically the first thing I do is to remove the default applications and set the root of the IIS website to the folder where the MVC application is. Then I add the CMS application usually naming it "kentico". In previous builds of Kentico, most recently 12.0.47, this worked w/o issue. I updated this project to 12.0.75 and that's when the page builder wouldn't load. I tried several different things including making sure all the appropriate settings were in place and so on. Finally, I tried renaming the CMS application to "cms" and then the page builder started working w/o an issue. I changed it back to "kentico" and the page builder broke again.

I believe something in one of the more recent updates is causing the issue if the CMS application is called "kentico" as in older versions this works w/o issue.

1 votesVote for this answer Unmark Correct answer

Recent Answers

Brenden Kehren answered on June 26, 2020 23:51

Reload all your nuget packages and see if this resolved your issue.

0 votesVote for this answer Mark as a Correct answer

Jim Piller answered on June 28, 2020 17:08

Hey Brenden,

Thanks for the reply. Unfortunately, that didn't work. Here are some of the console errors I'm seeing in Chrome:

GET http://kenticolaunchpad.staging/Kentico/Scripts/builders/page-builder.css net::ERR_ABORTED 404 (Not Found) 4example?instance=20bb0e36-9d99-4a50-9e13-82083f9610f2&uh=6de3325ff081e5bf7009ed64ba1db8efa740e02fadde0dca998553e5723651f0&editmode=1&administrationUrl=http%3A%2F%2Fkenticolaunchpad.staging%2Fkentico:178

GET http://kenticolaunchpad.staging/Kentico/Scripts/shim.min.js net::ERR_ABORTED 404 (Not Found) 9example?instance=20bb0e36-9d99-4a50-9e13-82083f9610f2&uh=6de3325ff081e5bf7009ed64ba1db8efa740e02fadde0dca998553e5723651f0&editmode=1&administrationUrl=http%3A%2F%2Fkenticolaunchpad.staging%2Fkentico:172

There are others, but I think you get the idea. I've never seen this before and I know I have all the pieces, scripts and CSS files in the correct places, so I'm really stuck.

0 votesVote for this answer Mark as a Correct answer

Jim Piller answered on June 29, 2020 15:53

Brenden,

I have a question about the CMSApplicationGuid app setting - should this value be the same between the CMS application vs. the MVC application? Also, there is a SiteGUID value in the CMS_Site table, and I'm wondering if that should be the same as the CMSApplicationGuid? I'm wondering if these ID's have gotten out of sync somehow, if that's what's causing the page builder to not work correctly?

Thanks,

Jim Piller

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on July 17, 2020 21:26

Jim,

This could very well be caused by cached IIS files from the JIT compiler. You'll find those in the following directory (assuming you're using 64bit)

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files

If you delete those files in those directories, it will clear up any cached JIT compiled files and force IIS to rebuild the site when it loads again. I've had many issues with being able to debug on my local instance and removing these temp files helped greatly.

Regarding your other question about the ApplicationGUID, the Kentico application and MVC application don't care about this at all. According to documentation, it's a, "Unique identifier of the Kentico instance. Used by Kentico Windows services to identify the Kentico instance."

0 votesVote for this answer Mark as a Correct answer

Jim Piller answered on July 17, 2020 21:40

Brenden,

I did try your suggestion and then tried renaming the CMS application in IIS back to "kentico" but I got the same page builder scripts 404 errors, so I don't think the cached files were an issue. When I changed the application name back to "cms" the page builder started working again. I do think there is an issue w/ the keyword "kentico" being used as the CMS application name.

0 votesVote for this answer Mark as a Correct answer