ronams
Forum Replies Created
-
I think you’ve made my point. I more than appreciate the help that anyone made and was aware that people were going ‘beyond’ (hello doodlebee!). All I’m suggesting is that there is a clear gotcha that I got hit with that seems at least possible for people to run into. A warning/ mention of this PHP memory limit in the install or upgrade notes would suffice. I’m still waiting for OneWorldHosting to explain how their own blog is WordPress and they advertise how to install WordPress in their support area, yet is going to fail as per my experience and intoxications test proved.
Only good words and thoughts for the support people here. So your suggestion to also help is what I’m doing here by suggesting a warning.
Just another thought. How is it possible to have run into this memory problem when I deactivated all the plugins on installation of 2.0.4?
I also reverted to my original 2.0.3 and it also stayed in failure mode?
It seems there is still more to this story.
I’ve been searching everywhere for how to access these apache error logs. I’ve scoured OneWorldHosting, the internet etc. and no luck. That said, anything this difficult to track down, and the fact that it seems quite possible to hit this limit should have a warning and /or method to sort out whether you’ve hit this limit. I still have no idea other than the host support group to have acknowledged this problem and have provided a solution. I was at the WordPress event in SFO a month ago and provided feedback a number of times. To get wide acceptance of WordPress, it has to get easier and easier. The Five Minute Installation was proof of that understanding. Knowing about a reasonable chance of failure due to a memory limit and having the solution be as tough to track down (including asking someone to track down their apache error log that I’ve still not been able to do, with hours of searching), is not a good thing.
I’ve still not been able to find on the support pages an explanation on how to find this elusive Apache Error Log. That would also be good. I realize that it may be different for different hosts, but if it is part of MySql ? then there must be some similarity in where /how to find it.
Again many thanks to all who tried to help.
I’m obviously thrilled to be back up. But…. Mine is small blog so far and it seems inconceivalble that I would hit a limit so quickly. Especially and unadvertized limit.
I think there would be great value in adding this caution to the installation /upgrade guide. There was no warnings or obviously no info on the web or here that made solving this even close to easy. Anything that can be done to help those following me would be appreciated. People were pretty much stumped in trying to help.Here is another posting about WordPress and PHP memory limits.
http://wordpress.org/support/topic/78315/page/2?replies=44I sent a message to my hosting firm OneWorldHosting about the problem and here is their response. They claim they have a program memory limitation of 2MB’s.
I’d love any comments. I find the answer astounding. Especially since.
1/ I have only started to use my blog and have about 20 posting and a few small file size images and .pdfs
2/ There is no mention of a program file size limit on their site (that I can find)
3/ There are no alarms/ warnings that I’m reaching some limitation
4/ They advertize on their site how to set up a WordPress BlogI have asked for a better answer. My blog file is actually 7MB, but have three blog directories, since having tried to get my blog back up. That is why they’re saying I have 18MB (it is all three directories I assume). The problem probably started at 6 MB. Is this a limit with other hosts?
{From One World Hosting}
Your program surpassed the 18meg memory limit set in php. Its possible that was adjusted downword at some point. The default is 2megs but we do make exceptions so its possible it has been raised or lowered.Your program should work now Ive boosted the limit to 38 megs.
Ref Intoxination Great site. Great material.
Ron[die error message on i.e. is Parse error: parse error, unexpected T_EXIT, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /home/ronams/h2roadmap-www/blog/wp-includes/classes.php on line 1712]
function main($query_args = ”) {
[die test point shows up in i.e.]
$this->init();
[die test point also ok here]
$this->parse_request($query_args);
[die test point also ok here]
$this->send_headers();
[die test point also ok here]
$this->query_posts();
[die test point does not show up here – cannot display page]
$this->handle_404();
[die test point does not show up – cannot display page]
$this->register_globals();
}It looks like it fails on $this->query_posts();
I assume that this is a MySql query that isn’t working.
What’s next?[die(“test point”); //this shows up on i.explorer]
require_once( dirname(__FILE__) . ‘/wp-config.php’);
[die(“test point”); //this shows up also on i.explorer]
wp();
[die(“test point”); does not show up here. Goes to cannot display] What is wp(); doing to stop this?????
gzip_compression();
[die(“test point”); does not show up here. Seems stopped at wp();]
require_once(ABSPATH . WPINC . ‘/template-loader.php’);This seems to be a positive to see where it is stopping processing. Hopefully this is useful.
RonI have to do a web conference, but thought I’d let you know that I ran a check table on the MySQL on the posts table and it came back ok.
I’ll follow up again in about an hour. If anyone has any additional ideas in the mean time please let me know.
I looked at options reading. Gzip compression was never checked, so didn’t have to change.
Thanks for keeping on this. While I like a puzzle this getting ridiculous.I can get into wp-admin and see everything except the Manage section. I can even get to that if I go to the right bottom part of the wp-admin area and look at blog stats then click on comments. From comments I click on edit comments and that takes me to edit-comments.php which allows me to see the other Manage options. I can click on any of them ok except posts. Posts goes to Page cannot be displayed. This is the same response as going to the main page from i.explorer.
I will try to turn off the Gzip disable and see what happens.
I dont’ know how to look at or what is “apache error logs”. I don’t know where any error logs are that could help.
I also don’t know how to do any gzip compression changes. Please point where / how to change.
Thanks again for the help.Tried you die(“Test Point”) in wp-blog-header.php . I’ll mark with **** where it showed up and #### where it just went to page cannot be displayed. In some cases it was in the middle of an if statement and gave a different error as some unexpected stuff. Does this help?
<?php
****
if (! isset($wp_did_header)):
if ( !file_exists( dirname(__FILE__) . ‘/wp-config.php’) ) {
if ( strstr( $_SERVER[‘PHP_SELF’], ‘wp-admin’) ) $path = ”;
****
else $path = ‘wp-admin/’;
#####
die(“There doesn’t seem to be awp-config.phpfile. I need this before we can get started. Need more help? We got it. You can create awp-config.phpfile through a web interface, but this doesn’t work for all server setups. The safest way is to manually create the file.”);I don’t think the re-direct is the problem, but I’m desparate and hope that it could be.
I have more than one url pointing at the same site.
During my 2.0.3 blog days, either http://www.strategy2execution.com/blog or http://www.h2roadmap.com/blog would go to the blog correctly and all would work. http://www.h2roadmap.com is the base url, but the name http://www.strategy2execution.com is the actual focus of the blog’s material.I continue to try both when I try to get to the blog and both fail. Today I changed the entry in the wp-admin options to http://www.h2roadmap.com/blog to ensure no potential confusion. But it hasn’t had any impact.