ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

help for Expression Engine (code)

April 10, 2008 3:21pm

Subscribe [1]
  • #1 / Apr 10, 2008 3:21pm

    Os...

    4 posts

    Hello Code Igniters,

    Im not sure wether i can ask you something, or in the Lounge, but I thought I give it a try 😉

    Anyway, as already (poorly) discussed in the EE “how to” forums here:
    http://ellislab.com/forums/viewthread/76024/

    I am determined to solve the problem of Next / Previous entry linking across weblogs resp. template_group/templates.

    To be more precise: EE ofers to paginate the entries using this code pair

    {exp:weblog:next_entry}
    Next entry: <a href="http://{path=">{title}</a>
    {/exp:weblog:next_entry}

    But as you can see it links to a hardwired path=“site/comments”, which means ONE template. Now, in this one template i cannot use my custom entry fields from various weblogs (if you know EE).

    So I want to link to what I call the original template_group/template path.

    Englands best Expression Enginist Mark Bowen tried to help with some if-clauses, as you can read in the thread above, but there EEs next/prev function intents only to grab the first link and the last (title), resp. ignore the if-statements.

    I thought that maybe someone here is clever enough to see what I mean and help it out. The next/prev function lies at system/modules/weblog/mod.weblog.php line 6469, and looks too big for me to decipher ...

    Even a small donation shall be innit.

    cheers,
    Os…

  • #2 / Apr 10, 2008 3:54pm

    Pascal Kriete

    2589 posts

    I’ll have a look, but one question.  Why did you sign up for another account?

    All EL sites are one EE install.  That means one login for everything.

  • #3 / Apr 10, 2008 4:41pm

    Os...

    4 posts

    Oh, didnt realize that i can sign up with same account. Bummer..

    And yes, thanks for throwing an eye on that topic. i only want to keep the flexibility of multiple weblogs aasigned to their own template_groups/template, but also send users through the weblog entries using next / prev.

    Thanks,
    Os.

  • #4 / Apr 10, 2008 5:06pm

    Pascal Kriete

    2589 posts

    So basically what has to happen is that EE has to grab the template of the next entry, instead of just assuming the same template?

  • #5 / Apr 10, 2008 5:50pm

    Os...

    4 posts

    the next or previous template-group name of the next or previous entry, thats right (see below).

    The given { exp:weblog:next_entry } ... { /exp:weblog:next_entry } tag pairs only attach the next entry url as 3rd segment to the path= variable. I need this path= kinda dynamic, not static, esp. not (site)/comment.

    There were some attemps in the EE “How To” Forum (link above),  but they couldnt work out right. ( theres one mistake to correct: it has to be segment_1 at last try , cause thats were the template_group name changes, ie. live/article, feature/article and so on.)

    Will check back ltr.

  • #6 / Apr 11, 2008 8:41am

    Os...

    4 posts

    So basically what has to happen is that EE has to grab the template of the next entry, instead of just assuming the same template?

    yes, the next / prev template_group is enough in my case. Thought if the { exp:weblog:next_entry } ... { /exp:weblog:next_entry } tag pairs correctly find the next (and prev) entry_titles, then they -somehow- should also grab the correspondent template_group/template segments.

    Or an extra mysql statement to retrieve the info which template_group is prev or next according to the entry_id? The result must then be placed dynamically into the Path={*here goes the template_group*}/article link. Possible?

    I dont know how to do this in php, here is a documentation of the template class used by EE (http://expressionengine.com/docs/development/usage/template.html),
    -if it helps.

  • #7 / Apr 11, 2008 8:59am

    Pascal Kriete

    2589 posts

    Just to let you know this is still on my radar screen.  It’s a great excuse to bury myself in the EE source code.  It’s taking a while because I know absolutely nothing about the EE database structure and that function generates an enormous query.

    If you’re serious about possibly purchasing EE and need a quicker/more solid solution than my dirty hacking, you might want to consider the Pre-Sales forum (/waves fence post 😉 ).

  • #8 / Apr 11, 2008 10:04am

    Os...

    4 posts

    I think i can await your hackin’ 😉 hehe

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases