mo file uploading broke my 1.2
-
i actually testing a wp single 3.0 beta + bp 1.2 trunk “out of the box” install
All went fine during install, except a minor fatal error in the different incoming links widgets in WP:
Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 1245184 bytes) in /xxx/xxx/xxx/wp-includes/class-simplepie.php on line 5410.When i add the mo file, in WP or BP, the whole site shows a blank error page with:
Fatal error: Allowed memory size of 20971520 bytes exhausted (tried to allocate 77824 bytes) in /xxx/xxx/xxx//wp-admin/includes/template.php on line 153I can use a mo file in WP or BP, but not the both. And if i want to use one, i have to erase the other file.
I expected the same problem with a standard version of wp and bp. And i tried with a different mo in another language. Same errors.
20 mo php memory limit is common on a shared host, and many wp user are on shared host. Does this usual capacity compromise these user in the future, after the merge ? Do they all have to went on a dedicated 5 tera host ?
I put a ticket on wp, bp and wpmu trac… without reaction at this time.
But for now, i’m wondering if somebody using translation on his site experience the same issue ?
-
Ooooh DJPaul, i didn’t expect such an answer
!I had many out of memory issues in my weblife… it is not a fatality. Some where due to whitespace, i remember. So what here ?
The problem is i don’t use old stuff, or outdated scripts, this is a pure out of the box experience.
i can’t acces to php.ini directly or via htaccess instructions.
My host is ready to sell me a different offer, of course, but i’m not ok.
Is it normal that a translation, who works well elsewhere, takes so much memory ?
And i’m not sure my problem is so simple as “if you’re out of memory, you’re out of memory”
We had an analog problem in the past on WPMU/BP, with 64 bits servers i you remember ?
subsidiary question:
Do you know a shared hoster who gives unlimited php memory amount or more than 16 or 20 mo for php scripts ?
@erich73, na Bueb, das’is n’Gstanzel ! Net von Dir !
@DJ, did you read my post ? I expected the same problem with a standard install…
So it remains the problem of memory.
My host give the possibility to install automatically CMS’s like joomla, wordpress or wpmu, drupal etc to his customers on any of his shared offers. From the cheapest to the most expensive !
Do you really think he would do that if these tools can’t work because of an unapropriate memory appetite ?
So what is the minimal size to rent on a shared host to have an operating install with the actual and next coming version ?
And please, don’t tell me i have to go to wordpress.com
@Boone, yep, thx !
So i progressed on my site. I downgraded to wp 2.9 and asked (gently) my host to give me more memory.
I have now 25 mb for php and the install is working. But i haven’t installed plugins other than BP for the moment….
If this memory lack is “normal” or “expected”, i would preddict that as soon as WP 3.0 is avaible, 90% of all WP user actually on a shared host, and who udate, will go down. As actually no shared host offers at least 32 mb for php…
The cgi php solution with 64 mo, the new host trend apparently, is more powerfull but is always shared too, which means that i could write at my site entry: open between 3 and 4 am. The rest of the day, maybe my neighbour is trolling on emule and consume the server memory with * db queries on his overspammed fischerman forum… Wouaaaaaaaa ! Nice future…
This means also that from now on, a WP usage with BP is only intended to be on dedicated server.
If this hypotesis is right, this must be annouced to the world and should be mentionned, at least, in the readme file and on the download page.
So i discover that WP, who once was one of the fastest and litest CMS, is now entering in the heavy weight super-pro area, with ultra wide storage capacities, intense RAM consumption and specialized hi-band connection… Whouaaaaaa !
Twenty Ten, a new template but also a very surprisingly year !
- The topic ‘mo file uploading broke my 1.2’ is closed to new replies.
