New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
txp:if_article_id on article list context #35
Comments
From mani...@gmail.com on August 25, 2009 16:01:46 BTW, this is current "workaround": <txp:article_custom file_id="_%" section='<txp:section />' > <txp:title /><txp:else /> txp:if_article_id <txp:title /><txp:else /> <txp:title />/txp:if_article_id /txp:if_article_list /txp:article_custom |
From mani...@gmail.com on August 25, 2009 17:07:13 Let me deviate a little from the original issue. This is "worst" that what I would have expected. The above workaround won't work, as txp:if_article_list <txp:article_custom section="a-section"> I've tested the above snippet both on 4.0.8 stable and 4.2.0 RC ( r3269 ) and got the Personally, I consider it a bug, as it doesn't seem to fit in the "standard" TXP way Does it makes any sense? |
From julian.l...@gmail.com on August 28, 2009 18:22:02 Back to the initial issue, anyone may argue that using if_article_id outside an Using it inside an individual_article context, the question means: "is the article id Using it inside an article_list context, the question could mean: "on the current A few more thoughts on all this: Regarding issue on #c2 (if_article_list being "true" inside article_custom, even on Regarding if_article_id, i spotted this scenarios on different scenarios A) if_article_id on individual_article context: A.1) <if_article_id> (no id attribute) is used outside an <article_custom> tag => A.2) <if_article_id id="X"> is used outside an <article_custom> tag => keep current A.3) <if_article_id> (no id attribute) used inside an <article_custom> tag => keep A.4) <if_article_id id="X"> is used inside an <article_custom> tag => keep current (being that every point above says "keep current behaviour", I'm not yet sure where B) if_article_id on article_list context: B.1) <if_article_id> (no id attribute) is used outside an <article_custom> tag => B.2) <if_article_id id="X"> is used outside an <article_custom> tag => new feature: B.3) <if_article_id> (no id attribute) used inside an <article_custom> tag => new B.4) <if_article_id id="X"> is used inside an <article_custom> tag => keep current Ok, I'll stop by now, sorry if this is too much non-sense. |
From mani...@gmail.com on October 31, 2009 08:42:45 Some ongoing discussion related to commend #2 here: http://forum.textpattern.com/viewtopic.php?id=32216 |
Lots of info lost during transfer from Google Code. Let's try that again: Reported by mani...@gmail.com, Aug 25, 2009 When on individual article context, the following snippet work as expected:
But then, if I'm on article list context, I get no ouput at all for any of Tag trace (for the sake of brevity, I've copied just one loop and of the
If you need additional info, please, tell me. What version of the product are you using? On what operating system? Aug 25, 2009 #1 mani...@gmail.com BTW, this is current "workaround":
Aug 25, 2009 #2 mani...@gmail.com Let me deviate a little from the original issue. This is "worst" that what I would have expected. The above workaround won't work, as
I've tested the above snippet both on 4.0.8 stable and 4.2.0 RC (r3269) and got the Personally, I consider it a bug, as it doesn't seem to fit in the "standard" TXP way Does it makes any sense? Aug 28, 2009 #3 julian.l...@gmail.com Back to the initial issue, anyone may argue that using if_article_id outside an Using it inside an individual_article context, the question means: "is the article id Using it inside an article_list context, the question could mean: "on the current A few more thoughts on all this: Regarding issue on #c2 (if_article_list being "true" inside article_custom, even on Regarding if_article_id, i spotted this scenarios on different scenarios A) if_article_id on individual_article context: A.1) A.2) my brain may be reaching a dead-end street below here A.3) A.4) (being that every point above says "keep current behaviour", I'm not yet sure where B) if_article_id on article_list context: B.1) B.2) B.3) B.4) Ok, I'll stop by now, sorry if this is too much non-sense. |
@petecooper , He has nothing to do with this issue. it looks like it's a bug of the GitHub interface. it was # 35 pull request in my repository, synchronization |
As this issue's ten year birthday is approaching this year, I figured it would be worth revisiting.
Is this the answer? @bloatware @Bloke - what is your view on this issue, please? |
As of 4.7.0, |
@Bloke @bloatware is this issue still valid, given the tag changes that were done as part of the 4.8 dev cycle? |
I'm going to close this issue - it's an extreme edge case that nobody know if resolved or not! Basically you can achieve this with other tags anyway nowadays so I don't see any issues. |
From mani...@gmail.com on August 26, 2009 00:53:46
When on individual article context, the following snippet work as expected:
if I'm viewing article X, then article X title is not linked on the
generated output. Great!
But then, if I'm on article list context, I get no ouput at all for any of the two "branches" on the conditional tag.
Tag trace (for the sake of brevity, I've copied just one loop and of the above code):
If you need additional info, please, tell me.
Thanks. What version of the product are you using? On what operating system? I'm on TXP 4.2.0 RC ( r3269 ) on Ubuntu Linux.
Original issue: http://code.google.com/p/textpattern/issues/detail?id=31
The text was updated successfully, but these errors were encountered: