Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 83 bytes) in /typo3/sysext/core/Classes/Database/DatabaseConnection.php on line 1038 + TYPO3


Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 83 bytes) in /typo3/sysext/core/Classes/Database/DatabaseConnection.php on line 1038 + TYPO3

Some time we are facing the issue of memory size exhausted in typo3 backend.

We are also facing “Allowed memory size of 134217728 bytes exhausted” issue while we save records in backend module.

Like : Edit page content, Powermail field data, News records or any other field data.

We can set memory limit in php.ini file as well. if we are not able to change on server file then we can also manage it from typo3 configuration.

Following script we have to set in “LocalConfiguration.php” OR you can directly set on the Install Tool set.

$TYPO3_CONF_VARS['SYS']['lockingMode'] = 'disable';

If this is not working for you then you can also set “setMemoryLimit” in your LocalConfiguration file.

$TYPO3_CONF_VARS['SYS']['setMemoryLimit'] = '16M';

Ie that 16 MB must use to run the script. Since it can then sometimes happen that the allocated 16 MB are not enough. so we can set it more from LocalConfiguration file and also manage it from install tool.

i hope it will work for you 🙂

If you have any queries, please do not hesitate to contact me at Jainish Senjaliya

readLLXMLfile error in typo3 extbase extension


While TYPO3 update to TYPO3 6.2 and Pi-Based Extensions throws error of “t3lib_div::readLLXMLfile” which is deprecated in typo3 6.2.xx version

updating TYPO3 from 4.5 to 6.2 version many Pi-Based Extension adjustments a particularly annoying bug has stayed with us.

For me, this error has only be shown if a new content item in the backend should be created.

The error was in the PI1, PI2, … ” … wizcon.php “file and generated a 500 error.

Following error may show in your backend area

( ! ) Fatal error: Call to undefined method TYPO3\CMS\Core\Utility\GeneralUtility::readLLXMLfile() in C:\wamp\www\typo3\jainish\typo3conf\ext\js_contact_form\pi1\class.tx_jscontactform_pi1_wizicon.php on line 72
readLLXMLfile

readLLXMLfile

t3lib_div :: readLLXMLfile is not supported in latest version of typo3. we have to replace those deprecated function to new function

To correct the problem, you have to replace both line.

// OLD CODE
$llFile = t3lib_extMgm::extPath('YOUR_EXTENSION').'locallang.xml';
$LOCAL_LANG = t3lib_div::readLLXMLfile($llFile, $GLOBALS['LANG']->lang);

// New Code 
$llFile = \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::extPath('YOUR_EXTENSION').'locallang.xml';						
$parser = t3lib_div::makeInstance('t3lib_l10n_parser_Llxml');
$LOCAL_LANG = $parser->getParsedData($llFile, $GLOBALS['LANG']->lang);

I hope this will work for you.

If you have any queries, please do not hesitate to contact me at Jainish Senjaliya

Sorry, you didn’t have proper permissions to perform this change + Typo3 4.7 TemplaVoila


 
After installing TemplaVoia. and i try to add page content element on page. that time i suddenly received is :

“Sorry, you didn’t have proper permissions to perform this change.”

The following SQL should do the trick and also fixed your problem.

ALTER TABLE pages ADD t3ver_swapmode tinyint(4) NOT NULL default '0'

I hope it will work for you 🙂

Because of this issue your template may not render on front end side.

If you have any queries, please do not hesitate to contact me at Jainish Senjaliya

Frontend login security level in sr_feuser_registration


 
Front End User Registration (sr_feuser_register): Frontend login security level must be set to “normal” or to “rsa”.

If this error message generated after install “sr_feuser_register” and then you must have to ser configuration in install tool.

Or you can set it directly in localconf.php file

and also In the localconf or in the install tool, the requested value must be entered. The OldMailAPI is set to 0.

$TYPO3_CONF_VARS ['FE'] ['login security level'] = 'normal';     
$TYPO3_CONF_VARS ['MAIL'] ['substituteOldMailAPI'] = '0 ';    

A small stumbling block had crept in: Instead of ‘FE’ was ‘BE’ is entered. The settings look indeed look almost identical.

If you have any queries, please do not hesitate to contact me at Jainish Senjaliya

Typo3 Red question marks instead of language flags OR Typo3 default language icon


You just upgraded to TYPO3 4.5.x and the backend now shows white question marks in a red circle where you used to see a language flag of the default language of your content elements?

Since v4.5 the TYPO3 backend makes heavy use of sprites. These sprites replace all the tiny icon images that up to now flooded the backend and created hundreds of HTTP requests for each single page to load. Instead all these icons are now compiled into larger images in which single icons are addressed through CSS formatting rules. So for hundreds of different icons the backend will only load one single image file!

The flag icons have been replaced by this sprite technique too. As a result you have to change your TS-Config code a bit and delete the “.gif” part in the value of the defaultLanguageFlag property.

Old TS-Config before v4.5:

mod.SHARED{
  defaultLanguageFlag = gb.gif
  defaultLanguageLabel = English
}

New TS-Config since v4.5:

mod.SHARED{
  defaultLanguageFlag = gb
  defaultLanguageLabel = English
}