I am still running the 1.2beta beta version you put together when you were trying to help me sort out that one really complex index I had. We never managed to get that to work (for some odd reason, the plugin appeared to end up using far more memory than just repeating the weblog entries tag for each part of the display), so I was wondering if you’d suggest I stick with this beta if I plan to use the plugin for something else, or if I should downgrade to the latest proper release?
You should be fine sticking with the version you have, Linda. I’m not even sure why I still have the “beta” label attached to 1.2. I probably just forgot to take it off.
Btw, I don’t suppose you have any more idea now why the implementation I tried out never quite worked?
The fact that it does manage to output some of the entries (and with the right formatting and all) makes me think memory issues, but on the other hand, doesn’t a lack of memory in php usually result in a blank page, not a partially rendered page? And it does seem strange if the plugin would take more memory than the 20+ wbelog entries tags I have to use otherwise (and that setup does work).
I never did come up with a good explanation for the problems we had with your setup. I don’t remember all the details, but I seem to recall that everything worked just fine ... until a certain point. Then it went phlbbbbbp. I never could figure out why that straw kept breaking the camel’s back.
Were you using advanced conditionals ({if:else} and/or {if:elseif} ), by chance?
Try dumping the advanced conditionals. I hardly ever use them these days because I too often run into problems caused by them being parsed so late in the template parsing process. Regular {if}s make for uglier template code, but they seem sturdier.
Not sure if I did this right, but I tried to switch to just regular conditionals and then I am definitely running into memory issues as I get a blank page:
Lets say that each link in that index is made into an entry, named as the links are currently named.
Do you think Reeposition could help me create an index of these entries that is formatted just as the index currently is formatted? Since its an existing static section that I am trying to move into EE, its important for me to stay as close to the old layout as possible.
I have been trying all day to wrap my head around how one could do this, but I don’t think I am too much closer to a solution. It would be easy enough to label each ‘level’ of entries using categories or a custom status for each, but actually producing a nested index like that without having to manually lay it out seems like it would take some pretty convoluted conditionals, and that might be an issue with Reeposition given the advanced conditionals issues.
I am trying to move multiple items using your wonderful Reeposition plugin, but I can’t get it to do what I want this time.
The code I have right now does reposition the code, but unfortunately it shows the same (first) entry twice.
Could you tell me if this code should be working, or how I can get it to work… or is this not possible?
{exp:reeposition}
{!-- //weblog tag --} {exp:weblog:entries weblog="home" orderby="date" sort="asc" limit="2"}
Okey dokey, I took a look at this and I think I see what’s happening. Fortunately, I also have a solution. I’ll start with the solution. Change these lines:
As for an explanation, without looking into it too deeply, it looks like you’re hitting some sort of parsing order problem. At the time Reeposition runs, it is seeing the contents of both “if” blocks for both entries. That means two things. First, it means that Reeposition ends up trying to place four (2x2) different items; and second, it means that both of the put_item variables get replaced by the first entry, leaving nothing else to replace after that. (Did that make any sense?)
I will need to look deeper to determine if there’s something I can do to Reeposition to help the situation, but the only solution that comes to mind would cause problems in certain usage scenarios, so it’s out.
Any idea why this is not working? It does not seem to move the items, but prints out the tags (I get {reeposition:put_item id=“catid”} and {reeposition:put_item id=“catid”} tags displayed in the debugging).
Any idea why this is not working? It does not seem to move the items, but prints out the tags (I get {reeposition:put_item id=“catid”} and {reeposition:put_item id=“catid”} tags displayed in the debugging).
Notice that I put the reeposition tag inside the paginate tag instead of out. The paginate tag simply defines how it will look, not where it will go; hence, trying to reposition this is an exercise in futility. However, if you reposition its contents, it should work.
EDIT: I assume this is the snippet of code you were talking about?
What I’m trying to do is pull up the latest entry according to a sort oder, find the category that entry belongs to, then move that category ID down to the last exp:weblog:entries tag.
Just wasn’t sure if it ended up being an experimental ‘side branch’ or if it actually is in line with the regular release.
