Forum Replies Created

Viewing 15 replies - 1 through 15 (of 24 total)
  • Forum: Fixing WordPress
    In reply to: Fatal Error: cache
    Thread Starter sevennine

    (@sevennine)

    Ok, the error is back. uggh. Looks like the plugin didn’t cause it. Anyone have a clue?

    This time the error is:
    Fatal error: Allowed memory size of 94371840 bytes exhausted (tried to allocate 65536 bytes) in /home/marchodges/sevennine.net/wp/wp-includes/cache.php on line 382

    Forum: Fixing WordPress
    In reply to: Fatal Error: cache
    Thread Starter sevennine

    (@sevennine)

    Nevermind, I figured it out. The ‘Broken Link Checker’ plugin was causing the cache error.

    Forum: Fixing WordPress
    In reply to: using mod wrewrite
    Thread Starter sevennine

    (@sevennine)

    Carlla

    It didn’t seem to work. The images aren’t uploaded through WP so that might be the issue. Do you have another idea?

    Thread Starter sevennine

    (@sevennine)

    ok, after some brute force and ignorance I got something working. My only question is why doesn’t name_save_pre get called the first time I save a post or when I change its category. I have to click save twice to get it to work.

    For reference, here’s the skeleton of my working code. It’s interesting because post savings are actually redirected to the post.php file but with no attributes. Once it’s saved, you’re redirected to the editing screen. So there’s a secret page that saves the post. It makes debugging a little harder.

    function mhp_change_slug($slug) {
    	$new_slug = $slug;
    
    	//get post since it's not global
    	$post = get_post($_POST['post_ID']);
    
    	//filtering magic goes here
    
    	//return new slug
    	return $new_slug;
    }
    
    add_filter('name_save_pre', 'mhp_change_slug', 1, 1);

    so does anyone know why ‘name_save_pre’ doesn’t get called on the initial save?

    Forum: Plugins
    In reply to: rewrite
    Thread Starter sevennine

    (@sevennine)

    just found a wicked tutorial to help out… well it’s actually a plugin but you can figure it out from looking at the code
    http://www.whypad.com/posts/wordpress-plugin-url-rewrite/194/

    Hey, I had the same issue and managed to fix it

    I posted a solution in another thread.

    Thread Starter sevennine

    (@sevennine)

    Ok… I’ve managed to correct the issue. It seems that it’s caused by some of the entries in the ‘postmeta’ table of the WP DB.

    Once I deleted all entries in the table where meta_key=_tc_post_format or meta_key=_tc_post_encoding then everything worked fine again. I don’t know why, but it does.

    Thread Starter sevennine

    (@sevennine)

    ok… I’ve been able to figure out that it’s only happening when I load a blank new post page. But if I load a published post then I don’t get the error. It’s weird.

    Thread Starter sevennine

    (@sevennine)

    got some reason $post wasn’t globally called, just added
    global $post;
    and it was all good

    Thread Starter sevennine

    (@sevennine)

    its running in TAG.PHP and is called when the tag archive is called for the Ultimate Tag Warrior plugin

    Thread Starter sevennine

    (@sevennine)

    you would think that wouldn’t you? but the following only produces a list of the titles, am I missing something here? Shouldn’t it produce the title and the post’s details?

    <?php
    if (have_posts()) :
    while (have_posts()) : the_post();
    the_title();
    print_r($post);
    endwhile;
    endif;
    ?>

    Thread Starter sevennine

    (@sevennine)

    much appreciated

    Thread Starter sevennine

    (@sevennine)

    Thread Starter sevennine

    (@sevennine)

    ok, I managed to add my rules to the rewrite, but can someone tell me why they don’t work. When I print out the $wp_rewrite->rules, my section is below.

    I’m assuming that I can’t use the $_GET to get the variables… what do i use?

    [photos/albums/?$] => index.php?pagename=photos&view=albums
    [photos/albums/([0-9]+)/?$] => index.php?pagename=photos&album=$matches[1]
    [photos/albums/([0-9]+)/([0-9]+)/?$] => index.php?pagename=photos&photo=$matches[2]&album=$matches[1]
    [photos/albums/([0-9]+)/page([0-9]+)/?$] => index.php?pagename=photos&album=$matches[1]&thumb_page=$matches[2]
    [photos/tags/?$] => index.php?pagename=photos&view=tags
    [photos/tags/([_0-9a-z-]+)/?$] => index.php?pagename=photos&tags=$matches[1]
    [photos/tags/([_0-9a-z-]+)/([0-9]+)/?$] => index.php?pagename=photos&photo=$matches[2]&tags=$matches[1]
    [photos/tags/([_0-9a-z-]+)/page([0-9]+)/?$] => index.php?pagename=photos&tags=$matches[1]&thumb_page=$matches[2]
    [photos/page([0-9]+)/?$] => index.php?pagename=photos&thumb_page=$matches[1]
    [photos/([_0-9a-z-]+)/?$] => index.php?pagename=photos&view=$matches[1]
    [photos/([_0-9a-z-]+)/page([0-9]+)/?$] => index.php?pagename=photos&view=$matches[1]&thumb_page=$matches[2]
    [photos/([_0-9a-z-]+)/([0-9]+)/?$] => index.php?pagename=photos&view=$matches[1]&photo=$matches[2]

    Forum: Plugins
    In reply to: F Gallery released!
    Thread Starter sevennine

    (@sevennine)

    I also managed to get the error, once, but can’t produce it on a regular basis once I cleared the cache. So my only assumption is that it’s a cache problem. Just clear the gallery cache and it should work properly.

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