ek_wals

Forum Replies Created

Viewing 15 replies - 1 through 15 (of 39 total)
  • Thread Starter ek_wals

    (@ek_wals)

    More info:
    The browser is being sent code that does not appear in in header.php

    Header.php has, in part,

    <noscript>
    <link rel=”stylesheet” href=”<?php bloginfo(‘template_url’); ?>/assets/stylesheets/unsemantic-grid-mobile.css” />
    </noscript>
    <script type=”text/javascript”>
    var ADAPT_CONFIG = {path: ‘<?php bloginfo(‘template_url’); ?>/assets/stylesheets/’,

    The code sent to the browser has a bunch of cruft inserted after the ‘</noscript>’ line. The cruft is a single line, and includes an extra ‘</head><body>’ and one character that is not understood by my browser or editors.

    Thread Starter ek_wals

    (@ek_wals)

    And Apache 2.2.21

    Thread Starter ek_wals

    (@ek_wals)

    The local site uses WAMP 2.2, PHP 5.2.9-2, and SQL 5.5.16, which has all worked with no problems except for a reluctance to change PHP versions.

    Thread Starter ek_wals

    (@ek_wals)

    The filter is in the plugin. The plugin hooks it into the_content using add_filter() (is that what you mean?)

    The MU network has 2 users. Both act the same when they have the plugin enabled. It still fails in one site if the other has the plugin deactivated.

    I don’t know the difference between ‘active on all sites’ and ‘active in MU-plugins’
    Under wp-admin/network, the plugin is not network activated and it fails identically if I ‘network activate’ it.

    Thread Starter ek_wals

    (@ek_wals)

    Another wasted day and time to just work around it.

    I could find nothing in the configuration of my local PHP that would help.

    It fails only when ALL the following are true:
    1) a specific theme is used (The Erudite) AND
    2) its on multiuser not an individual site AND
    3) The MU is running on localhost

    If all three are true, it fails in multiple ways (more tag fails, excerpts are printed twice and not truncated, tinyMCE visual display is inconsistant, dropcaps missing from post)

    Thats a specific enough case that it could easily be a bug in WP itself and/or bad behavior in WAMP or the theme or …

    Way beyond my skills!

    Thread Starter ek_wals

    (@ek_wals)

    Sure enough, it seems to work on the live site.
    I’d be interested in any theories as to why WordPress should work differently on localhost.
    Are there any more gotchas waiting to make my life miserable??

    Thread Starter ek_wals

    (@ek_wals)

    No I haven’t, but it sounds like a good idea. Shouldn’t take long…

    Forum: Fixing WordPress
    In reply to: Upgrading to 2.9.1
    Thread Starter ek_wals

    (@ek_wals)

    Yeah but then what? what pitfalls await? What stupid thing will I do to mess things up? What little thing will I forget that leads me on a wild goose chase? How can it help but provide a dozen more places for me to screw up?

    After all, this goose chase began with the desire to upgrade WP. What could be simpler than pressing the upgrade button? On a newly installed WP instance. 3 hrs later and I’m preparing to reinstall my site from scratch just to get it to work without the upgrade.

    The bottom line is that the WP automatic install can’t work until the nameservers are pointed at my site – at which point I won’t dare to even try on the live site.

    Sorry about the rant – this stuff seems trivial for everyone but me.
    Thanks for trying to help (actually, you did)

    Forum: Fixing WordPress
    In reply to: Upgrading to 2.9.1
    Thread Starter ek_wals

    (@ek_wals)

    Perish the thought! I’m already lost in the woods. I don’t need to get sidetracked into getting a local server to work, and then figure out how to incorporate it into my work flow.
    I’ll just assume that 2.8.6 is good enough for now and some time into the future and live with it.

    Just got to the point of seeing that to get Akismet working I had to enter my WordPress API key. After getting new passwords from WP etc, I discover what it really meant was “Akismet API key (which I had already) Grr!

    Thanks for your help. A negative result but a result nontheless.
    At least I know this one problem is not just my stupidity!

    Forum: Fixing WordPress
    In reply to: Upgrading to 2.9.1
    Thread Starter ek_wals

    (@ek_wals)

    My ftp client seems to have the same problem but give a better error message “invalid host name specified” Apparently I just can’t FTP to an inactive site. Fortunately the inactive site can still upload.

    I think I’ll give up and assume that WP cannot be updated except on a live site (scary), and stick with 2.8.6 until Fantastico starts installing a newer one.

    Forum: Fixing WordPress
    In reply to: Upgrading to 2.9.1
    Thread Starter ek_wals

    (@ek_wals)

    Yes. I have to because ‘mydomain.com’ points at the site on dreamhost.

    I put the FTP_HOST, FTP_PASS and FTP_USER defines into wp-config.php
    Upgrade now shows those values already entered in shaded boxes but the same message
    Error: There was an error connecting to the server, Please verify the settings are correct.

    The host box shows the host ending with “…:2” instead of ‘..:21’ Is there an actual length limit on the hostname, or just a display issue?

    Tried without the ‘:21’ same result
    Created a new ftp user with simple password — same result.

    Forum: Fixing WordPress
    In reply to: Upgrading to 2.9.1
    Thread Starter ek_wals

    (@ek_wals)

    The site is currently on Dreamhost. I want to move it to ASO(asmallorange.com) and to upgrade it and change the theme. I do not want to do the upgrade to the live site. I have installed WP 2.8.6 at ASO, and want to upgrade it to 2.9.1 before I attempt to overlay the actual site and import the sql.

    Forum: Fixing WordPress
    In reply to: Upgrading to 2.9.1
    Thread Starter ek_wals

    (@ek_wals)

    Nope. Perhaps it doesn’t like the form
    https://ftp.myhost.com/~user
    Forced on me because the (working) site is at another host.
    Can you only upgrade a live site??
    And is it true that you can’t use anonymous?

    Forum: Fixing WordPress
    In reply to: 500 errors
    Thread Starter ek_wals

    (@ek_wals)

    I realize the home htaccess is commented — The point is that I didn’t do it. All those comments are done by the server, (and dated to a period when I never even accessed the site!)

    I tried commenting the maxredirects (and increaing it to 150) with no effect.

    That 500 error is really being generated by the server, and really claims that the server is misconfigured. Something in my site may be exposing that misconfiguration, but it really seems to be BlueHost’s problem. I was able to find one other thread that mentioned 500 errors, and it also mentioned BlueHost. Also identical code works on 42 out of 50 states.
    My guess is that some timeout(‘s) in Apache are set wrong, and the rather slow PHP code (dealing with over a thousand categories) is tripping it.

    Conclusion – BlueHost will fix it on monday or I will move the site to another host. (ugh!)

    Forum: Fixing WordPress
    In reply to: 500 errors
    Thread Starter ek_wals

    (@ek_wals)

    The .htaccess in public_html is:

    RewriteOptions MaxRedirects=50
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress

    There is also a .htaccess in the parent directory ( home)

    # File modified on Thu Aug 3 16:09:48 2006 by server
    # <deactivated is not a supported htaccess directive
    # is not a supported htaccess directive
    # </deactivated>
    # File modified on Thu Jul 27 16:41:12 2006 by server
    # <deactivated is not a supported htaccess directive
    # is not a supported htaccess directive
    # </deactivated>
    # File modified on Thu Jul 27 16:29:23 2006 by server
    # <deactivated is not a supported htaccess directive
    # is not a supported htaccess directive
    # </deactivated>
    # File modified on Fri Jul 14 16:04:09 2006 by server
    # <deactivated is not a supported htaccess directive
    # is not a supported htaccess directive
    # </deactivated>
    # File modified on Fri Jul 14 04:37:07 2006 by server
    # <deactivated is not a supported htaccess directive
    # is not a supported htaccess directive
    # </deactivated>
    # File modified on Mon Jul 10 21:50:31 2006 by server
    # <deactivated is not a supported htaccess directive
    #
    # File modified on Mon Jul 10 20:30:20 2006 by server
    # <deactivated is not a supported htaccess directive
    # is not a supported htaccess directive
    # </deactivated>
    # File modified on Sun Jul 2 19:30:04 2006 by server
    # <deactivated is not a supported htaccess directive
    # is not a supported htaccess directive
    # </deactivated>

    I am ignorant about shell access or access logs.

    There is an error_log in the public_html dir. that shows only out of date errors, nothing caused by this error.

    Remember that all of this worked in April, and I have made no changes since then. As such, I dislike the idea of modifying the code.

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