We are using TYPO3 8.7.19 with the extension frontend_editing (Version: 1.4.0) and CoolURI. We still use css_styled_content.
When editing a content element in the frontend with the „frontent-editing bar”, e.g. text I get an error, but only, if it contains an internal link.
The changes are not saved. It crash with:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1460629247: No valid handlers found for type: unknown | TYPO3\CMS\Core\LinkHandling\Exception\UnknownLinkHandlerException thrown in file /usr/share/typo3/typo3_src-8.7.19/typo3/sysext/core/Classes/LinkHandling/LinkService.php in line 163. Requested URL: https://www.mysite.de/typo3/index.php?ajaxID=%2Fajax%2Ffrontend-editing%2Fprocess&ajaxToken=--AnonymizedToken--&page=123
There is a bug report and a suggested solution für TYPO3 9.5.x and a solution for TYPO3 8.7.x
Unfortunately, I don't know how to realize that solution for my system, cause
wee use coolURI but not the required realurl-xtension.
I don't know where to add the suggested code
Any hints for me?
Problem has been solved by the author of frontend_editing:
Add in typo3conf/ext/frontend_editing/Configuration/TypoScript/setup.ts
# Prevent links from being parsed to FE url
lib.parseFunc_RTE.tags.a >
Related
I'm using TYPO3 V11.5 with an extension, which has only a backend module.
Therefore it doesn't exist any configPlugin and also no ext_localconfig and under Configuration->TCA->Overrides no tt_content.php file.
If I try to call the backend I get the following error message:
What is required to avoid this error or is it an TYPO3 bug?
Edit
Stupid misteake, forgot to include the extension template under Template->Includes!
Without having too much code I guess it is because the class really does not exist! Is the file really called BackEndController and also the class in it BackEndController with an uppercase E?
I made an error when using a ViewHelper with an unsupported argument and my Fluid Partial wasn't rendered at all.
How can I debug / track down problems like these? Usually I would expect an exception to be thrown. I enabled debug preset and there is nothing in the sys_log, no error message is displayed.
Is there some setting I can use to cause error messages to be created or more information to get logged?
Reproduce
Use Fluid ViewHelper with unsupported argument (here, name is not a supported argument):
<f:uri.external name="something" uri="https://typo3.org">f.uri.external</f:uri.external>
Result
The Fluid Partial is not displayed at all.
most of the time I'm using to check do I even get wanted values before:
<f:debug>{_all}</f:debug>
or
<f:debug>{variable}</f:debug>
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.
Been successfully using Orbeon 4.4CE for a long time, but today the Form Editor seems to have suddenly broken. Creating a new form (or editing an existing form) shows a partial toolbox missing most of the controls.
Log file reveals this:
INFO ProcessorService - /fr/service/custom/orbeon/builder/toolbox - Received request
ERROR XSLTTransformer - Error at line 32 of oxf:/forms/orbeon/builder/service/toolbox.xsl:
An empty sequence is not allowed as the value of variable $resources-property
ERROR PageFlowControllerProcessor - error caught {controller: "oxf:/apps/fr/page-flow.xml", method: "GET", path: "/fr/service/custom/orbeon/builder/toolbox"}
Configuration is Orbeon 4.4, MySQL persistence layer with MySQL 5.6, Java 1.7.67 and Tomcat 7.0.52 on Ubuntu 14.04. This was working fine as of late last week, and now seems broken on several systems all at once. Nothing in the configuration has changed in several months (as verified by a scan looking for files having recent modification times).
UPDATE: The problem is actually worse than I suspected...I copied an existing, working form from the MySQL orbeon_form_definition table to another Orbeon instance, and the form does not run. The Orbeon log file shows: "An empty sequence is not allowed as the value of variable $captcha" (the form does not use Captcha codes in any way).
We also tried installing a copy of Orbeon 4.7.0CE, and it appears to have similar symptoms.
The same problem is now occurring on three completely independent (but similarly configured) systems - we do not have a way to edit or create new forms using Form Builder, or even to move existing forms around between systems by updating the database definitions.
Any suggestion how to fix this, or even to diagnose where the problem might be?
Today I had a very similar problem.
I created a new form and didn't saw the toolbox controls:
Looking in the log there was the following error:
2018-03-16 10:33:26,212 ERROR XSLTTransformer - Error at line 32 of oxf:/forms/orbeon/builder/service/toolbox.xsl:
An empty sequence is not allowed as the value of variable $resources-property
2018-03-16 10:33:26,239 ERROR PageFlowControllerProcessor - error caught {controller: "oxf:/apps/fr/page-flow.xml", method: "GET", path: "/fr/service /custom/orbeon/builder/toolbox"}
2018-03-16 10:33:26,411 ERROR PageFlowControllerProcessor -
The reason was the name I had chosen for the form: reset-password. I changed the name in something else and the problem wasn't any more.
It seems that the form name must not contain the string "password".
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.