Showing results 1476 to 1500 of 1561

Feature
New Orphaned Backend User Interface

#93545 Inverse the behaviour of redirect creation after slug update

When ext:redirects is installed and a user changes a slug, TYPO3 creates new redirects for that slug. When done it shows a JS popup prompting the user if she wants to wants to

  • revert the slug change
  • revert the redirect creation

For big sites saving a page becomes very slow and in case the user decides to revert the change the time was wasted. For better UX and performance I like to propose to change the behavior and ask what to do before the redirects are getting created.

Author Stefano Kowalke
Created 02/18/21, 12:24
Updated 02/18/21, 12:24
Feature
New Orphaned Site Handling, Site Sets & Routing

#93535 Allow disabling of Mount Point link overlay for specific parts of the website

If I’m on a mount point page all links for the same mount point get overridden by the mount point path. I can disable this globally, so all pages get there original URL back, but I would like to only disable this feature for the main menu and keep it for the page content, so that if I navigate in the page content I stay inside the same mount point where possible, but if I change to a different page via the main menu, I will actually change the page even if I have a closer alternative via a mount point.
So I would suggest to add a new parameter for the MenuProcessor “disableMPOverlay” to remove the Link overlay for this specific menu. The function behind that should just work like the global typoscript-setting “config.MP_disableTypolinkClosestMPvalue”.

Author Anonymous
Created 02/17/21, 14:41
Updated 02/17/21, 14:41
Feature
New Orphaned TypoScript

#87551 Explicitly allow ignoring "pidInList" in TS select function

Currently, the implementation of the TypoScript function “select” will automatically set “pidInList” to “this” if it is not set, even when “uidInList” is specified and points to a uid on a different page.
The result will then be empty, even if the record exists and could be displayed. This is confusing and hard to understand, especially since there is no documented way of ignoring “pidInList”. Instead, some people implement workarounds with high recursion limits e.g. descending from the site’s root page.

My proposal is to add a new setting “ignore” that will lead to the value not being evaluated. This works already, since the non-empty value will prevent the default of “this” from being used. However, it is undocumented behaviour and thus might break in the future w/o any notice. Therefore, let’s make it explicit and document it.

Author Andreas Wolf
Assigned to Andreas Wolf
Created 01/25/19, 15:59
Updated 02/05/21, 16:57
Bug
New Orphaned TYPO3 CMS 10

#93433 TCA placeholder __row|field doesn't translate related records

When using the __row|field syntax in placeholders, the related row is not overlaid with its translation.

example TCA for a tt_content field:

    'tx_myext_teaser_title' => [
        'label' => $lll . '.tx_myext_teaser_title',
        'config' => [
            'type' => 'input',
            'placeholder' => '__row|tx_myext_teaser_page|title',
        ],
    ],

For a translated content element, the placeholder should be filled with the value from the translated page record.

Author Sebastian Michaelsen
Created 02/04/21, 11:40
Updated 02/04/21, 11:42
Feature
New Orphaned Security

#93390 Integrate source file based integrity check

  • having signed(!) list of valid hashsums of core and extension files
    • being part core release process
    • being part of TER publication process
  • system report comparing file hashes
    • detect modifications
    • detect additional files

This probably works for know locations, but cannot be applied directly to “arbitrary file storages” like /fileadmin/.

Author Oliver Hader
Assigned to Oliver Hader
Created 02/01/21, 07:56
Updated 02/01/21, 07:56
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#87759 Record preview fails when the record is disabled or before starttime because of routing

If I configure a preview button for a record leading to a routed detailpage the preview fails when the record is disabled or hidden by starttime.

It seems routing is unable to fetch the records slug because of a query restriction, this leads the preview running into a 404 error.

Greetings
Daniel

Author Daniel Dorndorf
Created 02/21/19, 09:41
Updated 01/20/21, 16:29
Bug
New Orphaned Workspaces TYPO3 CMS 10

#93286 Workspace notification Email not showing multiple page IDs

*Description:*
- When changing the stage of multiple pages at the same time, the notification mail will generate only one preview link for one page.

