Client Lib Debug Mode Fixes a Javascript Problem | Community
Skip to main content
Level 3
June 13, 2017
Solved

Client Lib Debug Mode Fixes a Javascript Problem

  • June 13, 2017
  • 10 replies
  • 2100 views

Hi,

I'm currently having a problem if I view a page as published.

I get a javascript error saying "Uncaught ReferenceError: KmlMapParser is not defined" but if I add "?debugClientLibs=true" to the end of the URL my problem is fixed.

Can anyone explain what is happening here?

Thanks,

Karl

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by karlw37000147

I have sorted this now.

It was a scoping issue that was caused by the different ways the different modes compile the JS.

Thanks,

Karl

10 replies

Feike_Visser1
Adobe Employee
Adobe Employee
June 13, 2017

To me the option writes out separate lines in the JS. Can you check that?

Level 3
June 13, 2017

Do you mean that the Javascript isn't compressed?

Thanks,

Karl

Level 3
June 14, 2017

How long do we usually have to wait for an answer?

Thanks,

Karl

Feike_Visser1
Adobe Employee
Adobe Employee
June 14, 2017

Missed your previous answer, my bad :-)

The option "debugClientLibs=true" is not compressing, but it writes out files one by one in the HTML source.

And around the wait-time: this is a community forum with SLA :-)

Level 3
June 14, 2017

I thought that about the community but I wasn't sure how active it was that's all.

I don't have my local site to compress the JS even without the Debug mode activated.

Everything seems to look like it's in the correct order.

I'll keep checking but it just seems weird how it works in Debug mode.

Thanks,

Karl

Feike_Visser1
Adobe Employee
Adobe Employee
June 14, 2017

Compressing is done via the minify option via the OSGi-configuation

Feike_Visser1
Adobe Employee
Adobe Employee
June 14, 2017
Level 3
June 14, 2017

Thank you but my code isn't compressing right now and I don't think it should be doing on my local version.

Thanks,

Karl

smacdonald2008
Level 10
June 14, 2017

Community can respond right away or may take a bit of time - that is the nature of community.

karlw37000147AuthorAccepted solution
Level 3
June 14, 2017

I have sorted this now.

It was a scoping issue that was caused by the different ways the different modes compile the JS.

Thanks,

Karl