Forum Replies Created

Viewing 15 replies - 1 through 15 (of 19 total)
  • Thread Starter djhomeless

    (@djhomeless)

    Ok, sorry for the duplicate thread.

    Thread Starter djhomeless

    (@djhomeless)

    Hi Moshu,
    You are right, sorry I didnt see the thread.

    However, the question remains, could this be brought to the developers as an instance where the logic could be changed? I don’t believe the site should not load simply because the siteurl does not match the current location.

    Could it at least be decoupled so users who are moving systems or locations could have a way of checking prior to making the switch?

    I’m running into this problem too. I’ve gone through both guides recommeneded in the Codex, both have failed.

    Plugin’s were disabled.
    DB was backed up.
    wp-content was copied over.
    .htaccess was copied
    wp-images was copied
    DB was restored in new table

    yada yada.

    Any ideas? I’ve been able to install wordpress 2.0 as a standalone new blog so i dont think there are conflicts there.

    Thanks,

    Geoffrey

    Thread Starter djhomeless

    (@djhomeless)

    That increases the size of the div container around the quicktags and the textarea. It doesn’t increase the size of the textarea.

    It would be nice to know why the quicktags seem to have some dependency on the textarea using a specific class….?

    Thread Starter djhomeless

    (@djhomeless)

    *sigh*
    This thread is not going anywhere. I will make one last valiant attempt to get my point across. ??

    Whenever a textarea is used in the admin pages to input/edit content, the code is this:

    <div><textarea rows="<?php echo $rows; ?>" cols="10" name="content" tabindex="5" id="content"><?php echo $content ?></textarea></div>

    Note the class id of “content”.

    In wp-admin.css, there is just the following simple CSS entro for content:

    #content, #excerpt {
    margin-left: 1%;
    width: 130%;
    }

    Changing this CSS entry to increase the text size has no affect.

    My theme’s CSS, which is called site-wide from the header, ALSO has an entry called “content”. It is as follows:


    #content {
    width:510px;
    float:left;
    padding:5px;
    margin:0;
    overflow:hidden;
    display:inline;
    }

    If I change this entry, it WILL increase the textarea in the admin pages. However, it ALSO changes how the content is styled on the site, despite the fact that the content is styled inside a differently named class!

    Also, if I create a new class to use on the textarea in the admin pages, it WILL work (ie it increases the textbox size). HOWEVER, the quicktags fail to function using this new class.

    Sorry for being so literal, and taking so much space. I’m really struggling on how to solve what should be a fairly straightforward change.

    thanks

    Thread Starter djhomeless

    (@djhomeless)

    Sadly I tried that.

    Whenever I created a new class for the textarea, the form would indeed change. However, for whatever reason the quicktags stopped working!

    Does anyone know why that would happen?

    Thread Starter djhomeless

    (@djhomeless)

    Your working on the sabbath? You heathen! ??

    I mentioned it earlier in the thread, but my theme does call the site stylesheet in the admin pages.

    As its done in the header, I’m not sure how to disable it just in the admin pages….

    Thread Starter djhomeless

    (@djhomeless)

    Its the other way around.

    I’m making the changes in the site stylesheet, not the admin one. I mentioned this above, but for whatever reason when I made the change in the admin stylesheet (for the textarea), it didn’t change.

    Both the admin stylesheet and the site stylesheet have a class called “content”.

    Thread Starter djhomeless

    (@djhomeless)

    Its the other way around.

    I’m making the changes in the site stylesheet, not the admin one. I mentioned this above, but for whatever reason when I made the change in the admin stylesheet (for the textarea), it didn’t change.

    Both the admin stylesheet and the site stylesheet have a class called “content”.

    Thread Starter djhomeless

    (@djhomeless)

    I know, I don’t get it myself, hence the reason for this post.

    I changed the class for the textarea, in the admin pages, and the change was reflected. However, it also changed the way the content was styled on the site!

    Then I created a new class, and changed the textarea to reference it. The textarea did change, however the quicktags stopped working.

    Its all very weird….

    Geoffrey

    Thread Starter djhomeless

    (@djhomeless)

    I do get it. The title of the post says it all, I’m looking to modify the textarea you use to input your content.

    All I’m looking to do is change the width of the textarea, which I mention above.

    I am confused, because not only is the change reflected in the textarea (ie the form), which is what I wanted, but it is also shows up on the website in terms of how the content is displayed, which is what I don’t want.

    Both stylesheets are referenced in the admin screen, and both stylesheets contain a class called “content”. Strangely enough, if I change the content class in the admin css, it does nothing.

    The content is displayed on the site inside a div that references a class called “post-content”. So again, I am confused why chaning a differently named class would have any affect.

    Thread Starter djhomeless

    (@djhomeless)

    Ok, so I’m not doing a good job explaining myself.

    The textarea, refers to the form you use to create and edit content.

    Whenever I talk about the ‘front end’, I refer to how the content appears on the site.

    The content as it appears in the site, is inside a div with a class of “content-post”.

    The textarea where you input the content, is in a class called “content”.

    As I’m self taught on CSS, I’m confused why changing the atrributes for the “content” style, which should only affect the textarea of the form, also impact how the content styles in the “content-post” class.

    Does that make sense?

    Geoffrey

    Thread Starter djhomeless

    (@djhomeless)

    Slight correction here, though I’m still confused.

    Looking through my theme, which is Connections, the content is actually styled using the post-content class.

    However, when I modified the content class, the modifications were reflected on the front end website as well as on the form pages. But if the web display is referencing the post-content class, then why did it pick it up?

    The only thing I can see that might cause the this is that the two classes are referenced in the stylesheet differently. I don’t really know what it means, but here are the two references:


    #content {
    width:510px;
    float:left;
    padding:5px;
    margin:0;
    overflow:hidden;
    display:inline;
    }

    .post-content {
    padding:10px 0;
    margin:3px 0;
    border-top:#BBC4A3 1px solid;
    font-family: Georgia, Verdana, Arial, serif;
    font-size:12px;
    }

    Does the hash key act as some sort of wildcard? Like any class that contains the word ‘content’ will also utilise these attributes??

    Thanks All,

    Geoffrey

    djhomeless

    (@djhomeless)

    What about changing the width? I’ve tried modifying the stylesheet and even changing the code that calls the textarea (increasing the cols up to 60).

    Anyone know? Its driving me up the wall!

    thanks,

    Geoffrey

    Thread Starter djhomeless

    (@djhomeless)

    Big thanks to Manzabar! I’ve survived my ‘Slashdotting’ after tallying up just under 30,000 unique visitors in under 24 hours. The bulk of that came after I installed WP-Cache 8 hours into the hit, so it more than proved that it can handle a load of traffic.

    Technically, my site is still running slow, but considering its hosted on my DSL line, on a server in my kitchen, its pretty incredible its running at all considering the traffic that is still hitting it.

    Question: Just being curious, how fast is the site loading where you guys are? I’m in the UK.

Viewing 15 replies - 1 through 15 (of 19 total)