TYPO3 bugtracker - ISSUES

0013459: Front-end login is broken with Safari

Login not possible with mac, leopard 10 and safari 4.04.
No problems with Safari,Opera, IE on windows, or Firefox on Mac.

0013800: Cropping small images fails if noScaleUp is enabled

If the install tool option noScaleUp is enabled, so images won't be scaled up, cropping images won't work, if the desired dimensions are larger than the processed image.

The result is some missing path information in the imageInfo array returned by $cObject->getImgResource().

Imho if the image dimensions are smaller than the desired dimensions, still valid pathes to the temporary file should be returned.

0013721: No access to configuration in encodeTitle_userProc function from inside tx_realurl

RealURL provides a place where to call a user function for custom processing when encoding a title (from inside tx_realurl_advanced) or an alias (from inside tx_realurl). One would expect the same information to be available from inside that function. Unfortunately, this is not the case.

When tx_realurl_advanced is the parent object, it comes with the encoding configuration available as the "conf" member variable of the parent object. This corresponds actually to the "pagePath" part of the RealURL configuration.

But when tx_realurl is the parent object, it has no "conf" member variable. There is thus no way to get the encoding configuration (like the "spaceCharacter" for example). This is a problem when you need to fully re-encode the title or the alias inside the encodeTitle_userProc function (which is my case).

I propose to add the relevant configuration as an additional parameter to the function call. The attached patch does this. Note that - in the context of tx_realurl_advanced - the value of "strtolower" is hard-coded to "TRUE" since all titles are lower-cased by tx_realurl_advanced::encodeTitle().

0013799: [Feature] ExtJS driven fading in/out Flashmessages

This singleton class creates fading-in FlashMessages, they stay for given duration and then fade out again.

Possible usage:

TYPO3.Flashmessage.msg(1, "TYPO3 Backend - Version 4.4", "Ready for take off", 3);

See screenshot and example patch

0013750: Several GIFBUILDER features broken for IM4, IM6 and GM (Solution included!)

When IM4, IM6 or GM are used, several GIFBUILDER features that internally use mask images (e.g. SHADOW and NICETEXT) are broken.
The reason is a flawed processing of quoted parts in IM commands that probably has many more side effects.

0013461: wrong image-path returned in class.t3lib_tceforms.php if TYPO3-source is symlinked (backend-redesign)

If an extension is installed in 'typo3conf/ext/' and overrides BE-icons, the result of 't3lib_iconWorks::skinImg' (line:4008) is i.e. "../typo3conf/ext/myextension/icons/gfx/i/pages.gif".
thats correct, but if we use a symlinked TYPO3-source we get an incorrect path to the imagefile and so we do not get the correct image-dimensions from 'getimagesize' (line:4010)!

the result is, that dropdown-menus in backend-forms which contains icons, are not rendered correctly...icon is shown under text and text is positioned leftmost.

One possible solution is, to check if the path begins with '../' after 't3lib_iconWorks::skinImg' returned the image-path and pass the new full path to 'getimagesize'.
returned iconPath without patch is: /var/www/typo3-4.3.1/typo3/../typo3conf/ext/myextension/icons/gfx/i/pages.gif
returned iconPath with patch is: /var/www/typo3-4.3.1/typo3conf/ext/myextension/icons/gfx/i/pages.gif

it worked for me with the following modified lines:
4009,4010c4009,4014
< $iconPath = substr($selIconFile, strlen($this->backPath));
< $selIconInfo = @getimagesize(PATH_typo3 . $iconPath);
---
> if (substr($selIconFile,0,3)=='../') {
> $selIconInfo = @getimagesize(PATH_site.t3lib_div::resolveBackPath(substr($selIconFile,3)));
> } else {
> $iconPath = substr($selIconFile, strlen($this->backPath));
> $selIconInfo = @getimagesize(PATH_typo3 . $iconPath);
> }

0013798: empty redirect setting: login message without logout button

If a login doesn't have a redirect setting (for example if a login box is needed on any page and a user shouldn't be redirected at login) the logged-in message only gets the content of the markers ###STATUS_HEADER### and ###STATUS_MESSAGE###. The logout button isn't shown.

This can be fixed in class.user_felogin_pi1.php with the following three lines of code, which have to be inserted in the function showLogout() right before the line "// Hook for general actions after after login has been confirmed":

$subpart = $this->cObj->getSubpart($this->template, '###TEMPLATE_LOGOUT###');
$markerArray['###LOGOUT_LABEL###'] = $this->pi_getLL('logout', '', 1);
$markerArray['###USERNAME###'] = htmlspecialchars($GLOBALS['TSFE']->fe_user->user['username']);

