soundtrip

Actually you can use two blogs with one theme no problem if you are on Linux. Simply create a softlink to the theme you are wanting to share. This is actually a no brainer unless the specific theme has been modified to require something specific to the blog installation it is installed under.

I have done this successfully many times. I am referring to Themes only; and yes, the new blog should be intalled in a different folder.

Of course this implies that you should probably make the theme files read only unless the intention is to allow modifactions on one theme span to the other blog. On the other hand, it is often easier to maintain two seperate copies.

For an example of this in action see:

https://www.soundtrip.com/
https://hband.soundtrip.com/

The only file not shared is the header because I wanted to do something funky with the flash player. Otherwise the files are shared across both blogs, one theme, one theme installation, no problem, very convenient.

Trip

That may be all fine but the problem is not with K2. I have the same problem after upgrading to wp 2.0. with multiple themes.

There is something wrong with using the tag as follows:
<a href="<?php trackback_url(TRUE); ?>">Trackback URL</a>

It Returns : https://www.myurl.com/wp-trackback.php?p=1114

Clicking on that will yield:

The document has moved here. Where “here” links to :

https://www.myurl.com/?p=1114

This clearly is a problem in wp 2.0. I checked the codex and the themes I am using have it correct. Perhaps there is something wrong with permalinks.

Hi,

Your div tags look out of line. You can check your page againt the xhtml referrer. https://validator.w3.org/

Go to the very bottom and you can see that your divs look messed up.

Trip

Look at SoundTrip. It is a three column feed that might be of interest. https://www.soundtrip.com/

Hi. It looks to me like you are on Yahoo. They have modified the wp 2.0 files and/or possibly have a 2.0 pre-release. In any event this is no problem.

Set the disable property right after the following lines as shown below.

if ( file_exists(ABSPATH . 'wp-content/object-cache.php') )
require (ABSPATH . 'wp-content/object-cache.php');
else
require (ABSPATH . WPINC . '/cache.php');

// For now, disable persistent caching by default. To enable, comment out
// the following line.
define('DISABLE_CACHE', true);

You can use the Yahoo control panel to delete the contents of the cache if you so desire.

Trip

Much better!! I make a habit of checking the referrers to see if they can spot the missing tags. It’s so easy to get these out of whack.

Glad to help.

Trip
https://www.soundtrip.com/

It still shows 430 on your site so I am assuming you changed it back. The next thing I would look for is a missing image or something that is throwing the site off.

See Line 124

Column 79

The element type “br” must be terminated by the matching end-tag “</br>”. This could be the biggie.

You may also want to check the site against a referrer :
https://validator.w3.org/

There are quite a few validation errors that may lead you to the problem.

#content {
background: transparent;
border: none;
color: #FFFFFF;
margin: 0;
padding: 0 30px 30px 67px;
text-align: left;
width: 430px;
}

Trip

Quick fix, probably shorten the width in your content id to be somewhere around 400px. I would also scale back on the padding until the columns lined back up again. Make sure to check in both IE and firefox as they render differently.

Trip

Hi. I have had some requests from a few people on this issue. Here is my synopsis and fix. Everyone I spoke to has had success with this solution.

The WordPress 2.0 cache has a bug and or issue in it that adversely affects some users. Perhaps it has something to do with the use of redirects by some web hosts or virtual domains.

The category problem is fixed by disabling the WP 2.0 Cache and clearing out its contents. Disabling the cache will improve your life and most people probably won’t see any difference on thier blog for the most part. At least in the initial 2.0 release.

I believe that that the WP cache should not apply to the admin side of the back end in any event. This is not to criticize the developers of WP, merely to point out a caching strategy that I think may need to be revisited.

You will need access to the WordPress installation to disable the cache. There is a file in the root called wp-settings.php. Search for the word disable and uncomment the define line.

// define(‘DISABLE_CACHE’, true);

So that it looks like the following:

define(‘DISABLE_CACHE’, true);

You should also delete the contents of the cache before re-enabling the cache if you ever feel the need to do that. There is a directory called wp-content/cache. All files and subdirectories should be removed from this directory as well as this holds the erroneous data. Some people have been chmod’ing the directory to prevent writes but that is unnecessary. Removing the commented out directive will fix the problem just fine.

Please backup your blog and files before you delete the files. better safe than sorry. I have seen no ill affect by removing the files from this directory or disabling the cache; life will be better!

Trip

There is a problem in 2.0 if you change the permalinks struture. It generates the file you have listed above. I enabled permalinks and all of a sudden my podcasts broke because the rewrite rule broke access to my mp3’s, even if you tried to navigae to them directly.

The fix for me was to return permalinks to the default and delete the .htaccess file as listed above (rename it to be safe). It could be that this only broke old posts when permalinks were different but I am not sure. Links to my .mp3 files would actually return posts as opposed to the file, ouch!

I haven’t had a chance to dig into this yet but that is the quick fix for me; not sure about the 1.5 .htaccess file.

– Trip

Ah, The site looks good. 403 is forbidden. Strange. A short post shouldn’t work either in that case unless there is a certain element that is contained in the post that is inaccessible.

I suspect a CSS problem on your site because both IE and FF don’t work.

This would be easily confirmed by temporarily switching out themes and trying a longer post. These are definately confusing.

I see a lot of xhtml errors on your site which may indicate malformed HTML. This can cause huge problems and generally stems from poorly structured CSS or improper use of the tags. This is not a major deal but it could be that some element in the long post may be pulling in a bad CSS definition.

Go to : https://validator.w3.org/

and enter in https://www.divaknitting.com/blog/ for validation to see the errors.

The site looks great however.

Note that 2.0 might break some themes.

Trip

You should uncomment the define line.

// For now, disable persistent caching by default. To enable, comment out
// the following line.
define(‘DISABLE_CACHE’, true);

Deleting the contents of the cache will not work unless you actually trun it off. ls -a might show hidden files.

The comment in the wp-settings file is misleading. – trip

Hmm, Did you add any quick tags?

What plug-ins are you using? Try disabling any plug-ins one at a time and seeing if any of them cause the problem. WP 2.0 should load flawlessly with IE and/or firefox. – Trip

Hi TS,

The editor in WP 2.0 generates </br> and tags whenever it detects a linefeed and/or combination of linefeeds. I was not aware that this was happening and that is what was throwing my HTML output off.

I’ve learned that it is important to look at the generated code, or minimally check posts against an xhtml compliance checker to make sure that the code stays in speck.

Thanks for your help. – Trip