Forum Replies Created

Viewing 15 replies - 1 through 15 (of 20 total)
  • Thread Starter gilgimech

    (@gilgimech)

    First off,

    Why are you assuming that I’m actually using this in a real site? I never stated or implied that I was. I just asked a question. This is just something I came acros a few months ago and digging through the core by myself hasn’t giving me any answers, so against my better judgment I decided to post it here hopping there might be someone that is willing to help me figure this out.

    If, you know exactly what I’m asking then why don’t you just answer my question instead of making assumptions.

    Yes, I know how conditional functions, add_action, and do_action() work.

    There are no functions attached to the do_action(‘init’). It’s just do_action(‘init’) all by itself with no other functions. do_action(‘init’) shouldn’t do anything (as far as I know). If anything, I think it should throw an error, but it doesn’t. What it does do is it allows the conditional function in the functions.php file even though they shouldn’t.

    So what’s causing that? are there some core function tied to init() causing this. If so what are they? Why would these functions be causing the conditional functions to work? That’s what I’m looking for.

    So, catacaustic. Please just stop posting unless you’re willing to help me figure this out.

    Thread Starter gilgimech

    (@gilgimech)

    OK,

    Never mind. You just don’t understand what I’m asking. This was just a fluke that I came across and I want to understand why it works. Is it just a bug, or is it something else?

    I’m not asking if it’s right or wrong. I don’t need help with any code. I just want to figure out why this works the way it does.

    It seems like a bug to me, and if I can figure it out or if someone might be able to help me figure it out. Then it can be reported and fixed.

    Just read my original post. The first this I said is that I understand why the conditionals don’t work in the functions.php file, but I stumbled onto this and I want to figure out why it works.

    Thread Starter gilgimech

    (@gilgimech)

    No,

    Sorry, maybe I didn’t explain it well.

    I’m not calling any function with the do_action().

    It’s literally just

    <?php do_action(‘init’); ?>

    with no function attached to it.

    for some reason just having that little snippet causes the conditionals to work in the other functions in the functions.php file. Where as if that snippet wasn’t in the head the conditionals don’t work.

    The load_js() function was just a demonstration. The function is irrelevant. Its the is_home() that’s the focus.

    gilgimech

    (@gilgimech)

    The error is being caused by this function on line 1238 in the disqus.php file.

    function dsq_prev_permalink($post_id) {
    // if post not published, return
        $posts = &get_post($post_id);
        if ($posts->post_status != 'publish') {
            return;
        }
        global $dsq_prev_permalinks;
        $dsq_prev_permalinks['post_'.$post_id] = get_permalink($post_id);
    }
    add_action('pre_post_update', 'dsq_prev_permalink');

    The error is cause by the $post variable. It’s trying to return the get_post() function by reference. As of PHP5 you no longer need to do this because it returns a reference automatically.

    If you want to hack the disqus plugin just remove the ‘&’ before the get_post() function. That will get rid of the error.

    Removing it hasn’t caused any errors for me, but you should be warned. Removing it could cause errors that I’m not aware of, and any updates to the plugin will override your changes.

    I’m not sure why it’s there. It’s either just code that hasn’t been updated or disqus is just trying to accommodate older versions of PHP. Then again I may just be way off and there is a reason for it. Again if you are going to hack the plugin there might be unseen consequences.

    Use

    #fb-root {
      display: none;
    }
    .fb_iframe_widget, .fb_iframe_widget span, .fb_iframe_widget span iframe[style] {
      width: 100% !important;
    }

    and make sure is it’s wrapped in an element that it width is set to 100%

    First off. You have your logo wrapper in a <hgroup> tag. <hgroup> tags are for grouping H tags (<h1>). Try changing it to a <div>.

    If that doesn’t work add this CSS to <div> wrapping your logo image.

    position: absolute;
    top: -30px;

    Thread Starter gilgimech

    (@gilgimech)

    Yeah, the more I use this plugin the less I like it. I plan on switching to Gravity Forms in the near future.

    Thread Starter gilgimech

    (@gilgimech)

    Yeah, I had to go into the plugin and remove them there. It’s in each of the files in the modules folder.

    Look for $html variables. That’s where I edited it.

    If you’re not comfortable with PHP I don’t recommend editing the files.

    Thread Starter gilgimech

    (@gilgimech)

    Yeah, but unless it’s been change since I down loaded it Tuesday. There are no template files in the plugin, just some empty folders.

    Thread Starter gilgimech

    (@gilgimech)

    That didn’t make any difference. I’m pretty sure it’s not the CSS. I’m thinking it might be a plugin.

    Thread Starter gilgimech

    (@gilgimech)

    Here you go
    Inner Mind Labs

    Thread Starter gilgimech

    (@gilgimech)

    Yeah, it renders correctly on the default theme, but I have no idea where the <p> is coming from. There’s nothing in my theme that should be making it.

    this is the code on the page.php file.

    [Code moderated as per the Forum Rules. The maximum number of lines of code that you can post in these forums is ten lines. Please use the pastebin]

    `
    I just don’t see what can be causing it.

    Thread Starter gilgimech

    (@gilgimech)

    No that’s not it.

    The way it’s being outputted is

    <p>
    <lable></lable>
    <span>
    <span>
    <select></select>
    <p>
    </span>
    </span>
    </p>

    the way it should be outputted is

    <p>
    <lable></lable>
    <span>
    <span>
    <select></select>
    </span>
    </span>
    </p>

    for some reason an extra <p> is being generated.

    Thread Starter gilgimech

    (@gilgimech)

    Never mind I got it working. For some reason a div from a pagination function was being output in the live-comment-preview.js. I just removed that function and it worked.

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