TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-03-05T08:52:51ZTYPO3 Forge
Redmine TYPO3 Core - Bug #87841 (Closed): Sitemap generation doesn't take request language into accounthttp://forge.typo3.org/issues/878412019-03-05T08:52:51ZSoren Mallingsoren@meteko.dk
<p>The sitemap.xml only takes content from the default language upon creation.</p>
<p>Case:</p>
<p>on domain.dk/sitemap.xml the sitemap is created with all content from the default language (in this case "Danish")</p>
<p>on domain.net/sitemap.xml it was expected to contain only content from the langauge of that site. Instead it takes the content of the default language.</p>
<p>Issue has been identified with Richard Haeser</p>
<p>Sitemaps can be found <a class="external" href="http://www.meteko.dk/sitemap.xml">www.meteko.dk/sitemap.xml</a> and <a class="external" href="http://www.meteko.net/sitemap.xml">www.meteko.net/sitemap.xml</a></p>
<p>Site configuration</p>
<pre>
rootPageId: 1
base: 'https://meteko.dk'
baseVariants: { }
languages:
-
title: Danish
enabled: true
languageId: '0'
base: /
typo3Language: da
locale: da_DK.utf-8
iso-639-1: da
navigationTitle: ''
hreflang: da-DK
direction: ltr
flag: dk
-
title: English
enabled: true
languageId: '2'
base: 'https://meteko.net/'
typo3Language: default
locale: en_US.utf-8
iso-639-1: en
navigationTitle: English
hreflang: en-US
direction: ltr
fallbackType: strict
flag: gb
errorHandling:
-
errorCode: '404'
errorHandler: Page
errorContentSource: '15'
routes: { }
routeEnhancers:
NewsPlugin:
type: Extbase
extension: News
plugin: Pi1
routes:
-
routePath: '/{news_title}'
_controller: 'News::detail'
_arguments:
news_title: news
defaultController: 'News::list'
aspects:
news_title:
type: PersistedPatternMapper
tableName: tx_news_domain_model_news
routeFieldPattern: '^(?P<path_segment>.+)$'
routeFieldResult: '{path_segment}'
PageTypeSuffix:
type: PageType
map:
sitemap.xml: 1533906435
</pre> TYPO3 Core - Bug #87581 (Closed): Reintroduce removed page tree TSconfig settingshttp://forge.typo3.org/issues/875812019-01-30T09:52:25ZSoren Mallingsoren@meteko.dk
<p>In issue <a class="external" href="https://forge.typo3.org/issues/82919">https://forge.typo3.org/issues/82919</a> a number of page tree settings was removed with the background of they werent used.</p>
<p>Feedback from users and clients have made us aware that at least of them was very actively used (excludeDoktypes) to hide specific doktypes in a pagetree. The client had 40.000 pages of a "Article" doktype that wasn't meant to be displayed in the tree.</p>
<p>This issue and following patch is solely to bring back the excludeDoktypes setting. None of the other settings are touched in this patch</p> TYPO3 Core - Feature #52080 (Rejected): Pre- and Post-process hook in DatabaseConnection for sql_...http://forge.typo3.org/issues/520802013-09-17T15:55:06ZSoren Mallingsoren@meteko.dk
<p>Since Extbase moved to use the TYPO3 Database API it's possible to add even more content/record security as focus can be put at one single entry point to the database.</p>
<p>This change introduces two new hooks (four, including the once for DBAL) before and after the general sql_query (used by Extbase).</p>
<p>From here you get the created query and the parent DatabaseConnection object. From here you can ex. check whether or not access should be granted to records fetched.</p> TYPO3 Core - Task #39603 (Closed): Move default columns to a backend_layout configurationhttp://forge.typo3.org/issues/396032012-08-08T00:41:03ZSoren Mallingsoren@meteko.dk
<p>Following the thread</p>
<p><a class="external" href="http://lists.typo3.org/pipermail/typo3-team-core/2012-August/052131.html">http://lists.typo3.org/pipermail/typo3-team-core/2012-August/052131.html</a></p>
<p>We came up with a concept of migrating the default 1,0,2,3 column to a backend_layout configuration</p>
<p>This makes it easier to work with the db_layout.php class, as there will be only one way to render the columns.</p>
<p>This task is a part of implementing drag'n'drop functionality, as this will clean up some code output and only have 1(!) markup</p> TYPO3 Core - Feature #38255 (Rejected): Post processors should be extendablehttp://forge.typo3.org/issues/382552012-06-21T15:53:41ZSoren Mallingsoren@meteko.dk
<p>It should be possible to extend postprocessor and add configuration</p>
<p>At this moment the postprocessors are hardcoded to only support "mail" where as postprocessors for stuff like persisting would make the FORM tool great for user registration etc.</p> TYPO3 Core - Task #30296 (Closed): Linkvalidator should have a hook for report markershttp://forge.typo3.org/issues/302962011-09-26T16:36:03ZSoren Mallingsoren@meteko.dk
<p>The Linkvalidator scheduler task should provide hooks within the markers, in order for administrators to create more detailed reports.</p>
<p>This hook gives the possibility to get the information about a page, and use it for any data purpose (user in charge, last update etc.)</p> TYPO3 Core - Bug #28756 (Closed): Cardlayout: Click in pagetree doesn't reload contenthttp://forge.typo3.org/issues/287562011-08-04T15:19:30ZSoren Mallingsoren@meteko.dk
<p><strong>Use case:</strong></p>
<ol>
<li>Click "Web" > "List" </li>
<li>Click on a page on your page tree</li>
<li>Click on a record you want to edit</li>
<li>Click on the page in your pagetree again</li>
</ol>
<p><strong>What happens:</strong></p>
<p>The list of records is not reloaded, you are "stucked" with the edit form</p>
<p><strong>What should have happened:</strong></p>
<p>The content area should reload and display the list of records on that page.</p>
<p><strong>Additional information:</strong></p>
<p>The same issue can be found if using the "Template" module and submodule "Info/modify"</p> TYPO3 Core - Bug #24273 (Closed): help_aboutmoules hardcoded as start up module - returns error i...http://forge.typo3.org/issues/242732010-12-02T13:24:03ZSoren Mallingsoren@meteko.dk
<p>With great features comes great responsibility ;)</p>
<p>As we are now able to uninstal former hardcodede extensions, some issues are shown.</p>
<p>If you uninstall the "aboutmodules" extension and haven't changed your "start up" module, the following error will be shown in the javacsript console/debug console</p>
<p>[string] help_aboutmodules was not found in modules</p>
<p>which is correct. The reason for this issue is at line 119 in t3lib/class.t3lib_beuserauth.php</p>
<pre><code>var $uc_default = Array(<br /> 'interfaceSetup' => '', // serialized content that is used to store interface pane and menu positions. Set by the logout.php-script<br /> 'moduleData' => Array(), // user-data for the modules<br /> 'thumbnailsByDefault' => 0,<br /> 'emailMeAtLogin' => 0,<br /> 'condensedMode' => 0,<br /> 'noMenuMode' => 0,<br /> 'startModule' => 'help_aboutmodules', <------ HERE</code></pre>
<p>The "aboutmodules" is hardcoded as startup module and only changed, if you as a user changes the settings.</p>
<p>What should be done here? Is it a administrator responsibility to change the default module for created users if he/she uninstall the default startup module?</p>
<p>(issue imported from #M16646)</p> TYPO3 Core - Feature #23589 (Rejected): Popup wizard doesn't close when clicking "save & close"http://forge.typo3.org/issues/235892010-09-24T09:13:24ZSoren Mallingsoren@meteko.dk
<p>Using below configuration in TCA.</p>
<p>The popup window doesn't close, but shows the "parent element" that "popped up" the window, since it's set in the returnUrl and you can't overwrite it.</p>
<p>A solution might be to overwrite the returnUrl, would this be accepted as a solution? </p>
<pre><code>'categories' => array(<br /> 'exclude' => 0,<br /> 'label' => 'LLL:EXT:mediadatabase/Resources/Private/Language/locallang_db.xml:tx_mediadatabase_domain_model_media.categories',<br /> 'config' => array(<br /> 'type' => 'select',<br /> 'foreign_table' => 'tx_mediadatabase_domain_model_category',<br /> 'size' => 10,<br /> 'maxitems' => 20,<br /> 'wizards' => array(<br /> '_PADDING' => 2,<br /> '_VERTICAL' => 1,<br /> 'add' => Array(<br /> 'type' => 'popup',<br /> 'title' => 'LLL:EXT:tt_news/locallang_tca.xml:tt_news_cat.createNewParentCategory',<br /> 'icon' => 'add.gif',<br /> 'params' => Array(<br /> 'table'=>'tx_mediadatabase_domain_model_category',<br /> 'pid' => '###CURRENT_PID###',<br /> 'setValue' => 'append',<br /> ),<br /> 'script' => 'wizard_add.php',<br /> 'JSopenParams' => 'height=280,width=465,status=0,menubar=0,scrollbars=1',<br /> ),<br /> ),<br /> ),<br /> ),</code></pre>
<p>(issue imported from #M15782)</p> TYPO3 Core - Bug #23582 (Closed): Docheader (save, save+view, save+close etc) missinghttp://forge.typo3.org/issues/235822010-09-23T09:43:08ZSoren Mallingsoren@meteko.dk
<p>Editing/creating new elements in any tables, no buttons are shown in the top.</p>
<p>Check out screenshot</p>
<p>(issue imported from #M15771)</p> TYPO3 Core - Bug #22654 (Closed): htmlArea RTE: RTE is greyed out and has no "styles" in page mod...http://forge.typo3.org/issues/226542010-06-01T12:01:50ZSoren Mallingsoren@meteko.dk
<p>Using revision 7796 the RTE is "greyed" out and lost default css style</p>
<p>(issue imported from #M14567)</p> TYPO3 Core - Bug #22770 (Closed): [No Title] shown when editing a record on root levelhttp://forge.typo3.org/issues/227702010-05-31T07:07:42ZSoren Mallingsoren@meteko.dk
<p>For records on root level the title of the record is not shown, when I edit the record.</p>
<p>E.g. the page title isn't shown, when editing page properties of the root page. (Have a look at attached screenshot.)</p>
<p>The field for pagetitle is filled and is shown in the pagetree.<br />The title is also displayed correctly, when the record I edit is not on root level.</p>
<p>(issue imported from #M14545)</p> TYPO3 Core - Bug #22766 (Closed): Export/Import to/from .t3d lacks new sprite iconshttp://forge.typo3.org/issues/227662010-05-30T23:01:14ZSoren Mallingsoren@meteko.dk
<p>The Export and Import to/from .t3d is lacking the use of the new sprite api</p>
<p>(issue imported from #M14541)</p> TYPO3 Core - Bug #22763 (Closed): Icons missing in page tree for "Page contains" pageshttp://forge.typo3.org/issues/227632010-05-30T22:56:52ZSoren Mallingsoren@meteko.dk
<p>After choosing from "Page contains"</p>
<p>no icons is shown in the page tree for these pages.</p>
<p>screenshot shows for pages containing</p>
<p>"News" <br />"Website users" <br />The dam created folder</p>
<p>using latest checkput from trunk</p>
<p>(issue imported from #M14538)</p> TYPO3 Core - Bug #22684 (Closed): "User Settings" doesn't have CSS stylehttp://forge.typo3.org/issues/226842010-05-19T19:45:24ZSoren Mallingsoren@meteko.dk
<p>Sorry if double posting, couldn't seem to find this issue.</p>
<p>Using revision 7641 (and before) the "User Settings" module is lacking of CSS due to wrong path for the compressor made CSS styles.</p>
<p>From</p>
<p>typo3/ext/setup/mod/index.php</p>
<p>the css is tried to be reached by the address</p>
<p><link rel="stylesheet" type="text/css" href="../typo3temp/compressor/element_csh-3d889fbcb8e616b940bdf33f8e49fbe2.css.gzip" media="all" /></p>
<p>Solution:<br />-------------</p>
<p>There should be a <base.. > or the links should be generated with a absolute url?</p>
<p>(issue imported from #M14437)</p>