I am integratign AEM 6 with Adobe Target and have some problems with it.
Particularly, when I add "Adobe Target Mbox" component on the page - T&T request is sends but in console there is an error :
Uncaught TypeError: undefined is not a function.
I found that it throws when mboxOfferDefault.prototype.show(content) function is called from /etc/clientlibs/foundation/testandtarget/util/source/init.js.
The problem is that this function calls this.hide(content) which doesn't exists in mboxOfferDefault.prototype and that's why I suppose this error is thrown.
Can anyone tell me why this function in init.js is overriding default mboxOfferDefault.prototype.show(content) defined in mbox.js and what will be the risks if i'll remove this function from /etc/clientlibs/foundation/testandtarget/util/source/init.js ?
I will be appreciated if some one will help me with this problem.
Thanks!
Related
In Automation Studio a new function block is created. The compiler gives an error of "Undefined reference to myNewFunctionBlock." This error message gives no information on how to solve the issue.
How do eliminate this error?
Add the function block to the Software\Library page.
Instructions
Open the Configuration View
Open Cpu.sw. This will open the Software page.
Expand 'Library Objects'
Open the Logical View
Drag your function block to 'Library Objects'
Site works fine. Suddenly it will through an error. When clicking "flush system cahce" the error will go away for a some time. Anything from minuttes to severaæ hours.
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1247602160:
Unknown column 'tx_my_domain_model_formular.rel_formular' in 'where
clause' |
TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException
thrown in file
/webserver/typo3/src/6.2.15/typo3/sysext/extbase/Classes/Persistence/Generic/Storage/Typo3DbBackend.php
in line 862.
It is correct that the columns does not exist. But how to preceed in finding the error after this? Where is the sql generated that causes the site to crash?
UPDATE
A check "myParentObj->getChildObj instanceof myChildObjClass" used to work just fine. After changing myParent model to lazy load the ChildObj, then the class of childObj changed from childObjClass to a lazyLoadClass... I am not sure but I guess that is in turns somewhere somehow caused the core error seen in the log.
How to investigate further I simply cannot work out. Eg. store all DB calls in a file og DB to analyze after the error occours.
First
Please take time to write a good question. For a good question you'll get a good answer. It doesn't have to be perfect (not everyone is a native english speaker) but please reread your question.
Answer
If all fields are defined correctly, just run a DB compare from within the installtool.
If not, you need to define the DB-fields in your extension correctly.
Is this your own extension? When doing the query that triggers the error you could call execute(true) to generate the actual SQL statement and debug from there.
In Selenium I recorded a test suite and while executing I received the script error:
Element id=ui-id-12 not found
You are getting this error because you have recorded wrong script. The element ID 12 is changing every time. So you can use another way to detect the Web-Element.You will have to use more preferred way of locating the Web-element. Instead of using id please try to use static attribute of the Web-Element. I believe it will fix your problem.
After setting up , I get an error
Uncaught TypeError: undefined is not a function
on the line of 1273 which is the following
this._on(this.options.dropZone, {
I can't find where the function is defined in the javascript file (https://github.com/blueimp/jQuery-File-Upload/blob/master/js/jquery.fileupload.js). Do I have to use it with other Javascript files in the package?
it looks You haven't connected widget part of jquery.
http://jqueryui.com/download/#!themeParams=none
I had the same problem, so I added it and now file upload works.
I have a small web application written using Java programming language . whenever I am trying to access a jsp page I am getting the following error..................
HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: /jsp/newInvoice_acct_not_in_db.jsp(101,3) The s:hidden tag declares that it accepts dynamic attributes but does not implement the required interface
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:148)
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:777)
org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1512)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2393)
org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2399)
org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2343)
org.apache.jasper.compiler.Validator.validate(Validator.java:1739)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:166)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:315)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:282)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:586)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
Someone please help me find the solution for it..........
Your jSP has an compilation issue...Check whether your JSP fine
There's something wrong with a hidden tag in your JSP. Check the Struts 2 documentation on hidden tags (http://struts.apache.org/2.2.3/docs/hidden.html) to make sure everything's compliant. Try removing it temporarily, and if that fixes the problem start changing bits and pieces of it until you know what the problem is. Also, are you using Eclipse? If not you should, because it will make it a lot easier to figure out where things have gone wrong with your tags.