Would be nice if book links (when insert a book page in another content) be hide.
A parameter book could show this link for who need it.
Thanks!
Would be nice if book links (when insert a book page in another content) be hide.
A parameter book could show this link for who need it.
Thanks!
Comments
Comment #1
AlexisWilke commentedHi lilyzm,
It would be nice, wouldn't it?
I was working with a customer when I first noticed the problem. I indeed have to fix it! More soon. What I have seen so far does not indicate that this will be easy... but I'll have a solution, may quite specialized, or just by changing a template.
Thank you.
Alexis
Comment #2
AlexisWilke commentedLilyzm,
Re-reading your node, I think that all you have to do to get the book page description is to use the cck=body; option (see here.)
So try something like this:
[node:123 cck=body;]
Although, I was thinking that did not work because I was doing it with books that had a completely empty body and the result was the default, themed, node body. I checked in a fix for that case and it should appear within the next 12h.
For the navigation I added another CCK field as follow:
[node:123 cck=book_navigation;]
This new option inserts the links to the children and the previous, parent, and next links at the bottom.
If this does not answer your request, feel free to re-open this issue.
Thank you.
Alexis
Comment #3
AlexisWilke commentedJust in case, I also added another entry to only insert the links from a book page:
[node:123 cck=book_children;]
Feel free to reopen the issue if you cannot make it work the way you wanted to.
Thank you.
Alexis
Comment #4
lilyzm commentedHi!
Thank you for your reply but I'm not sure that i understand what you are telling me.
We use in our project insert node a lot.
Our content has many cck fields and body may be empty. Insert Nodes are made by users. It's hard to train user to use [node:123 cck=body, cck=field_name....] when we have 10 cck fields in a content, plus the user need to know the name of all fields.
So i have a book node that i'll insert into another contet (that is not into a book and is not related with one). I don't want for inserted node to have navigation at all. And i don't understant why a node that belongs to a book when i insert it into another content has to have navigation.
I tried [node:123 content] but the navigation book of inserted node shows.
I tried also what you recomanded to me but it doesn' filter (i see [node:123 cck=body;] in view mode).
Another issue is with teaser of cck field that has as first content an insert node. It truncate html code, not text, div doesn't close normally and ruins the design of page.
I'm sorry for my english.
Thank you very much.
Comment #5
AlexisWilke commentedlilyzm,
Unfortunately, books are a special case.
Did you try with this?
[node:123 cck=body; cck=book_children;]
It should give you the body (description) and the links to the children pages, but no navigation (i.e. no previous/up/next link at the bottom).
And yes, you can create node 456 with the tag [node:123 cck=...] and then later insert node 456 with [node:456] and you won't get the navigation.
Let me know if that works better for you.
Thank you.
Alexis
Comment #6
AlexisWilke commentedLilyzm,
Have I solved your problem yet?
I would think that all the CCK field would be included automatically with the body, but I may be wrong. I'd have to test again. Now, with books you cannot use the body... Hmmm....
Also, you mentioned the teaser, I don't recall creating the CCK teaser feature and the main teaser should be cut properly. If not, then it's strange. As far as I recall, my teasers are properly cut at tags end.
Thank you.
Alexis
P.S. Did you really put the semi-colon in [node:123 cck=body;] ? You may want to copy and paste to make sure... The missing semi-colon is the most likely reason for the filtering to fail.
Comment #7
AlexisWilke commentedI will assume that this was fixed. It works for me. 8-)
Thank you.
Alexis
Comment #9
khaki commentedhave anyone of you tried to remove some extra tags (ex.
tanx,
khaki
Comment #10
AlexisWilke commentedkhaki,
For CKK fields, you can override their CSS. I have no clue how, but I'm sure you can find that information somewhere on Drupal.
Thank you.
Alexis Wilke
Comment #11
khaki commentedi have no problem with the cck or their css... what i want is just remove those tags that are being generated by the module itself (insertnode) :(
Comment #12
AlexisWilke commentedkhaki,
Most everything in the InsertNode module is inserted using a theme() call. So you could override those too. But that could prove difficult if you want to insert this here and that there...
At this point, did you test with the 'plain' flag?
[node:123 plain cck=field_foo;]Thank you.
Alexis
Comment #13
khaki commentedthat's not working... :(
Comment #14
AlexisWilke commentedkhaki,
I will assume that you had the ';' which was missing in my previous post (which I now fixed.)
Could you post what the HTML output is? Write it between <code> and </code> so you don't have to escape the < and > tags.
That way, I will see exactly which tags you are talking about.
Thank you.
Alexis