• ok weird…..
    im probably missing something but i updated to 1.3 but im transfering stuff from my old index .php to the wp-header.php
    but at this point…
    all goes well…

    <div id="content">
    <?php endif; ?>

    but when i ad…this..(as in my original index.php).

    <div id="content">
    <?php if ($posts) : foreach ($posts as $post) : start_wp(); ?>
    <?php endif; ?>

    i get an error like below…
    Parse error: parse error, unexpected T_ENDIF in /home/public_html/myblog/wp-header.php on line 114
    So what am i missing ?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter john1000

    (@john1000)

    what kind of bullshit respond is this…
    man your very helpfull idiot…

    Moderator James Huff

    (@macmanx)

    Most parse errors go unsolved. The moral of the story is, don’t use the nightly unless you’re only using it as a test blog, or know a lot about PHP and MySQL. This is the only solved parse issue, maybe it’ll help you: https://www.ads-software.com/support/2/17222

    John – language like that will get you no help at all in the future.
    I said to CAREFULLY change the files IF you wanted – it was not absolutely necessary.

    Thread Starter john1000

    (@john1000)

    well im just reflecting how i feel..
    and if its an alpha release….who cares !
    main thing is that i get it work….
    if i cannot help another on a forum i just keep my mouth shut,and not posting towards someone who’s asking for help….that its a alpha shit.
    and language podz..?……come on…
    and i hoped for a more detailed story on the changes….

    Thread Starter john1000

    (@john1000)

    well i already figured out what went wrong…
    and i understand your all friends but i dont give a damn.
    if your not have your own opinion that posting a shitty link sucks then i cant help it.
    support means support,to bad for some….there’s no between or grey area.

    John – I can recall when you have posted here before…….
    1.3 is NOT ready for a full release, so please expect to have problems. Read the sticky post I wrote here:
    https://www.ads-software.com/support/3/12916
    If you want a detailed breakdown of all the changes, then it won’t be found here in one place. It will however be found by searching through many posts that details small changes here and there, and by checking out the wiki. And the reason it’s not here is simply because 1.3 has not yet been released.
    I suggest you read this post very carefully too before posting again:
    https://www.ads-software.com/support/3/14659

    Thread Starter john1000

    (@john1000)

    oh but i do understand that every forum has his rules but posting a link like the above member did isnt in any way constructive and helpfull.
    its not helping but giving a kick in the face …..
    and people should stop doing that….
    my motto is help each other or get lost…
    im honest enough to say im sorry for any bad language used…
    that means….im honest enough…i cant speak for others…

    Dear John:
    I beg to differ. I just gave the link that Moshu provided a CURSORY glance and saw this (and comprehended it too, I might add!):

    Using nightlies in the alpha stage is only recommended if you are actively debugging the code, meaning finding bugs and sending in patches.

    So what Moshu was trying to do, I’m sure, was to educate you on the purpose of the nightlies. If you have problems with them, that’s not the same as having problems with the stable version. These kind of things are to be expected. And while no one is attempting to censor your right to free speech such as it is here on this webspace that neither you nor I pay for, you can get more help acting like a gentleman than like a little beast.
    Nuff said. Hopefully you’ll accept my comment — and all the others — in the spirit of helpfulness in which they are given. (Mine at least, I shouldn’t speak for anyone else.)
    You’d be amazed at what you can see when you remove your head from that dark place….

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘where does this error comes from?’ is closed to new replies.