Forum Replies Created

Viewing 15 replies - 16 through 30 (of 36 total)
  • Thread Starter mndoci

    (@mndoci)

    A number of people have successfully moved to my current host, so I suspect it does work, and Podz (whose tutorial I followed) also hosts there.

    I did create a .htaccess file. Lets see how it works.

    I am not sure what you mean by the re-saving settings part? Yes, this is a completely new host (same domain name).

    Thread Starter mndoci

    (@mndoci)

    An update:

    I redid the blog move, this time, turning off a few plugins, including wp-cache. I changed my nameservers over. The front page looks OK, but when I click on individual links, I am getting errors like

    The requested URL /blog/archives/ was not found on this server.

    Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

    What could be causing this?

    Thanks

    Thread Starter mndoci

    (@mndoci)

    BUMP .. Anyone?

    Thread Starter mndoci

    (@mndoci)

    Just for the record here is the complete error message


    Warning: fopen(/home/user/public_html/domain_name/blog/wp-content/cache/wp_cache_mutex.lock) [function.fopen]: failed to open stream: Permission denied in /home/user/public_html/domain_name/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 79
    Couldn't write to: /home/user/public_html/domain_name/blog/wp-content/cache/wp-cache-48736852343c354627f7d006c54befd0.html
    Warning: flock(): supplied argument is not a valid stream resource in /home/user/public_html/domain_name/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 88
    Warning: fopen(/home/user/public_html/domain_name/blog/wp-content/cache/wp-cache-48736852343c354627f7d006c54befd0.meta) [function.fopen]: failed to open stream: Permission denied in /home/user/public_html/domain_name/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 223
    Warning: fputs(): supplied argument is not a valid stream resource in /home/user/public_html/domain_name/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 224
    Warning: fclose(): supplied argument is not a valid stream resource in /home/user/public_html/domain_name/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 225
    Warning: flock(): supplied argument is not a valid stream resource in /home/user/public_html/domain_name/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 97

    Thread Starter mndoci

    (@mndoci)

    1. Yes I do
    2. Not all my themes, since there were a few I never used. I guess I should. Plugins, yes. I had not copied the content of the cache folder (under wp-content), but I just did. However, the specific file that is giving the error is not there.

    Thread Starter mndoci

    (@mndoci)

    Thanks, that seemed to help… and changed the errors

    Now I am getting a bunch of cache related errors like the following


    Warning: fopen(/home/user/public_html/domain_name/blog/wp-content/cache/wp_cache_mutex.lock) [function.fopen]: failed to open stream: No such file or directory in /home/user/public_html/domain_name/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 79
    Couldn't write to: /home/user/public_html/domain_name/blog/wp-content/cache/wp-cache-48736852343c354627f7d006c54befd0.html

    Thread Starter mndoci

    (@mndoci)

    From what I can gather, the addon domain is not an issue. Since I am not changing the blog structure, I suspect its the database. Any troubleshooting suggestions?

    Thread Starter mndoci

    (@mndoci)

    I redid everything from scratch and still the same problem

    Here is my wp-config.php. Everything is the same as before, except that here the db name and username have a pre-fix that cpanel automatically attaches when I created the empty db and a new user for it. I typed in the username and password manually into the file (probably not the right thing to do either)


    <?php
    define('WP_CACHE', true); //Added by WP-Cache Manager
    // ** MySQL settings ** //
    define('DB_NAME', 'blog_db_name'); // The name of the database.
    define('DB_USER', 'username'); // Your MySQL username
    define('DB_PASSWORD', 'password'); // ...and password
    define('DB_HOST', 'mysql'); // 99% chance you won't need to change this value
    // Change the prefix if you want to have multiple blogs in a single database.
    $table_prefix = 'wp_'; // example: 'wp_' or 'b2' or 'mylogin_'
    // Change this to localize WordPress. A corresponding MO file for the
    // chosen language must be installed to wp-includes/languages.
    // For example, install de.mo to wp-includes/languages and set WPLANG to 'de'
    // to enable German language support.
    define ('WPLANG', '');
    /* Stop editing */
    define('ABSPATH', dirname(__FILE__).'/');
    require_once(ABSPATH.'wp-settings.php');
    ?>

    Thread Starter mndoci

    (@mndoci)

    Diane

    Thanks for your response. Very good question. Here’s how it works. I have moved one domain over (not a blog) already, and things seems easy enough.

    1. All files go into a folder called public_html. The main domain resolves to that folder. Each addon domain goes into its own folder underneath public_html. In the previous case, changing the DNS to point to my new hosts DNS servers did the trick

    2. In my current blog I have the following structure
    /
    index.php
    blog/

    All my files are under blog, but going to xyz.com reads the index.php file which just points to the blog/ (something I would love to change but too much content to take the risk now)

    3. The database part is what I am worried about. I am no MySQL guru. Are the username and password in wp-config.php the same as the admin username and password for my wordpress account? They are a random string in wp-config.php. I presume I can use regular text to change things?

    Thanks for all the help

    Forum: Fixing WordPress
    In reply to: Is yahoo down?
    Thread Starter mndoci

    (@mndoci)

    It’s back up now, but I am getting really getting frustrated with Yahoo.

    Its back up for me as well

    I am getting the error too. I have tried using a different browser as well. I suspect some of the Yahoo servers are acting up, since not everyone is seeing this error.

    Thread Starter mndoci

    (@mndoci)

    I am trying a new experiment. I deleted the blog and set it up again, but I am not going to import my old posts at this time. I want to make sure that it was the blogger import that was the issue. If things work well for a bit then I will look into that again.

    Thread Starter mndoci

    (@mndoci)

    That is the information I needed. Right now I have about 40 posts (after deleting some). If I just load the blog itself everything seems OK, but if I start using the comment, posting and management tools, things start slowing down. I am going to work with my web host to see if it is anything at their end, otherwise I am going to try and use the blog without importing for a bit to see if it was related purely to that.

    Thread Starter mndoci

    (@mndoci)

    Thanks anyway .. My gut feeling is that it is something to do with WP and MySQL, but can’t be sure. Hopefully someone else has some ideas

Viewing 15 replies - 16 through 30 (of 36 total)