No output at all from one weblog after 1.6 upgrade.

#1 / Jun 25, 2007 10:49am

Linda A

666 posts

I went ahead and did the 1.6 upgrade, but now I’ve got an empty index for one of my weblogs.

The code being used is this:

<ul class="Concordance">
{exp:weblog:entries weblog="{current_weblog}" limit="500" orderby="{current_weblog_id}_number_sorting" sort="asc" disable="member_data|pagination|trackbacks"}
{categories}
{if category_id == "166"}
<li class="One">{{current_weblog_id}_number_display} <a href="http://www.westeros.org/Citadel/Concordance/Section/{{current_weblog_id}_number_display}/">{title}</a></li>
{/if}
{if category_id == "167"}
<li class="Two">{{current_weblog_id}_number_display} <a href="http://www.westeros.org/Citadel/Concordance/Section/{{current_weblog_id}_number_display}/">{title}</a></li>
{/if}
{if category_id == "168"}
<li class="Three">{{current_weblog_id}_number_display} <a href="http://www.westeros.org/Citadel/Concordance/Section/{{current_weblog_id}_number_display}/">{title}</a></li>
{/if}
{if category_id == "169"}
<li class="Four">{{current_weblog_id}_number_display} <a href="http://www.westeros.org/Citadel/Concordance/Section/{{current_weblog_id}_number_display}/">{title}</a></li>
{/if}
{/categories}
{/exp:weblog:entries}
</ul>

Yesterday, before I upgraded, this generated the index without any problems at all.

I went ahead and broke the code out into a separate template (which does have the variables used defined at the top), but even that didn’t help, so the error must be somewhere within this code. And I did check that the entries for the weblog are still in the database.

#2 / Jun 25, 2007 10:57am

Robin Sowell
13255 posts

A 500 limit is pretty high- what happens if you turn ‘show queries’ on in ‘Admin- System Prefs- Output and debug’- do the queries show ok? And can you tell if one is happening for the weblog with the id of the one that’s giving you trouble?
#3 / Jun 25, 2007 11:02am

Linda A
666 posts

I tried lowering it to 100 as well, but nothing shows up then either.

If I turn on the debug options, I get _a lot_ of queries. I am not quite sure what I am supposed to be looking for in them. There’s some 180 lines of queries.
#4 / Jun 25, 2007 11:05am
Robin Sowell
13255 posts
Well- that’s good- at least it’s not a php memory issue! Let’s try one more thing on the test template- after that, I may ask for access so I can take a look at the queries. Just put:
```
<ul class="Concordance">
{exp:weblog:entries weblog="{current_weblog}" limit="500" orderby="{current_weblog_id}_number_sorting" sort="asc" disable="member_data|pagination|trackbacks"}
{title}

{/exp:weblog:entries}
</ul>
```
Let’s see if the problem is with the conditionals, the category tag, or something else. Just make sure your globals are properly defined when you test the above.
#5 / Jun 25, 2007 11:08am

Linda A
666 posts

That outputs a list of all the entries.
#6 / Jun 25, 2007 11:20am
Robin Sowell
13255 posts
Hm- ok, I’m not duplicating with a simple test:
```
{exp:weblog:entries}
{title}
{categories}
{if category_id == "5"}
<h1>Category!</h1>
{/if}
{if category_id == "1"}
<h1>ALSO Category!</h1>
{/if}
{/categories}
{/exp:weblog:entries}
```
Two possibilities- I may be running a slightly newer build that has a bug fix: Build: 20070622. So- if you’re behind that one, try updating.

Also- I know in the next bug fix, there are some parsing issues that will be addressed- cropped up due to the new category custom fields. I’m not sure how pervasive the effects of the current parsing are- so it could be your globals or something are caught up in that issue somehow. One way to test that- put some placeholder text inside your conditionals- along the lines of what I have. See if that works.

Make sense?

#7 / Jun 25, 2007 11:31am

Linda A

666 posts

I’ve got the same build, so that shouldn’t be the issue, unless the build log was wrong about the update date (though, I uploaded all files changed on or after the 20th from the newest build zip, to make sure I got any that had been altered).

I tried with some placeholder text for each conditional, and that does give me some output.

Specifically, this:

