Tuxmind in creams?

The fans readers of tumind will sure have seen, if one may use the expression, that this afternoon the situated era unattainable. The effect has been the classic, hateful “internal error serveur… “, the cause a banal problem of memory allocation. I do not want certainly to make the sapientone, I write this post for giving a hand to how many were found in future of forehead to this situation. Stamani I have upgradato (ugly in Italian, but since we are in times from inglecismi…, also this then) to wordpress 2.3.2 and all it has seemed to proceed smooth. I re-enter in house to the 19:30 and “puff”, Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allotted…).
After a ten of minuteren of careful reflection it comes to me in mind to have had to that to make with a thing of the sort months ago and to have resolved inserting in the rows wp-config.php the code line ini_set (” memory_limit”, “24M”);.
All resolving!
Draft in short of a limitation introduced in the rows of configuration of php (php.ini) on the serveur of Aruba (mine I torture myself of web hosting). Clearly Aruba does not allow the customer to change the formulations of php.ini, however every script php has the possibility to modify these options for if same, enough to insert the code of which over.
To such purpose the obligation runs me ringraziare Polci Mark that has resolved this problem before me and from which obviously I have taken cue. Here the link of its post.

It marks it near: