jcwinnie

“Just saying,” for an installation on a remote host, it would seem ill-advised to recommend adding the parameter to .htaccess

Talked with remote host tech support.

I had to change the parameter in the php.ini in /public_html, then copy php.ini to every directory AND subdirectory that has php files where I wanted the change to take effect. I also altered the memory parameter of the wp-config.php file.

The error message disappeared after all of that was done. I set all to 96MB.

O.K. After about 2 hrs. back to about 97% normal.

The cPanel interface tells me it is copying the files over, though there are problems due to incomplete copying.

Nope, rebuilding the database files failed to solve all the problems. For example, the browser was trying to open or save comment.php when I wanted to save a modified comment. So I had to re-install. The server is slow in copying the files, so it is difficult to see how much the plug-ins and widgets have been wiped out.

Google Webmaster Tools
Error: The last attempt at downloading the Sitemap failed. The details below are representative of the last successful download. Resubmit?

URLs in Sitemap Submitted Downloaded
Sitemap Total: 3,132, Indexed: 3,132

Oct 12, 2009 – Error Oct 14, 2009

Sitemap errors and warnings
Line Status Details
Errors –
We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit.
Problem detected on: Oct 14, 2009

Adding the parameter resulted in a 500 Internal Server Error.

Removal of the offending line, resulted in a reactivated site, yet a blank screen.

Repair of all database files resulted in a working site again.

Somewhat related, I have earlier version and unable to automatically upgrade it.

Error message: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 311529 bytes) in /home/jcwinnie/public_html/wordpress/wp-includes/http.php on line 1331

This occurs using WP 2.8-beta-2

This may or may not be related. I have deactivated this plug-in in 2.7 becuase it caused a Fatal Error each time I posted / edited an entry or comment.

It began to happen when I switched over to PHP5. If I returned the setting on my remote host to PHP4, then the problem was eliminated. I have chosen to deactivate the plugin because of the improvement in performance by using PHP5, plus PHP4 is being deprecated.

My thanks for the above suggestion from Michael H.

I had the same problem with 2.7. Followed his directions using phpAdmin on bluehost to correct the problem.

Although it occurred on line 1044, it was same error message for wp-includes/widgets.php. The error occurred after I tried to create a second text box in the second sidebar on a Sandpress themed blog. The text box included an inline statement.

I wanted to add a Google Blog Bar, but managed to bork my blog instead. Will wait for some clever widget maker, eh?

Have you tried waiting 7 minutes?

Can you say molasses, uphill, January?

Edit is the slowest, posting a comment or adding a tag also can take an inordinate amount of time.

Thanks bunches

(bump)

expletitive deleted — It would appear to be a plugin that is gumming up the works.

e.g.

Error!
Connection closed by remote server

You tried to access the address https://jcwinnie.biz/wordpress/wp-comments-post.php, which is currently unavailable. Please make sure that the Web address (URL) is correctly spelled and punctuated, then try reloading the page.