*Steps to reproduce*
1. Go to live mode
2. Create two pages with one or to content objects in each.
3. Switch to workspace
4. Make changes on two content objects from different pages
5. Switch to workspaces module
6. Select all the changed objects and send them to a different stage with a mass action

*Actual behavior*
An Email will be sent. In this Email there is only one preview link and all changes are listed under one site Id

*Expected behavior*
There should be one preview link for each site with changes on it. Also all changes are listed under one site.

Author Victor Manuel Grande Escanciano
Created 01/14/21, 07:33
Updated 01/14/21, 07:33
Bug
Accepted Orphaned Extbase TYPO3 CMS 8

#87655 Wrong count by extbase with own QueryBuilder

Hello Core-Team,

I have created my own Query with QueryBuilder. As I need a relation to categories I have to prevent duplicates through LEFT JOIN. So I have added GROUP BY to my QueryBuilder and give it to $query->statement($myQueryBuilder).

If I call f:count() in fluid on result it should return 13, but it returns 1. That’s because of a problem with COUNT and GROUP BY which results in:

COUNT
1
4
2
3
3

This problem is known in extbase. It is solved with help of $suggestDistinctQuery in Typo3DbQueryParser. But in case of an own QueryBuilder object, this property keeps untouched.

I prefer to check own QueryBuilder objects for an existing GROUP BY and set suggestDistinctQuery to true.

Stefan

Author Stefan Froemken
Created 02/05/19, 12:47
Updated 11/06/20, 09:09
Bug
New Orphaned Authentication TYPO3 CMS 6.2

#71312 fe_users: a logout does not clear the field 'is_online'

on login the field ‘is_online’ is written with a timestamp.
on interaction with the site the field is updated.
so you can consider an user as inactive if the timestamp is older than N minutes.

but if an user explicit logs out the field is not cleared but the last value stays in the field.
in this way you can not decide active users, as the the logged out user may have been called pages up until the logout and got a newer timestamp than an user which is reading for some time on a page and may interact in the next minute as his login is still valid.

Author Bernd Wilke
Created 11/04/15, 12:54
Updated 10/29/20, 09:31
Feature
New Orphaned felogin

#67453 fe_login redirect modes on logout

Now on logout, one can only redirect to $this->conf[‘redirectPageLogout’].

