danoneil

Thanks for your quick response!

That’s good info, but what confuses me is that the phpinfo shows up as 128M limits??

My host uses Heart Internet – their standard limits are 128M… it’s just for some reason WordPress is stuck at 32M.

Ok, update…

I’ve changed the default-constants.php file in wp-includes to set the memory limit to 128M. This is now showing up correctly in the TPC memory usage plugin, however there is still no progress on the wordpress update – it still freezes at downloading and the server log tells me that it’s exceeded the 32M allocated to it…

Who is your host? I’m having the same problem as this – only affects me when trying to update larger plugins or wordpress itself.

Me too – very frustrating! Some plugins work fine, but most freeze at the “downloading update” phase…

I’ve checked my server error logs and I’m getting a zend_mm_heap corrupted message when one goes wrong… also each one leaves a tmp file hanging around in the wp-content directory.

If anyone has any ideas, they would be gratefully received!

Thanks for your reply Mike, I’ll backup and do it manually – I’ll report back soon!

Works beautifully! Not sure what happened last time, maybe I uninstalled it first…

Thanks, I will do!

To update – I’ve now installed your trunk version and it’s working wonderfully now! I’m very impressed by the fact that you’ve allowed for multiple forms on one page – it focuses on the correct one!

One thing, I de-activated, deleted and then ftp’d the new version across and then activated it. Now, although the old forms were still available (I have default number set to 5), they weren’t showing up in the admin panel – presumably it’s drawn from the temp files in wp-content?

Not a major thing, as they were pretty easy to rebuild for me, but is there a config file that I removed by doing it this way – normally when I do an automatic update through wordpress all the details are still available.

Thanks again – top job!

Dan

Thanks for the swift response – I’ve tried the latest development version and fiddled with all the settings, however it still breaks the page – showing only the header and footer (nothing in between)… although firebug is not reporting 404/410 errors any more.

Thanks,

Dan

Blimey and massive thanks!

What hosting service do you use? I’ll make a note to avoid them!

It takes time to get all your pages translated – a word of warning though, I’ve had the latest version running for several weeks now (set to translate a page every 6 minutes) and I’ve got about 90 posts or so in total and over 125MB of translated pages stored in the cache. I’m only set to translate into 6 other languages too…

The advantage this plug-in has over the other one above is that you can translate your posts (not just the comments) and have google index them as a seperate post.

If there was a plug-in that did this translation, stored it in mysql and also allowed unique page addresses for each translation, then it would be perfect in my book.

Thanks Pozzad,

I’ve switched it to Prompt as you suggested and I’ll try switching back to Google in a few weeks.

I’d love it if this would work with Google on my blog, but for some reason all I ever get is “Sorry, the Google translation engine is temporarily not available. Please try again later or switch to another translation engine”

This is with the latest version now too 0.9.1.1…

I can see there are a few sites using this plug-in where the same problem is happening. You can see here on my personal development blog what is happening.

Well my host finally sussed this one out – in my .htaccess file in the root of my domain was…
AddType application/x-httpd-php .html
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www.
RewriteRule (.*) https://www.%{HTTP_HOST}/$1 [R=301,L]
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_URI} !(.*)/$
RewriteRule ^(.*)$ https://www.aquariuscoaching.co.uk/$1/ [L,R=301]

By changing the second RewriteEngine On to Off, it has stopped the odd error. Hope this helps someone in the future!

Ok, so I’ve done some digging around now and it seems as though the only problem is when the trailing slash / is not used – so https://www.aquariuscoaching.co.uk/blog/ works fine, however…

https://www.aquariuscoaching.co.uk/blog does not.