TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-26T16:01:01ZTYPO3 Forge
Redmine TYPO3 Core - Bug #103490 (New): CKEditor wraps table head with <tbody>http://forge.typo3.org/issues/1034902024-03-26T16:01:01ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Team,</p>
<p>it is possible to create a table width header-rows oder header-col in CK-Editor. Now with a fine context menu. Unfortunately, the header is not wraped in a <thead></thead> but in a <tbody></tbody>. So if you define a table head, you got two <tbody> within your table tag. But for CSS it would be much easier to style, if you have a thead and a tbody. And the html is more valid.</p>
<p>Thank you <br />Martin</p> TYPO3 Core - Feature #96721 (Closed): Different cropping options for page ressource and tt_contenthttp://forge.typo3.org/issues/967212022-02-01T10:13:50ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Team,</p>
<p>thank you for the great cropping-Tool. I love ist and I am glad about the option of configuring it with TCEFORM. So I do not need an empty extension only for configuring TYPO3-features.</p>
<p>I can also create different cropping setting for different pages (e.g. News) via conditions.</p>
<p>Bit one thing I often longing for: A different setting für page media. Often page media is used for header images or background-images. These are completely different sizes than Text/Image-Contents.</p>
<p>Is there a way or would it be possible to create a way to differentiate in TCEFORM?</p>
<p>Thank you<br />Martin</p> TYPO3 Core - Bug #95815 (Closed): page type "shortcut" does not work in rightrestricted structurehttp://forge.typo3.org/issues/958152021-10-29T09:10:17ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-develoopers,</p>
<p>we found a problem as part of the rights restricted pages trees. The page type shortcut checks if the shortcut target exists and wheather it is accessable in the frontend. So it is quite reasonable, that it is not possible to tageting a page that is restricted, because someone without the proper rights would get an error.</p>
<p>But often, a whole subleveltree is restriked and accessable for the same FE-usergroup. It should be no problem, to allow a restricted target page if the restriction is the same than the shortcut page: Because averyone who can access the shortcut page would also access the target page.</p>
<p>In the earlier TYPO3-Version and even in TYPO3 11 it is not possible targeting a restricted page from a shortcut page with the same restriction. The shortcut type is therefore useless.</p>
<p>Solution: TYPO3 checks, if the settings of Usergroup Access Rights of shortcut page and target page is the same.</p> TYPO3 Core - Bug #94559 (Closed): ckeditor stops rendering links after <hr>http://forge.typo3.org/issues/945592021-07-14T10:53:37ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Team,</p>
<p>in my actual projekt, I created a text-content with too Lines. Every text line is linked to an internal page. If I save this state, both lines are linked to their pages correctly. Now I insert an hortizontal ruler (hr) between the lines. After that, only the first line has its correct link. The link of the second line is<br /><pre><code class="html syntaxhl" data-language="html"><span class="nt"><a</span> <span class="na">href=</span><span class="s">"t3://page?uid=107"</span> <span class="na">title=</span><span class="s">"Bearbeiten"</span><span class="nt">></span>Second Line<span class="nt"></a></span>
</code></pre></p>
<p>This happens in my individual ckeditor-config as well as in the default config. The <hr> (btw. it's not a <hr />) seams to stopp rendering the typo3-links.</p>
<p>It would be great, if there would be a solution.</p>
<p>Thanks very much and regards<br />Martin</p> TYPO3 Core - Bug #93141 (Closed): rte_ckeditor does not display horizontal rule but the encoded <...http://forge.typo3.org/issues/931412020-12-21T17:32:05ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Team,<br />I tried using the HorizontalRule and removed the entry HorizontalRule from the "removeButtons"-List. I got the Button to insert a HR and the preview in the editor showed an hr. But in the frontend, TYPO3 renders <br /><pre><code class="html syntaxhl" data-language="html"><span class="nt"><p></span><span class="ni">&lt;</span>hr /<span class="ni">&gt;</span> <span class="nt"></p></span>
</code></pre><br />I could not find. where to change this. Also I tried the same in different installations. All the same. This should be work out of the box, shouldn't it?</p>
<p>Thanks for have a look.<br />Bye and merry christmas<br />Martin</p> TYPO3 Core - Bug #91979 (Closed): detectDomainRecords.target is set but no target is in a-taghttp://forge.typo3.org/issues/919792020-08-11T16:36:34ZJoe Jonesfoesse@web.de
<p>Dear dev-team,</p>
<p>I had problems, giving the links of the searchresults a target. In the Dokumentation there is detectDomainRecords.target, but is has no effect. I checkt the sourcecode and found the mistake in Classes/Controller/SearchController.php:</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="k">protected</span> <span class="k">function</span> <span class="n">preparePageLink</span><span class="p">(</span><span class="kt">int</span> <span class="nv">$pageUid</span><span class="p">,</span> <span class="kt">array</span> <span class="nv">$row</span><span class="p">,</span> <span class="kt">array</span> <span class="nv">$urlParameters</span><span class="p">):</span> <span class="kt">array</span>
<span class="p">{</span>
<span class="nv">$target</span> <span class="o">=</span> <span class="s1">''</span><span class="p">;</span>
<span class="nv">$uri</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-></span><span class="n">controllerContext</span><span class="o">-></span><span class="nf">getUriBuilder</span><span class="p">()</span>
<span class="o">-></span><span class="nf">setTargetPageUid</span><span class="p">(</span><span class="nv">$pageUid</span><span class="p">)</span>
<span class="o">-></span><span class="nf">setTargetPageType</span><span class="p">(</span><span class="nv">$row</span><span class="p">[</span><span class="s1">'data_page_type'</span><span class="p">])</span>
<span class="o">-></span><span class="nf">setUseCacheHash</span><span class="p">(</span><span class="kc">true</span><span class="p">)</span>
<span class="o">-></span><span class="nf">setArguments</span><span class="p">(</span><span class="nv">$urlParameters</span><span class="p">)</span>
<span class="o">-></span><span class="nf">build</span><span class="p">();</span>
<span class="c1">// If external domain, then link to that:</span>
<span class="k">if</span> <span class="p">(</span><span class="o">!</span><span class="k">empty</span><span class="p">(</span><span class="nv">$this</span><span class="o">-></span><span class="n">domainRecords</span><span class="p">[</span><span class="nv">$pageUid</span><span class="p">]))</span> <span class="p">{</span>
<span class="nv">$scheme</span> <span class="o">=</span> <span class="nc">GeneralUtility</span><span class="o">::</span><span class="nf">getIndpEnv</span><span class="p">(</span><span class="s1">'TYPO3_SSL'</span><span class="p">)</span> <span class="o">?</span> <span class="s1">'https://'</span> <span class="o">:</span> <span class="s1">'http://'</span><span class="p">;</span>
<span class="nv">$firstDomain</span> <span class="o">=</span> <span class="nb">reset</span><span class="p">(</span><span class="nv">$this</span><span class="o">-></span><span class="n">domainRecords</span><span class="p">[</span><span class="nv">$pageUid</span><span class="p">]);</span>
<span class="nv">$uri</span> <span class="o">=</span> <span class="nv">$scheme</span> <span class="mf">.</span> <span class="nv">$firstDomain</span> <span class="mf">.</span> <span class="nv">$uri</span><span class="p">;</span>
<span class="o">*********</span> <span class="nv">$target</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-></span><span class="n">settings</span><span class="p">[</span><span class="s1">'detectDomainRecords.'</span><span class="p">][</span><span class="s1">'target'</span><span class="p">];</span><span class="o">*********</span>
<span class="nb">print_r</span><span class="p">(</span> <span class="nv">$this</span><span class="o">-></span><span class="n">settings</span><span class="p">[</span><span class="s1">'detectDomainRecords'</span><span class="p">][</span><span class="s1">'target'</span><span class="p">]);</span>
<span class="p">}</span>
<span class="k">return</span> <span class="p">[</span><span class="s1">'uri'</span> <span class="o">=></span> <span class="nv">$uri</span><span class="p">,</span> <span class="s1">'target'</span> <span class="o">=></span> <span class="nv">$target</span><span class="p">];</span>
<span class="p">}</span>
</code></pre>
<p>The marked line must be:<br /><pre><code class="php syntaxhl" data-language="php"><span class="nv">$target</span> <span class="o">=</span> <span class="nv">$this</span><span class="o">-></span><span class="n">settings</span><span class="p">[</span><span class="s1">'detectDomainRecords'</span><span class="p">][</span><span class="s1">'target'</span><span class="p">];</span>
</code></pre></p>
<p>Maybe you can verfy this and patch it the next time.</p>
<p>Thank you and regards<br />Martin</p> TYPO3 Core - Feature #91835 (Under Review): TCAdefaults set for CTypes like TCEFORMhttp://forge.typo3.org/issues/918352020-07-21T18:58:46ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Team,<br />thanks for your great work. I have two improvements as a feature request for TCAdefaults:</p>
<p><strong>1. As in TCEFORM it would be great to specify a CType</strong><br /><pre>
TCAdefaults.tt_content.layout = 1
TCAdefaults.tt_content.types.image.layout= 2
</pre><br />This sets the default layout for images different to the other CTypes. This way would be a very consistent way to configure.</p>
<p><strong>2. Set TCAdefaults even for fields that are disabled</strong><br />Sometimes you would like to set e.g. different layouts via page ts but do not want the editor to change it. Att he moment TCAdefaults are only work, if the field is accessable for the editor. Maybe you could change that?</p>
<p>Have a good day<br />Martin</p> TYPO3 Core - Bug #81573 (Closed): Scheduler config check and documentationhttp://forge.typo3.org/issues/815732017-06-14T12:28:24ZJoe Jonesfoesse@web.de
<p>Dear core developers,</p>
<p>I am working with TYPO3 8.6.1 LTS now and had some problems to build the scheduler cron job. One probnlem is the documentation. The cron parameter changed and "scheduler" is depricated. It was not easy to find the correct parameter. But this works: <br /><pre>
.../typo3/sysext/core/bin/typo3 scheduler:run
</pre><br />It would be nice to find this in the scheduler configuration check in the backenend. At the moment there is written erroneously: <br /><pre>
Der Befehl, um den Planer von der Kommandozeile auszuführen lautet: "/.../typo3/sysext/core/bin/typo3 scheduler".
</pre></p>
<p>Also in the scheduler check there is a problem with the point "CLI-Skript". Even if the cron jobs works, the config checks alerts a missing cron job. In the point "Last run (Letzte Ausführung) there is listet the correct timestamp for the last cron job run. TYPO3 seams to be conencted correcty, but the config check does not notice it.</p>
<p>Thanks <br />Martin</p> TYPO3 Core - Bug #81211 (Rejected): Uncought Exeption in list-modul (NAMEPREP: Prohibited input U...http://forge.typo3.org/issues/812112017-05-12T15:27:59ZJoe Jonesfoesse@web.de
<p>Dear TYPO3 Team,</p>
<p>I updated a TYPO3 Installation. The Install Tool was fine (not as told in Bug <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: 8.7 LTS Upgrade Wizard: Execute database migrations on single rows failed (Closed)" href="http://forge.typo3.org/issues/80723">#80723</a>), but the same exeption is thown in the list modul. In the module web it is no problem.</p>
<p>Not alle pages with email adresses make problems. Maybe it is not even an upgrade problem.</p>
<p>1. Adding a new contentelement Image/Text.<br />2. Adding text with the ckeditor. Just a few simple lines with ü, ä, ö<br />3. Save and open list modul <br />--> No problem<br />4. Open the CE and adding a line with an email adress at the end<br />5. Save and open list modul <br />--> No problem<br />6. Open the CE and adding some english text<br />7. Save and open list modul <br />--> No problem<br />8. Open the CE and adding some Text with ö, ü, ä<br />9. Save and open list modul <br />--> the list modul crashes</p>
<p>Following pattern makes problems:<br />- string@string followed by any umlaut</p>
<p>Following patterns make no problems<br />- string ummlaut <br />- string string umlaut sting<br />- string space <code> space string umlaut<br />- string space @string umlaut<br />- string</code> space string umlaut<br />- <LINK <a class="email" href="mailto:email@address.tld">email@address.tld</a>>string space @ space string</LINK> umlaut (setting link with link editor)</p>
<p>It seams, that the conventional pattern of an email address as link text breaks the link validator, if an special char (umlaut) follows -- strange correlation :-/</p>
<p>Please check this and ask, if you need additional informationen.</p>
<p>Thank you<br />Martin</p> TYPO3 Core - Bug #81104 (Closed): ckeditor does not converts inch-mark to " entityhttp://forge.typo3.org/issues/811042017-05-02T12:14:58ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Team,</p>
<p>by changing to the new RTE-Editor I found a problem with quotationmarks. The typed " does not encoded to &quod; (see Screenshot). The green one was formated by the old RTE and afterwards quotes where replaced by stdWrap.replacement in „ resp. “. The yellow marks are formated by the ckeditor. It is still an inch-mark.</p>
<p>Please have a look at it. It is quite important for correct typography in the web.</p>
<p>Thank you for your work<br />Martin</p> TYPO3 Core - Feature #80228 (Closed): Missing non breaking space in glyphen-popup in ckeditorhttp://forge.typo3.org/issues/802282017-03-10T13:21:10ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Team,</p>
<p>I just found out, that there is no non breaking space ( ) in the glyphe popup of ckeditor. Maybe is has gone by the board.</p>
<p>Best wishes <br />Martin</p> TYPO3 Core - Bug #80205 (Closed): filebrowser mark files results strange CSS-behaviour in Chrome ...http://forge.typo3.org/issues/802052017-03-09T11:54:29ZJoe Jonesfoesse@web.de
<p>Hallo TYPO3 Team,</p>
<p>i am using TYPO3 8.6.1 and I found a bug in the filebrowser. When marking the files for import in the media list, the html/CSS of the popup gets mixed up. Maybe it depence on the scroll position.I had the problem on selecting files down in the list. In Opera the visible area changes on every click. In Chrome the view vanishes completely by clicking one select box.</p>
<p>See screenshot</p>
<p>Regards<br />Martin</p> TYPO3 Core - Bug #79351 (Closed): ckeditor adds empty paragraph on every content http://forge.typo3.org/issues/793512017-01-17T11:53:07ZJoe Jonesfoesse@web.de
<p>I am looking forward to a new RTE in TYPO3. I tried the experimental ckeditor and found out, that it always adds a <p> </p> at the end of the content. I found some possible solutions, but it is not clear, where to put the config-parameter for ckeditor. I tried in Ressources/Public/JavaScript/defaultconfig.js, but changes did not change anything. <br />So this issue is two issues: <br />1. Bug: undesirable <p> </p><br />2. Feature Request: central settings and documentation</p>
<p>Thank you and keep on :-)</p> TYPO3 Core - Bug #77541 (Closed): Lost Page media after translation and at news media Image-Edito...http://forge.typo3.org/issues/775412016-08-18T14:55:18ZJoe Jonesfoesse@web.de
<p>Hallo dear TYPO3 Developers,</p>
<p>an important bug is in TYPO3 8.3.2 in the multilanguage support:</p>
<p>1. Creating translation of a page does not adopt the ressource media of the standard page property.<br />2. Adding a ressource media to the translated page property is possible, but the image editor to create crops is not available.</p>
<p>In my case the header image now is rendered much to small, 'cause it assumes, that the ditor has cropped the image to a fixed proportion. The best would be, as the content elements do, the translated page adopts all properties of the standard page and you can change settings if necessary. <br />The missing Image Editor should be in translated resource medias as well.</p>
<p>Thanks<br />Martin</p> TYPO3 Core - Bug #77193 (Closed): Wrong Resourcepath for BE-Icons in form.csshttp://forge.typo3.org/issues/771932016-07-21T12:31:42ZJoe Jonesfoesse@web.de
<p>Dear TYPO3-Developers,</p>
<p>at first thanks for your great work. I just set up the new TYPO3 8.2 version and found a small problem in the tx_form sysext:</p>
<p>In form.css in line 577 and 580 you link to the resource "actions-delete.svg" and "actions-open.svg". But the path has one "../" too much</p>
<p><strong>correct Path:</strong><br />#fake-form .formwizard-element button.t3-icon-edit-delete {<br /> background-image: url('../../../../core/Resources/Public/Icons/T3Icons/actions/actions-delete.svg');<br />}<br />#fake-form .formwizard-element button.t3-icon-document-open {<br /> background-image: url('../../../../core/Resources/Public/Icons/T3Icons/actions/actions-open.svg');<br />}</p>
<p>For the next release :-)</p>
<p>Bye</p>