As I need the same redirect-functionality as on Login, I had to duplicate the code from login to the switch starting from line 726

                    switch ($redirMethod) {
                        case 'logout':
                            if ($this->conf['redirectPageLogout']) {
                                $redirect_url[] = $this->pi_getPageLink((int)$this->conf['redirectPageLogout']);
                            }
                            break;

Specially, the GET-/POST-variables where considered in my case:

            case 'getpost':
                    $redirect_url[] = $this->redirectUrl;
                    break;

Maybe, these should be solved in a more general matter. Why the redirect methods are not considered identically on logout as on login?

Author Michel Baeriswyl
Created 06/15/15, 10:54
Updated 10/21/20, 14:58
Bug
New Orphaned Linkvalidator TYPO3 CMS 11

#92586 Configuration for linktypes not considered in scheduler for linkvalidator

Linkvalidator report always reports results for external, internal (page) and file links, even if configuration was changed in scheduler

Reproduce

  1. set configuration in scheduler:
mod.linkvalidator.linktypes=external

Result

Only external link types will be checked but all will be reported. This means that the information for file and internal links reported may be stale.

It would probably better to separate the checking and reporting configuration (as is done in the checklinks “report” and “check” tab), and possibly separate the reporting (via email) and checking altogether, but while this is not yet done, I think the results give should be “fresh” and what was just checked.

Author Sybille Peters
Created 10/18/20, 14:29
Updated 10/18/20, 14:29
Bug
New Orphaned TYPO3 CMS 11

#92541 Text of flash message is misleading for JavaScript errors

Example: Page tree error message

Page tree error
Got unexpected response from the server. Please check logs for details.

When I get this type of error, the logs are usually empty. This is usually a JavaScript error displayed in browser console.

It would be great if error message which recommends to look in logs is only given if error has been logged.

Would be great if user got a different hint if there has been a JavaScript error.

Author Sybille Peters
Created 10/12/20, 11:53
Updated 10/12/20, 11:53
Bug
New Orphaned scheduler TYPO3 CMS 10

#92399 Scheduler tasks are executed in the same php process

Hi.

The new scheduler:run command runs tasks in a loop.
This can be an issue, because a single php process runs several tasks and those tasks share the same memory.

Example :
I have an issue with Solr indexing tasks: a site A is indexed and loads singletons (Extbase’s configuration manager), then the site B gets the configuration manager of the site A! (both sites are on the same TYPO3 instance).

I attached a patch which modifies the scheduler command in order to execute task in subprocesses.

Author Rémy DANIEL
Created 09/24/20, 16:41
Updated 10/07/20, 20:55
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#92368 PersistedAliasMapper: 404 error when linking to a non-translated news record

I get 404 errors on news detail pages in any translated language since the changes in the function resolve() from the following commit: https://github.com/TYPO3/TYPO3.CMS/commit/bd69d119a0a23381c358352b986c2466f600defb#diff-3497563e488963132628f6dc63ee879b

My website is configured in free mode.

If a news record has no translation, the URL is generated from the original news record path_segment and pointing to the translated detail page. With versions prior to 9.5.19 the original news was displayed on the translated page. Now I get a 404 error, because the path_segment in the URL does not match any translated news record path_segment.

If I overwrite the new PersistedAliasMapper resolve function with a custom mapper containing the previous function, the expected behaviour works again.

I think this change is causing the issue:

resolve function line 146-148 old version:

 $result = $this->getPersistenceDelegate()->resolve([
            $this->routeFieldName => $value
        ]);

Was changed to:

        $result = $this->findByRouteFieldValue($value);

Can you please check this issue?

Thanks!
Ulrike

Author cosmoblonde GmbH
Created 09/22/20, 12:25
Updated 09/22/20, 12:25
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#92361 Inconsistent port usage in redirects

Currently it is not possible to set up valid redirects with ports. One can enter a “<host>:<port>“ as <code>source_host</code> but this will be dropped again on next form display since the <code>SourceHost</code> evaluation marks the host as invalid.</port></host>

However, a port must be set here since the RedirectHandler does respect this. If redirects are set up without port, there is no match and the redirects won’t work.

Author Mathias Brodala
Created 09/21/20, 16:07
Updated 09/21/20, 16:07
Bug
New Orphaned TYPO3 CMS 10

#92288 Public access can't be denied in GeneratePublicUrlForResourceEvent

https://docs.typo3.org/m/typo3/reference-coreapi/10.4/en-us/ApiOverview/Hooks/Events/Core/Resource/GeneratePublicUrlForResourceEvent.html

> Method: setPublicUrl(?string $publicUrl)
> Description: Sets new public URL of resource – or removes public url (by setting null), disallowing public access.

Calling setPublicUrl(null) in an event listener does not disallow public access.

Perhaps GeneratePublicUrlForResourceEvent should implement StoppableEventInterface so we can force publicUrl = null.

As a workaround publicUrl can be set to an empty string (setPublicUrl('')). But that causes false URI generation using core ViewHelpers (e.g. f:uri.image) with absolute="true".

Author Georg Tiefenbrunn
Created 09/11/20, 12:13
Updated 09/11/20, 12:13
Bug
New Orphaned Install Tool TYPO3 CMS 10

#91800 Calculation of the relative path of the Typo3 library during CoreUpdate in combination with softlinks in the document path

Hello,

i have at my new webhoster there is an unusual directory structure. It has a mixture of softlinks and real directories.

Simplified and similar to this example:
/abc/softlink :: <- Link to /abc
/abc/customer/htdocs :: <- real directory with Typo3

For whatever reason, the hoster has now set it up so that the document path is: /abc/softlink/customer/htdocs

Unfortunately CoreUpdateService does not work like this. Because in the method: CoreUpdateService#activateVersion($version) the “realpath()” is created by the path of the Typo3 library:

$newCoreLocation = @realpath($this->symlinkToCoreFiles . '/../') . '/typo3_src-' . $version;

But then the method CoreUpdateService#getRelativePath(…) is used:
$newCoreLocation = $this->getRelativePath($newCoreLocation);

However, CoreUpdateService#getRelativePath(…) directly uses the document path (Environment::getPublicPath()) without “normalizing” it with realpath.
At my webhosts this unusual softlink is in the root directory. This creates a totally long and relative path. Which does not even work.

Therefore, the method CoreUpdateService#getRelativePath(…) suggests this correction:

    /**
     * Get relative path to TYPO3 source directory from webroot
     *
     * @param string $absolutePath to TYPO3 source directory
     * @return string relative path to TYPO3 source directory
     */
    protected function getRelativePath($absolutePath)
    {
        $sourcePath = explode(DIRECTORY_SEPARATOR, @realpath(Environment::getPublicPath()));
        $targetPath = explode(DIRECTORY_SEPARATOR, @realpath(rtrim($absolutePath, DIRECTORY_SEPARATOR)));
        while (count($sourcePath) && count($targetPath) && $sourcePath[0] === $targetPath[0]) {
            array_shift($sourcePath);
            array_shift($targetPath);
        }
        return str_pad('', count($sourcePath) * 3, '...' . DIRECTORY_SEPARATOR) . implode(DIRECTORY_SEPARATOR, $targetPath) ;
    }

So you can put “any” path in there and internally this method always works with the real paths.

Best regards
Clemens

Translated with www.DeepL.com/Translator (free version)

Author C. Gogolin
Created 07/14/20, 09:40
Updated 08/16/20, 14:28
Feature
New Orphaned Workspaces

#92004 Create redirect entry if updated slug is published to live

When the package typo3/cms-redirects is installed and a user updates a slug in the LIVE mode and saves it, a redirect is created for the old slug and redirects to the changed one.

This is should happen in a workspace as well as soon as the reviewer publishes the change. Within projects where changes entirely happen in a workspace, the really nice redirect feature is not usable at the moment.

Author Uwe Trotzek
Created 08/14/20, 11:22
Updated 08/14/20, 11:22
Bug
New Orphaned TYPO3 CMS 10

#91996 forms ignores the attribute "action" completely (method: get) - example_ext included

TYPO3 10.4.6

I would like to filter the pagination

For this purpose, I have created a form in the FLUID template, which should be sent to a “filterView”.
- Parameters should remain in the URL, therefore method=“GET”.
- Form action=“filter”.
- Controller has the method “filterAction()”.
- ext_localconf.php -> configurePlugin the “filterAction” is not(!) allowed.

Expectation: TYPO3 returns error message that “the filterAction is not allowed with this plugin…”.

Unfortunately, the server gives me an error message directly (Forbidden) or the action is not called at all and the page (FE) refreshes itself only without forwarding and without error message:

Original fluid-form with “GET” breaks completely with server-error “forbidden”.

Then I tried custom form viewhelper as described here:
https://www.ophidia.net/fluid-fform-referrer-deaktivieren/
doesn’t work either, unfortunately.

Also with a pure HTML-form-tag with action=“f:uri.action…” does not work.

So after texting in slack and after creating an example_extension (see appendix), I found a workaround by simply adding a “hidden-field” name=“action” value=“filter”. Then the “forms” work as they should.
That is, the form attribute “action” seems to be completely ignored…

————————
Example ext has some forms which shows the problem.
The filterAction has a “die()” in it – to see if it works or not.
Add TS to your PageTemplate and put the listView of that ext on a page.
At the List.html Template there are some comments.
————————
Example ext available at https://github.com/Teisi/test_form ,too.

Author Christian Hackl
Created 08/13/20, 13:15
Updated 08/13/20, 13:15
Feature
New Orphaned Extbase

#77025 f:form: Disable referrer information

On validation errors, extbase forwards to the referring action – potentially breaking actions because the original plugin settings are not available (see #70384).

Having the option to disable the inclusion of the referrer information in <f:form> would prevent this type of bug.

Please add an argument to <f:form> to disable the inclusion of referrer information.

Author Christian Weiske
Created 07/11/16, 11:19
Updated 08/13/20, 12:24
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 8

#91934 File abstraction layer: works odd with reindexing / extracting

Hi all,

File abstraction layer behaves odd for indexing and callbacks for extractors.

Using ext:extractor (but can be anything) cannot be run on scheduler task File Abstraction Layer: Extract metadata in storage (scheduler)

Setup:
  • ext:extractor installed and configured correctly; is called on file upload (working) as well should be called on above mentioned scheduler task
  • jpg’s with different meta-data in folder fileadmin/
  • after upload, imageA has it’s own metadata, as well imageB do so.
  • after copying imageA onto imageB (via console, under the hood):
    - nothing changes in metadata of imageB, witch should show now metadata of imageA, even:
    – running File Abstraction Layer: Extract metadata in storage (scheduler)
    – running File Abstraction Layer: Update storage index (scheduler) at first and then File Abstraction Layer: Extract metadata in storage (scheduler)
    – setting “last_index” to 0 before running one or both tasks (as mentioned in http://meberhard.me/tag/scheduler/)
    – setting modified-timestamp to creation-timestamp as mentioned in https://github.com/xperseguers/t3ext-extractor/issues/26#issuecomment-667834446 does not work
    – deleting the sys_file_metadata in der database for these two files and rerunning all previous steps does not help:
    it creates again sys_file_metadata-entries, but empty.

I didn’t find a way at all to reread metadata of files which are changed by an external script in meanwhile.

What i would expect is:
“Updates the Index/Cache Data of a Storage; only needed if changes to the storage are possible outside the backend (FTP, RemoteStorages).“
=> This is the original description of scheduler task Update storage index (scheduler) and it does not do it at all.
=> This is exactly what i’m searching for: Re-reading meta-data on existing files, which may have changed under the hood and are not modified by editors.

The whole behavior of the FAL-storage-indexer and extractor-callbacks seem to be very odd?

Thank you, Thomas

Author Thomas Sam Wittich
Created 08/05/20, 15:49
Updated 08/05/20, 15:49
Bug
New Orphaned Localization TYPO3 CMS 9

#91828 Translation does not work across domains/websites if the translated content of a second language is the default language of another domain/website

Following scenario:

website [1] domain.de
default language: German (Base: “/”; de_DE.utf8; de-DE)
additional language: English (Base: “/en/; en_GB.utf8; en-GB; Fallback: “Strict: show only translated content, based on overlays)

website [2] domain.ch
default language: Switzerland (Base: “/”; de_DE.UTF-8; de-DE) – I noticed that this might be wrong in terms of SEO so I wanted to switch it to “de-CH” and “de_CH.UTF-8“
additional language: French (Base: “/fr/; fr_CH.utf8; fr-FR)

website [3] domain.co.nz
default language: English (Base: “/”; en_NZ.utf8; en-GB)

*Problem:*
I want to use translated news records, event records from website [1] on website [3] (cross-domain, in English) but that’s not possible.

To make it work I have to create a “fake” English default language on website [3] which I have to disable so it will look like this:

website [3]
default language (disabled): English (Base: “/”; en_NZ.utf8; en-GB)
additional language: English (Base: “/”; en_NZ.utf8; en-GB)

Now I can use the translated news records from website [1] on website [3].

The same problem appears on website [1] and [2] with German and Switzerland, only there it’s not that obvious because Switzerland is also a German speaking country, so using the default language for news records works (besides I have to change ß into ss) manually.

I think the correct way would be to translate the German news to the Switzerland localization and then use the translated news on website [2] but that’s not possible because I would need to add German as the default language and disable it as well.

I also noticed that German is not available as language record on the root site [id=0].
Wouldn’t it be better to have all available languages for a TYPO3 instance on the root site [id=0]? The you can choose the desired languages for a website in the site configuration and maybe translations cross-domain would work that way? I would imagine that having German as an additional language on another website and then I want to use the German news records wouldn’t work too.

*In summary:*
It should be possible to use a language as the default and an additional language on different websites/domains and use translated records.

Can anyone reproduce and confirm the issue? I don’t know if the issue still exists on TYPO3 10.

Author David Menzel
Created 07/20/20, 10:28
Updated 07/20/20, 10:28
Bug
New Orphaned Logging TYPO3 CMS 7

#78849 Show logged records of DatabaseWriter in ext:belog

Log entries that have been persisted using the logging-framework are not visualized in ext:belog.
The reason is, that the logging-framework uses different field names for the sys_log table that are not considered.

Author Oliver Hader
Created 12/01/16, 12:33
Updated 07/08/20, 23:49
Feature
New Orphaned Reports

#91668 Add system communication API

A system communication API could be used to retrieve data from official typo3.org services or send back anonymous usage data in order to help understand TYPO3-use-cases much better.

Scenarios

  • compare current TYPO3 version with latest TYPO3 version & warn about missing security updates
  • fetch and display vendor messages for selected topics – e.g. release updates, important security notifications, etc.
  • send anonymous usage data back to granted services (typo3.org or custom endpoints)

Requirements

  • non-blocking – most of the communication shall happen in the background or in the client only (AJAX)
  • HTTP requests need to provide as less information as possible (no referrers, no cookies, …)
  • each used communication stream/channel must be opt-in – users or site admins have to subscribe
Author Oliver Hader
Created 06/17/20, 17:46
Updated 06/17/20, 17:46
Bug
New Orphaned Extbase TYPO3 CMS 10

#91661 Wrong recordType constraint in default FrontendUserRepository if subclass of FrontendUser exists

In versions prior to TYPO3 10 in Extbase’s TypoScript configuration the persistence subkey could be used in different scopes: config.tx_extbase, plugin.tx_extensionname and plugin.tx_extensionname_pluginname. In TYPO3 10 this configuration is done in PHP in Configuration/Extbase/Persistence/Classes.php with a global scope like config.tx_extbase. There is no possibility to set a non-global scope.

Until TYPO3 10 the persistence configuration of a subclass of FrontendUser could be set to a non-global scope in TypoScript like this:

plugin.tx_extensionname {
  persistence{
    classes{
      TYPO3\CMS\Extbase\Domain\Model\FrontendUser {
        subclasses {
          Tx_Extensionname_Modelname = Vendor\Extensionname\Domain\Model\Modelname
        }
      }
      Vendor\Extensionname\Domain\Model\Modelname {
        mapping {
          tableName = fe_users
          recordType = Tx_Extensionname_Modelname
        }
      }
    }
  }
}

In TYPO3 10 the persistence configuration can only be set to a gobal scope in PHP like this:

return [
    \Vendor\Extensionname\Domain\Model\Modelname::class => [
        'tableName' => 'fe_users',
        'recordType' => 'Tx_Extensionname_Modelname',
    ],
    \TYPO3\CMS\Extbase\Domain\Model\FrontendUser::class => [
        'subclasses' => [
            \Vendor\Extensionname\Domain\Model\Modelname::class,
        ]
    ]
];

The change from non-global to global scope breaks method addRecordTypeConstraint in TYPO3\CMS\Extbase\Persistence\Generic\Storage\Typo3DbQueryParser if at least one subclass exists. With a non-global scope no constraint was added from a query out of this scope. Now in TYPO3 10 a constraint for the subclass is always added because the persistence configuration is in global scope. It is impossible to query a default FrontendUser without a recordType set. $this->frontendUserRepository->findByUsergroup($usergroup) for example returns no records without a recordType set because a constraint for the recordType of the subclass is added.

As a workaround I added a recordType for the default FrontendUser class and additionally set the recordType of existing FrontendUser records to this value:

\TYPO3\CMS\Extbase\Domain\Model\FrontendUser::class => [
    'recordType' => 'Tx_Extbase_Domain_Model_FrontendUser',
]
Author Tobias Schmidt
Created 06/16/20, 18:48
Updated 06/16/20, 18:48

Showing results 1476 to 1500 of 1561