Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter jamesfiv

    (@jamesfiv)

    I fixed the width like you said, thaKing, and found that the text jumped up to the left of the sidebar in Firefox, it was still on the right of it in IE. I then changed the sidebar float from left to right, and adjusted the margins a bit and it seems to work well enough. The look in Firefox isn’t ideal, it still looks better in IE, but at least the sidebar and content are next to each other.

    I think that whooami’s suggestion was right, too. The original suBLUEmenal probably has the sidebar on the right, and just couldn’t take a change to the left. I still want it on the left sometime, but am happy that the site looks halfway decent in Firefox now.

    I was using the large left margin of the content to force it to the right and the sidebar up to the left, but it just wasn’t the right solution for Firefox no matter what I tried.

    I’ll consider the case resolved for now. Thank you thaKing and whooami for your quick and patient support! ??

    Thread Starter jamesfiv

    (@jamesfiv)

    I may take a look at the original php for suBLUemenal tomorrow.

    Thread Starter jamesfiv

    (@jamesfiv)

    Whooami wrote: “You do realize that your sidebar is supposed to be on the left, dont you? Atleast thats what I see when I use firefox’s web dev extension.”

    When I look at the link you gave, I see that the sideboxes are on the left, but that the sidebar and content are ordered up above, below the header image. I still don’t have the foggiest why that is happening.

    Thread Starter jamesfiv

    (@jamesfiv)

    Instead of messing with the css for titles, I just shortened the title. I found one post that was too wide because of code, so I changed the size. I narrowed the content.

    Unfortunately the sidebar is too far to the right in Firefox, its position completely unchanged.

    Thread Starter jamesfiv

    (@jamesfiv)

    I see that the title did mess things up. I’ll have to read up on how to fix that in CSS.

    The sidebar is on the left in IE – which I usually use. I only recently started using Firefox and noticed the huge problems.

    If you look at the front page of the blog in IE, the title of that post is cut off, but the sidebar is still where it should be. But I’ll get to the CSS now. Thanks.

    Thread Starter jamesfiv

    (@jamesfiv)

    I DO feel good about myself today! I fixed all errors in the CSS (did XHTML before) – and even pasted my trophy W3C buttons into the sidebar. Took a quick look at the warnings, but all is ok, no need to change them.

    But the sidebar is still off to the right in Firefox. Confused. I still don’t get it.

    Thread Starter jamesfiv

    (@jamesfiv)

    Went to your link, thaKing. Oh boy, it looks like I have a lot of work to do… I’ll validate the CSS first and then ask again if the problem persists. I’ll try not to forget to close this thread if it works, if not then I’ll get back here within a few days I hope. Thanks for the tip!

    Thread Starter jamesfiv

    (@jamesfiv)

    I already validated the blog with W3C before I started the thread, the blog checked out ok. Do you mean the CSS by itself?

    Forum: Plugins
    In reply to: Tutorial Portal

    edited by myself: my answer was in the wrong thread.

    Thread Starter jamesfiv

    (@jamesfiv)

    A correction here, the error is only when editing pages not editing posts.

    Would an upgrade to 2.0.1 solve the problem? Was that one of the bugs in version 2.0?

    Thread Starter jamesfiv

    (@jamesfiv)

    Thanks for the tips. I finally found out that there are two places to turn off the rich text editor. I made sure both options were inactive and it finally worked. At least that problem is solved…

    Thanks! ??

    There is also a problem with RSS feed links. Google’s custom feed generator uses an ampersand as part of the code which, in the html editor generates something like codeampersandamp;amp;amp;amp; . Sometimes the incoming feeds so generated work and sometimes they don’t.

    I have a somewhat different problem.

    I wanted to use a plugin called Category Order from:
    https://www.buzolich.com/techtips/category-order/.

    The typical bug doesn’t let one see the categories if Permalinks are enabled. I went to the Options page, but that is not an option.

    I tried changing the preferences for permalinks, selected the custom option, and changed the .htaccess file with the given script.

    That made all links in the blog that were connected to the blog itself inactive. Even the comments page gave an error.

    Ok, I have set all things back to normal and permalinks back to default, no problems there anymore. But I still have not figured out how to disable permalinks.

    The above suggestions of eliminating the .htaccess file are not an option, because it is needed for other functions – the custom 404 page for example.

    Any other options?

    Thread Starter jamesfiv

    (@jamesfiv)

    Ok, this looks stupid, but here goes. I managed to solve the problem somewhat.

    I went to my host and found out that the version I was using was 1.5 – that is what they offer as their current version of WordPress, I had installed that just within two weeks from today. Why they are not offering 2.0 is beyond me.

    I decided that an upgrade may solve the problem, because the files I had used for correction were from version 2.0 and therefore not compatible, possibly causing the error message.

    I did the upgrade according to the directions here at WordPress and whaddayaknow! It worked! The plugins still don’t do what I want them to, but the category default menu looks better than it did before, at least things look normal again.

    A decent plugin (or code change in next upgrade) for the file categories would be nice too, though. Order by categories set by the site owner, not by ID or alphabetically unless specified. Full flexibility.

    If there is any other way to solve the problem listed in the OP I am sure that others would like to know. I have seen critique about WordPress 2.0, there may be some that would rather not upgrade.

Viewing 14 replies - 1 through 14 (of 14 total)