Inserted node gets cached?
capellic - July 15, 2008 - 19:26
| Project: | InsertNode |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
I am including a node inside another - I love this idea - thanks for the module.
But I am having a problem any time I go to update the inserted node. If I update the node that is being inserted and then view the page that is inserted the node, the changes don't take effect.
I checked into the node_revisions table to be sure that the the the inserted node wasn't being pulled into the node - I see that [node:999] is still there.
Then I went to the cache_page table - that is empty.
Any ideas?
#1
I gave up on this module for a bit and decided that I was going to build a single node view that would accept the node ID as an argument and then use view_insert module. A created a view that accepted a node ID and then added the insert code into my node body right above the [node:999] code. When I hit refresh, both nodes showed up (as expected). What wasn't expected is that even the node that was included with InsertNode was up to date! I played around around a little longer and realized that by simply having insert_view enabled and the filter set to allow for insert_view, that would flush whatever cache is happening with InsertView!