0013486: wrong icon-state returned from 'getIcon' in class.t3lib_iconworks.php

the current TYPO3-code causes the following situation:

a page which is disabled because...
...the endtime is in the future, outputs the filename 'pages__f.gif' ($futuretiming = TRUE;)
...the starttime is in the future, outputs the filename 'pages__t.gif' ($timing = TRUE;)
...the endtime is in the past, outputs the filename 'pages__t.gif' ($timing = TRUE;)
...the starttime is in the future AND the endtime is in the future too, outputs the filename 'pages__tf.gif' ($timing = TRUE; $futuretiming = TRUE;)

that is actually ok, but if you want to use a preciser icon-set to visualize the exact state, you dont have a chance to get the right icon, because there is missing a code in the futuretiming-concept:

i.e.: if the starttime is in the future and the endtime is NOT SET, the page is inactive, and so we should have the case 'futuretiming' ...but TYPO3 just returns 'timing'. the filename we get is 'pages__t.gif'
thats the same file we get, when only endtime is set and is in the past.

this problem doesnt affect the current available TYPO3-backend-skins, because none of them is using such precise icons to visualize this states especially in combination with 'Hide in menu' or 'Hide page'.
but if we are interested in designing a new backend-skin where we are able to express all this states with a small icon (or icon-overlay), this part is our stumbling block!

the problem is also relevant, if you are about to use icons, which represents the page's current visility in the frontend!
...a patch would be great for editors, because they could see by mean of the icon, why a page is currently NOT visible.

so i have a little patch here which solve this problem and has downward compatibility too:
just add after line 192 in class.t3lin_iconworks.php the following code:
// ...And if "endtime" is NOT set:
if (!$row[$enCols['endtime']]) {
$futuretiming = TRUE;
}

because of the fact, that the original files 'pages__t.gif' and 'pages__tf.gif' are identically, the patch doesnt affect current TYPO3-installations.
...but with this all backend-skinner get new chances to create meaningful new icon-sets and improve the usability of TYPO3!

btw: this "bug" is very very very old...

0013487: no alternative icon returned from 'getIcon' in class.t3lib_iconworks.php (backend-redesign)

current situation:
the function 'getIcon' checks if an icon with the current states (hidden/timing/futuretiming/protected...) is available and returns this.
but if we are using an extension which overrides some icons AND provides additional icons which are NOT available in the source (i.e.: for some states which would be normally displayed with 'icon_not_found.gif' or the appendix '*__x.gif') it does not return the new icon, because there is no check to the alternative path given by $GLOBALS['TBE_STYLES']['skinImgAutoCfg']['absDir']

in fact there is no possibility to improve the backend with replacements for missing icons at this time.

...thats why the following modification would be fine for backend-redesigner and other people who wants to improve the default icon-set:

