No, this is a bug... I thought we had it fixed. Note that the two statements are not equivalent. The first says, give me everything up to the first anchor. If there is no anchor on the page it should return the whole page, but in that situation it is returning a blank value instead. The second says give me everything regardless. We did some reworking of the process that finds anchors to fix some bugs, but evidently this is still not working perfectly in this specific situation.
I'm going to put out another try at 3.18 just shortly. It will include this fix. Sorry for the confusion, and thanks for spotting the bug. This may just repair some of our other broken plugins... Cheers, Dan On Tue, Oct 6, 2009 at 5:22 AM, MJ <[email protected]> wrote: > > OK. After looking at your demo page, I was able to get it fixed by > changing: > > [(include "{+p}#")] > > to > > [(include "{+p}")] > > Thanks > > On Oct 5, 7:48 pm, MJ <[email protected]> wrote: >> I have verified that I am getting everything in the template but the >> [(include "{+p}#")] part. >> >> On Oct 4, 7:22 pm, The Editor <[email protected]> wrote: >> >> >> >> > Just to verify, you are getting everything in the template but the >> > [(include "{+p}#")] part? All the right pages, and the peripherals, >> > but not the content? >> >> > This was broken temporarily for one or two releases, but seems to have >> > been repaired in 3.16. I just tested that on my home system, and it >> > still appears to be working in 3.17. I set up this demo page to show >> > it is working as I understand the problem... Please clarify. >> >> >http://www.boltwire.com/index.php?p=test.anchors >> >> > Cheers, >> > Dan >> >> > On Sun, Oct 4, 2009 at 7:00 PM, MJ <[email protected]> wrote: >> >> > > Getting a list of pages back without content. Template is as follows: >> >> > > ---- >> >> > > !! [[{+p}|+]] >> > > //>>[(time "{+p3}" "%x")] by {+:author}>>// >> >> > > [(include "{+p}#")] >> >> > > <div style='text-align:right'>//>>[[{+p}|Leave a comment...]]>>//</ >> > > div> >> >> > > On Oct 4, 5:40 pm, The Editor <[email protected]> wrote: >> > >> Are you getting a list of pages back without content or no pages. If >> > >> pages, what does your template look like. Perhaps it is just not >> > >> pulling in the content. >> >> > >> Cheers >> > >> Dan >> >> > >> On Sun, Oct 4, 2009 at 5:21 PM, MJ <[email protected]> wrote: >> >> > >> > The following is what is being used to display blog posts: >> >> > >> > {(search group=blog.* type=-header,footer sort=p3 order=reverse >> > >> > template="blog" if="more {now} {+p3}" count=5)} >> >> > >> > On Oct 4, 4:47 pm, The Editor <[email protected]> wrote: >> > >> >> Can you trace this down at all to what markup is no longer working? >> > >> >> More than likely a simple work around can get this going. All of my >> > >> >> blogs seem to be working fine. Including the largely defunct BoltWire >> > >> >> blog. >> >> > >> >> Cheers, >> > >> >> Dan >> >> > >> >> On Sat, Oct 3, 2009 at 7:23 AM, MJ <[email protected]> wrote: >> >> > >> >> > After upgrading to 3.17, the blog plugin no longer works correctly. >> > >> >> > The content no longer shows up. I will revert back to 3.15. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
