Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Did you figure out which plugin was causing the conflict? I just started getting this error as well.

    Thread Starter Brian Hall

    (@domain101)

    Unfortunately, no. I settled on a less elegant solution that involved adding some extra fields to taxonomies. Poor substitute for the solution I really wanted, but I didn’t have the time to really research a solution.

    If you come up with something though, I’d love to hear about it!

    Thread Starter Brian Hall

    (@domain101)

    Assuming I purchased the PRO version (which I was planning to do eventually anyway, this just bumps up the timeline), how would I accomplish this?

    Throwing out a possible solution, as I just encountered a similar problem. For me, it turned out to be a filter action on either the Title or Name (slug) not returning.

    In my case, I added a custom post-type that auto-generated a title and slug (off a combination of taxonomies) using the “title_save_pre” and “name_save_pre” filters. However, I only returned a value if the proper taxonomies were set – which in the case of Pages and Posts wouldn’t be set. But I forgot to return the original value, even if I didn’t override it.

    The point of this story was, if something is interfering with either your Title or Name (slug) for any Page/Post, or returning a null value, it obviously disables your ability to save or publish.

    Hope that helps somebody.

    Thread Starter Brian Hall

    (@domain101)

    Alright, I found a workaround. For anyone else looking for a solution, it goes something like this:

    In your 404.php file, get the key after the last “/” in the URL:

    $ru =& $_SERVER['REQUEST_URI'];
    $ruArray = split('/', $ru);
    $ruCandidate = $ruArray[count($ruArray) - 1];

    Next, run whatever DB queries you need to, and confirm you’ve got a real record. From here, you can save to session or whatever else you need to do. Finally, we want to display the homepage without modifying the URL or redirecting. Here’s how I did it:

    // Set your arguments to pull the home (front) page
    $home_args = array('page_id'=>get_option('page_on_front'));
    
    // Override $wp_query with the new query
    $wp_query = new WP_Query($home_args);
    
    // Cancel the 404 status
    $wp_query->is_404 = false;
    
    // Set the default template to load, if Page Template isn't defined
    $use_template = "index.php";
    
    // In case your page is using a specific Page Template...
    $page = $wp_query->get_queried_object();
    $custom_fields = get_post_custom_values('_wp_page_template',$page->ID);
    $page_template = $custom_fields[0];
    if (!empty( $page_template )) {
    	$use_template = $page_template;
    }
    
    // Load the template
    load_template(get_template_directory() . "/" . $use_template);
    
    // Kill everything else (including the default 404 display)
    die;

    Hope this saves someone else some time!

    Adding overflow:hidden to the #site element patched the display, though I didn’t see what was causing the expansion. You’ve got a lot of JavaScript code running, so it could be anywhere.

    #site {
        min-width: 962px;
        overflow: hidden;
    }
Viewing 6 replies - 1 through 6 (of 6 total)