replace line 251:
if (@is_file(dirname($absfile).'/'.$iconFileName_stateTagged)) { // Look for [iconname]_xxxx.[ext]

with this line:
if (@is_file(dirname($absfile).'/'.$iconFileName_stateTagged) || @is_file($GLOBALS['TBE_STYLES']['skinImgAutoCfg']['absDir'].'/'.dirname($iconfile).'/'.$iconFileName_stateTagged)) { // Look for [iconname]_xxxx.[ext]

this will also check the location of the alternative icons added by an extension and finally returns the new icon.

0007893: Can not resolve path when installed as global extension

Setting up my first Typo3 4.2b3 site, I thought I was wise, and installed TemplaVoilà as a global extension so that I won't have to install it on every site I make.

I got the following error:

****
Error in init.php: Path to TYPO3 main dir could not be resolved correctly.

This happens if the last 6 characters of this path, /home/hageform/public_html/typo3/ext/templavoila/mod1/ ($temp_path), is NOT "typo3/" for some reason.
You may have a strange server configuration. Or maybe you didn't set constant TYPO3_MOD_PATH in your module?

If you want to debug this issue, please edit typo3/init.php of your TYPO3 source and search for the die() call right after this line (search for this text to find)...
***

It looks like TV doesn't like to be installed as a global extension.

- Mathias

0013797: Move checkbox "secondary options" to users module

It makes much more sense to move the checkbox "secondary options" to the user's settings module. This will also make the BE a bit cleaner

0009729: Ship optimal TYPO3 configuration by default

By default TYPO3 comes with unoptimal configuration due to the bugfix 0004962. It is time to change it to optimal. If some installation disable mod_rewrite, it is not a reason to ship badly optimized installation to the rest of the world.

To make optimal configuration, rename the following files from _.htaccess to .htaccess in the TYPO3 core:

./typo3/contrib/_.htaccess
./typo3/gfx/_.htaccess
./typo3/mod/user/ws/_.htaccess
./typo3/sysext/_.htaccess
./typo3/sysext/t3skin/stylesheets/_.htaccess

0013796: htmlArea RTE: Extjize Remove format dialogue

The attached patch rewrites the Remove format dialogue as an ExtJS window.

Additionnally, a new option is added to remove non-breaking spaces.

0003714: RTE htmlArea: Remove formatting does not remove non-breaking spaces and pop uwindow still too small.

Using the rtehtmlarea 'Remove formatting' function on a formatted text does not remove ' '

I expect this function to remove all kind of code from the source text, even html entities,
or at least replace a with a normal space.

Like reported in issue 0002229, the upcoming pop window still ist too small in firefox.

0009218: "removeformat" messes up some in-line formats

When "removeformat" for Word is run on a sequence like

abc def

abcdef

The result will be

abc>def

abcdef

instead of

abc def

abcdef

While the extra >, only shows up in certain test cases, the much bigger problem of, the bold setting not being reset seems to affect any sequence that resets bold too often. However, this is quite common in copy&paste imports from Word.

0008275: Could not remove span with style and font tags

I try to get rid of all font´s and span´s with a style attribute.
To achieve this, i´m trying to use the "Remove formatting" function, but all font´s and style´s stay. The are not removed.

0013791: RTE randomly inserts non-breaking spaces instead of spaces

When entering text in a RTE field, e.g., for a text content element or news, the RTE sometimes inserts a non-breaking space instead of a normal space character.

This happens with several versions of TYPO3 and Firefox, including the latest ones. So far I haven't been able to find the circumstances that trigger this behavior.

0012157: Empty paragraphs contain
in Firefox instead of i.e.

When I enter twice in rte the empty line looks as follows:
FF:

IE:

Sometimes in FF I also get an extra br-tag at the end of the last paragraph.

Sorry, I can't evaluate if this ist due to my rte configuration or simply a bug.

Typo3 4.2.4

0013795: htmlArea RTE: Extjize About window

The attached patch rewrites the About dialogue as a ExtJS window.

0013794: Problem with LIST2 view in standard template tt_news_v3_template.html

If there is an odd number of news messages in LIST2 view in tt_news_v3_template.html a closing div tag is missing.

0013052: New Content Element Wizard didn't load

Hello,

i was working on my typo3 site today, and at some point the new content element wizard stopped working.

If i click on the "create new element button" only a blank page is shown. Sometimes it will work, most times there's only a blank page.

What i've already found out:

If i change the following line:

$this->content = $this->doc->insertStylesAndJS($this->content);

to

$this->content .= $this->doc->insertStylesAndJS($this->content);

on line 283 in mod1/db_new_content_el.php
it will work all the time, but output is broken (tabs are there 2 times)

another thing: if i start firebug extension on my firefox and activate the network module, all files are reloaded all the time and bing -> the problem is gone.

so it looks like there is a caching problem or something.

i'm using version 1.4.1 which is tagged in the svn. Same problem with trunk version.

0012904: Exclude from speaking URL

Under Typo3 4.3 'exclude from speaking URL' page property isn't working any more for the first subpage when its parents are shortcuts. Example:

root (shortcut)
|
L main content (shortcut)
|
L home (standard page)

links to page home look like somedomain.com/home/ even though 'exclude from speaking URL' has been checked in the pages properties.

0013280: Exclude sysfolders from import for restricted users

Although a user only has access to a specific db mount, all sysfolders for the group of the user are shown in the select box in the importer.

We would be glad if you would review the attached patch and apply it to trunk.

0013648: Plaintext newsletter - first element in bulletlist always empty

When using the content element bulletlist the plaintext version of the newsletter always shows one additional element in front of the others, which is empty.
I added two lines of code which works for me.
in the function breakBulletlist in file direct_mail/pi1/class.tx_directmail_pi1.php Line 405:
// [...]
$cParts = explode(chr(10),$str);
// just delete the first element if it is empty
if (is_array($cParts) and !$cParts[0])
unset($cParts[0]);
reset($cParts);
// [...]

0004805: The plain text content could not be fetched. The HTML content could not be fetched.

When I want fetch and compile the newsletter. I get the following error:
"The plain text content could not be fetched.
The HTML content could not be fetched."
This problem was a topic in Typo3 bugtracker in the past (resolved) but there was no solution so far.
I clear the fe cache.