<ul class="Concordance">
{exp:weblog:entries weblog="{current_weblog}" limit="500" orderby="{current_weblog_id}_number_sorting" sort="asc" disable="member_data|pagination|trackbacks"}
{categories}
{if category_id == "166"}
Cat 166
{/if}
{if category_id == "167"}
Cat 167
{/if}
{if category_id == "168"}
Cat 168
{/if}
{if category_id == "169"}
Cat 169
{/if}
{/categories}
{/exp:weblog:entries}
</ul>

produces this:

Cat 166 Cat 167 Cat 167 Cat 167 Cat 167 Cat 167 Cat 166 Cat 167 Cat 168 Cat 168 Cat 169 Cat 168 Cat 169 Cat 169 Cat 169 Cat 169 Cat 167 Cat 168 Cat 168 Cat 168 Cat 168 Cat 168 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 167 Cat 168 Cat 169 Cat 167 Cat 168 Cat 168 Cat 167 Cat 168 Cat 167 Cat 168 Cat 167 Cat 167 Cat 166 Cat 167 Cat 168 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 167 Cat 167 Cat 167 Cat 167 Cat 166 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 169 Cat 169 Cat 167 Cat 168 Cat 167 Cat 166 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 167 Cat 166 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 169 Cat 169 Cat 169 Cat 169 Cat 167 Cat 167 Cat 166 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 168 Cat 169 Cat 167 Cat 166 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 169 Cat 167 Cat 166 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 169 Cat 169 Cat 167 Cat 166 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 168 Cat 169 Cat 167 Cat 166 Cat 167 Cat 167 Cat 167 Cat 167 Cat 166 Cat 167 Cat 167 Cat 168 Cat 168 Cat 169 Cat 168 Cat 168 Cat 168 Cat 168 Cat 168 Cat 168 Cat 168 Cat 167 Cat 168 Cat 167 Cat 168 Cat 168 Cat 168 Cat 168 Cat 167 Cat 167 Cat 168 Cat 168 Cat 167 Cat 167 Cat 168 Cat 168 Cat 168 Cat 167 Cat 168 Cat 169 Cat 168 Cat 168 Cat 168 Cat 167 Cat 166 Cat 167 Cat 167 Cat 167 Cat 167 Cat 166 Cat 167 Cat 168 Cat 168 Cat 166 Cat 166

#8 / Jun 25, 2007 11:37am

Robin Sowell

13255 posts

Hm- well, I still lean toward it being that parsing issue- but I can’t duplicate it. I thought maybe it had to do with your globals- but I tried:

{assign_variable:current_weblog_id="booter"}
{assign_variable:booter_number_display="NESTED"}

{exp:weblog:entries}
{title}
{categories}
{if category_id == "5"}
<h1>Category! {current_weblog_id}</h1>
{/if}
{if category_id == "1"}
<h1>ALSO Category! {{current_weblog_id}_number_display}</h1>
{/if}
{/categories}
{/exp:weblog:entries}

That still displays fine. How are you defining those variables you’re using inside the categories tags?

#9 / Jun 25, 2007 11:39am

Robin Sowell
13255 posts

Also- did you create any new categories since upgrading to 1.6?
#10 / Jun 25, 2007 11:40am
Linda A
666 posts
The variables are defined like this:
```
{assign_variable:current_weblog="weblog32"}
{assign_variable:current_weblog_id="32"}
{assign_variable:current_template_group="Concordance"}
```
And no, haven’t created any categories since the upgrade.
#11 / Jun 25, 2007 12:46pm

Lisa Wess
20502 posts

There was another post on this, to which I don’t have a current link, but essentially this was because of the new category custom fields and some confusion. I believe Derek said it’ll be fixed in the next build.

Aha, I found the thread.
#12 / Jun 25, 2007 12:52pm

Linda A
666 posts

Aha, okay. Thank you both, Robin and Lisa. 😊

I’ll see about dropping Derek an email for the fix, since its a pretty important section to have up.

Thread

Linda A

Robin Sowell

Linda A

Robin Sowell

Linda A

Robin Sowell

Linda A

Robin Sowell

Robin Sowell

Linda A

Lisa Wess

Linda A

Username

Password

Thread