mediabaron
Forum Replies Created
-
SOLVED!!!
In the Google XML Sitemaps settings is a checkbox for:
[] Add sitemap URL to the virtual robots.txt file.Uncheck that box. Once I unchecked that box I was able to manually rebuild my sitemap like before.
I left the existing robots.txt file in the root of my website which contains:
User-agent: *
Disallow: /images/
sitemap: http://www.hawaii247.com/sitemap.xmlSOLVED!!!
In the Google XML Sitemaps settings is a checkbox for:
[] Add sitemap URL to the virtual robots.txt file.Uncheck that box. Once I unchecked that box I was able to manually rebuild my sitemap like before.
I left the existing robots.txt file in the root of my website which contains:
User-agent: *
Disallow: /images/
sitemap: http://www.hawaii247.com/sitemap.xmlNope. Rolled back to 3.2.3 and it still doesn’t work for me.
Forum: Fixing WordPress
In reply to: pre formatted text changes in size for no reasonOkay, fixed it. The body copy absolutely must have the closing tag
</pre>before each<!--nextpage-->tag and a new<pre>tag after it.I’ve temporarily switched to using Google News Sitemap since the current version of Google XML Sitemaps isn’t working.
I may switch to WordPress SEO by Yoast to generate the sitemap in the near future but it’s quite a bit of set-up.
I’m having the same problem. I’m wondering if it’s related to my recent update to WP 3.1.2
Are all of you running 3.1.2?
Forum: Plugins
In reply to: [Plugin: W3 Total Cache] w3 total cache – why cdn on local server ?I’m not sure but it could be that the browser will see that the content is on a separate domain and download the file concurrently with the files on the main domain.
Forum: Fixing WordPress
In reply to: Characters have changed from ” to ’Forum: Fixing WordPress
In reply to: WordPress 2.9 dashboard html editor inserting <p> tagsI think I may have found the solution. My problem turned out to be using Safari on Mac with WordPress 2.9.
To solve the problem I believe it may have been Google Gears messing things up.
Go to Safari>Google Gears Settings
and wipe out any WordPress setting in there.Also I closed my Safari windows (for Windows users you probably have to just open a blank page). Empty your cache.
I also went into my Library subdirectories and wiped-out any cached Safari pages.
Try the Gears trick first.
Forum: Fixing WordPress
In reply to: WP 2.9 major problems with the editorI think I may have found the problem. Google Gears was messing things up. I thought it was disabled since I moved to Snow Leopard. I went ahead and deactived it in Safari, went through yet another round of emptying the cache while no windows were open, went into my Library subdirectories and wiped-out any traces of Safari cache and now it seems to be working. I’ll update if it breaks again.
Forum: Fixing WordPress
In reply to: WP 2.9 major problems with the editorDid all of those things. It now appears that the problem is with the way Safari 4.0.4 handles the editor. Firefox appears to be okay but Safari doesn’t work properly.
Deleted cached files in Safari via both the drop down menu and also digging down into Library to delete cached files. Anybody else having this issue with Safari on Mac?
I’m going to test Safari on Windows next. Google Chrome seems to work okay.
Forum: Fixing WordPress
In reply to: WordPress 2.9 dashboard html editor inserting <p> tagsSomeone in the WooThemes.com forum said WordPress upgraded TinyMCE which is the editor in WP 2.9 and that may be the problem.
I’m having the same problem. Switching between Visual and HTML messes things up and leaves difficult to edit HTML text.
One partial work-around is to be in Visual mode, copy the text you want, then go to HTML mode and paste it in over where you want it. This will clean things up a little.
Need 2.9.1 to be pushed out with the editor fix.
Forum: Fixing WordPress
In reply to: Double upload dialog boxes popping upGood call. I deactivated plugins and found the culprit turned out to be the PicApp plugin. I’ve posted a bug report on their plugin page.
All is well again.
Mahalo Shane!
Forum: Fixing WordPress
In reply to: How do I show a custom field meta without the key’s name?I had gone to that page, that’s how I got the original <?php the_meta(); ?> code.
After some digging and trial and error I was able to answer my own question (notice I had said I’m not a php whiz). If someone thinks there’s a better way let me know. All I know now is that this solution works so far.
I used this code in my theme template and it seems to be okay.
<?php $key=”map”; echo get_post_meta($post->ID, $key, true); ?>Forum: Fixing WordPress
In reply to: WP using 3x allocated memory on VPS?I had (and am still somewhat having) the same problem as you. I was running a shared hosting account with DreamHost with several WP blogs and got the dreaded 500 error so they said I should go with VPS, I did and during the first free trial week (you can set memory to anything you want the first week so you can figure out how much you need) everything was going well with my memory usage below 150M.
Then all hell broke loose with runaway memory useage. The memory use went over 4,000M compared to 150M the previous five days. Disaster and my VPS came to a crunching halt. I had to go in via SSH (using my terminal.app in Mac OSX) to see in real-time memory usage.
I shut down the WP sites that weren’t really being used, I disabled all plugins and did this to get my main site http://www.hawaii247.org back up and running. Strangely even though I had enough memory I couldn’t get the site going again. Finally it magically started working again, I could get into wp-adim (I set-up my front page as a static html so it wouldn’t tax the server).
I slowly added necessary plugins to get the site back to where it was before, I disabled other plugins that might cause the load. DH kept saying it was wp-cron doing much of the memory load along with the fetching of my tag files.
I’m back up and running again but it was terrible, on the weekend so tech support wasn’t very fast (at least not in internet terms). My site was down for almost 24 hours.
I’m doing some other things to alleviate server load which may or may not work.
* I turned on php cache (xcache) and have mod_php version 5.x running
* I incorporated a Google AdSense search onto the site instead of using the built-in search which would generate all the posts in the results.
* Set up the plugin HyperCache to cache pages
and a number of other things.I can now see that having tags on the site hammers the memory usage when people hit the tag to generate results. I’m considering just stopping the use of tags.
In the DreamHost VPS info it says just having the server running uses up about 100M of memory so you’ll have to figure on your site using above and beyond that. Their shared hosting plans have a cap of 90M per account.
Did you ever get your memory problem resolved?