Since a long time it’s possible to split your TypoScripts into external files and include them from your template via
<INCLUDE_TYPOSCRIPT: source="FILE: fileadmin/fileToInclude.ts">
So it’s very easy to use your favorite editor and, more important, organize the TypoScript-Files into smaller, reusable chunks.
My common setup is something like that:
<INCLUDE_TYPOSCRIPT: source="FILE: fileadmin/tpl/include.ts">
But there is one large downside. Every include adds an
[GLOBAL] at the end of file. So it’s not possible to include files based on a multi level condition. For example if you like to develop a new design and want to test it on a test domain. For more information see https://forge.typo3.org/issues/16525
But since Typo3 7.6 there is something which can help. Continue reading
After upgrading a Typo3 4.5 Installation to Version 6.2 your old pibase extension may still running. Hmm .. at least mostly 🙂
You just need to remove some
requice_once statements and modify the
ext_table.php to use the
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility class. Most of the other stuff is still there.
Once when you try to upgrade to version 7.6 you are in need to modify a bit more. But don’t worry. After all it isn’t that complicated. And by the way … you don’t need to wait until you upgrade. These changes are running very well even in an 6.2 installation.
So here is a small list of needed action to upgrade from 4.5 via 6.2 to 7.6 🙂
After you upgraded from a Typo3 Version 4.5 LTS to Version 6.2 or higher you may wounder why the backend search is not working anymore as expected. Even in the list mode the result of extension records can be empty.
If it’s your own extension you can fix it very easy. Since Version 4.6 the search behavior was changed (see https://forge.typo3.org/issues/36452).
To re-enable the search function of your own extension records to have to add this line to your
$TCA['name_of_table']['ctrl']['searchFields'] = 'col1, col2, col3';
Just include all columns which make sense. Clear the system cache and it’s done. Of course you need to do this for every table which you wanted to be searched 🙂
If you like to upgrade your mysql installation to a newer version you may try this:
First of all we need to add a repo with contains the new mysql version. I’ve chose the one of the IUS Community
Then we need to check what currently is installed:
# rpm -qa | grep mysql
We need to remove the old stuff. Be sure to select only the parts we can really get rid off 🙂 Never every remove the one which starts with plesk-mysql-server !
rpm -e --nodeps mysql-server-5.5.48-1.el6.remi.x86_64 mysql-libs-5.5.48-1.el6.remi.x86_64 mysql-5.5.48-1.el6.remi.x86_64 compat-mysql51-5.1.54-1.el6.remi.x86_64 compat-mysql51-5.1.54-1.el6.remi.x86_64
Now install the new one. In my case I want mysql 5.7:
yum install mysql57u-server.x86_64 mysql57u.x86_64
Since the databases are in the old format we need to upgrade them to work with the new server version:
mysql_upgrade -u admin -p`cat /etc/psa/.psa.shadow`
This may take a while. After that you should restart the mysql server.
If you every modified
/etc/my.cnf you may should have a look since it may reset to the defaults. But don’t worry. The original one should be saved to my.cnf.rpmsave (or something similar).
I really like to you the hibernate mode of Windows. And it’s working very fine. However I recently added a new mouse device. First it seems to work but when I accidentally moved my mouse while the PC was in hibernate the computer restarted! The quickest way to find out which device is able to awake the computer and disabled it is to use the command line:
powercfg -devicequery wake_armed Will list all devices which are allowed to wake up the computer.
powercfg -devicequery wake_programmable will list all disallowed devices.
Now you just have to pick the right one from the allowed list and disable it with this command
powercfg -devicedisablewake deviceNname
For what ever reason I had to disable all devices until the movement of my mouse didn’t wake up the PC any longer.
If you wounder how to create links in an extbase controller instead of using the old
pi_getPageLink methode you should have a look at this:
To get more information you may search for
If you have a problem when uploading images with umlauts in the file name you first stop may will be to check the
config.local_all setting. The setting should match some value of the
locale -a command of the server. Mose of the time it’s something like
But if you still getting errors like
/usr/local/bin/gm convert: Unable to open file ([image file name]) [No such file or directory].
You should also set
systemLocale of the Typo3 configuration. The most simple way to do this is to use the Installation Tool/All Configuration:
$TYPO3_CONF_VARS['SYS']['systemLocale'] = 'de_DE.utf-8';
If you like to delete mails from the mail queue of postfix on a given pattern (from/sender email) you can use this command:
postqueue -p | grep "firstname.lastname@example.org" | cut -f 1 -d ' ' | xargs -n 1 postsuper -d
postqueue -p you’ll get the queue.
grep just selects the line with the sender AND the message id.
cut extracts the message id.
xargs/postsuper will delete the message
Since Version 10 it’s possible that the password of the mysql database of Plesk is, well they call it encrypted. This is basically fine, but may can run you in some trouble. For example if you like to install you own global phpMyAdmin installation and then try to log in as
You’ll first try will be to use the same password as you will use when log in to Plesk. That will not work! Then you’ll may step over the ssh shell and type in
This will give you something like
Yeah … that looks like the password is encrypted. As Plesk admin you know an other way to get the password
This will output the password you already tried. Then you’ll dig around the internet and may find this cmd
mysql -uadmin -p`cat /etc/psa/.psa.shadow`
And … it’s working! You get access to mysql. Hmm … now you’re may a bit confuse. But thing about it. If you want to access your mysql database outside of Plesk you have to use the whole output of
as password! Even if it look like it’s encrypted. This is your database password!
If you don’t like to have such a super long password and can live with a plain text password in the file
/etc/psa/.psa.shadow you can change it back. But remember to repeat this every time you change the password via the Plesk panel 🙂
/usr/local/psa/bin/init_conf -u -passwd 'some_password' -plain-password
Alternative you can add an other user with full admin rights to your database.
As server admin you are sometimes in the need to know the password of an email address. Plesk is making this very easy. Just run this command and you’ll get a list of all mail accounts of your server. Also the plain text password of the accounts are shown 🙂
Of course of have to adjust the path to your Plesk installation.