mookus
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Comments Direct Links – Using ‘href’ instead of ‘name’Okay – I finally have comments in a format I find aesthetically pleasing, and behaving as expected link-wise.
I had to make changes to my theme’s “comments.php” file -and- to the CSS file, since they weren’t using the same header tags.
Thanks for all the help folks, I definitely would not have figured out how to fix this without ya. 🙂
Forum: Fixing WordPress
In reply to: Comments Direct Links – Using ‘href’ instead of ‘name’OH – I see what you were saying now Moshu, thanks for clarifying.
I honestly was not following, hope you didn’t take it personally. 🙂
Anyway, like I said thanks for pointing that out – I swapped out the ‘comments.php’ file from my current theme with the one from WordPress default and the comment links work!
It breaks the formatting though, so now I need to compare the two ‘comments.php’ files and see how to get the formatting of my current one to work with the links from the default one … but at least now I know for sure I’m looking in the right spot.
Yay!
Forum: Fixing WordPress
In reply to: Comments Direct Links – Using ‘href’ instead of ‘name’Thanks for all the replies folks, still working on it.
Moshu I’m not sure I’m understanding what you mean by “there is nothing in the CSS files when it comes about links.” The CSS files for both my current theme, Blue Horizon (which my current theme was modded from), and the WordPress Default theme have many, many entries for comments and/or links.
As mentioned, my current theme is a three-column variation of Blue Horizon – I set my theme back to the original Blue Horizon and am having the same problem.
So now I’m trying to discover what is different between the CSS files of the WordPress Default (based on Kubrick according to its notes), which works, and those of Blue Horizon/Blue Horizon Variant, which do not.
Forum: Fixing WordPress
In reply to: Comments Direct Links – Using ‘href’ instead of ‘name’A couple of things I’ve noted after more fiddling:
1) The link to …
“http://www.mysite.com/post-permalink/#comments”
… works just fine, but links to …
“http://www.mysite.com/post-permalink/#comment-1234”
… still do not.
2) When viewing the blog with the default theme, everything works as intended.
I’m now concentrating my efforts on the CSS file of the theme I’m using (though I’m not really sure what I’m looking for, at least I think I’m looking in the right place!)
Forum: Fixing WordPress
In reply to: Comments Direct Links – Using ‘href’ instead of ‘name’Mmm, unfortunately I only have ‘Webalyzer’ stats access from my server host, not the actual raw logs … I don’t think I have any way to check the server logs down to such a fine detail. 🙁
Forum: Fixing WordPress
In reply to: Comments Direct Links – Using ‘href’ instead of ‘name’Hmm, no love on the ‘Update Permalink Structure’ front.
Maybe something odd in the .htaccess?
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>It’s driving me nuts. 🙂
Forum: Fixing WordPress
In reply to: Change The Default Page (for 404?)Oooh, Samboll, that does look really cool! 🙂 I’ll be using that for my WordPress stuff for sure. But my site has a lot of content outside the blog, i.e., lots and lots of pages that aren’t ‘WordPress’ pages, they’re just good old fashioned html / php files. The WordPress blog is a small piece of the whole, but I feel like it’s hijacking my htaccess lol. It makes sense for a ‘404’ from ‘mysite.com/blog/’ to default to the WP index, but outside the blog directory I feel like a domain with WP installed should still be able to have it’s own ‘404’ system.
I’m still on the mission 😀
Forum: Fixing WordPress
In reply to: Change The Default Page (for 404?)Rats, spoke too soon, what I thought had fixed it merely broke something else.
After poring over lots and lots of websites and forums, I can finally at least understand the current WordPress .htaccess:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>Basically if something is requested that isn’t a file or directory, the request is sent to ‘/blog/index.php’ instead. But I don’t want ‘404’ requests going to the blog index page, I want it going to the main site page … if I change ‘/blog/index.php’ to just ‘/index.php’ this solves the ‘404’ page issue, but then all of my WordPress permalinks fail to resolve (because instead of going to ‘blog/this-is-post’, they go to simply ‘/this-is-post’, which doesn’t exist).
Anyone follow all that enough to lend a hand? Does anyone know if it’s at least possible, so I’m not just banging my head for nothing? 🙂
Forum: Fixing WordPress
In reply to: Change The Default Page (for 404?)Thanks Samboll! All is well now 🙂
Forum: Fixing WordPress
In reply to: RSS Feed ‘Stuck’ on Summary Only?Heya guys, thanks for the quick replies – seems like this might only be a problem for older feed readers? I downloaded and looked at my feed (http://www.themook.net/blog/wp-rss2.php) using SharpReader instead of Abilon (FeedDemon is no longer free :D) and the posts appeared as full text.
It’d be nice to ‘fix’ the feed so it would show correctly on older readers too, but I can live with this. Reluctantly (OCD anyone?) 😀