After upgrading Node Teaser to version 5.x-1.2, whenever I create a new node "n/a" appears in the body field on node/add/* pages. A minor issue because it can be deleted easily, but an issue nonetheless.
After upgrading Node Teaser to version 5.x-1.2, whenever I create a new node "n/a" appears in the body field on node/add/* pages. A minor issue because it can be deleted easily, but an issue nonetheless.
Comments
Comment #1
nancydruCheck that the input format that is being assigned is available to the person seeing this.
Comment #2
jackalope commentedI'm experiencing the same problem after upgrading to 5.x-1.2, and I've verified that the assigned input format is available to the user.
Comment #3
ericclaeren commentedHaving the same problem, installed 1.1 and that works, 1.2 doesn't work correctly with fckeditor
Comment #4
Pedro J. Fernandez commentedFor me is "n/d". May be it appears when the user doesn't define a text for signature?
Comment #5
Pedro J. Fernandez commentedThe signarute doesn't appear. Only the "n/d".
Comment #6
gatiba commentedSame problem here: n/a on body with 5.x-1.2...
Comment #7
nancydruSee comment #1. While I think this is not being handled in the best way, it is not inappropriate.
Comment #8
wouter99999 commentedI've the same. The input format that is being assigned is available to the person seeing this, so that is not the problem.
Comment #9
d.sibaud commentedsame problem with fckeditor installed
Comment #10
spookypld commentedgot this too
my uid=1
Comment #11
foripepe commentedI think the problem comes from here (nodeteaser.module / nodeteaser_nodeapi()):
Short fix: Comment out the node_prepare() function.
Comment #12
jonskulski commentedThat is indeed where the n/a shows up. nodeteaser calls node_prepare which does:
and check_markup returns t('n/a') if the first argument is empty.
@NancyDru
The check that fails is
so you're right that the filter_access might fail, but also if the $node->body or $node->teaser is empty, then we will see the n/a as well.
I am using the bio module for a site which do not have a $node->body.
I am not sure the correct action here.
@Pedro: Are you using translation? That is probably why n/d is showing for you?
Comment #13
nancydruIn either case, I think "n/a" is not inappropriate. And, at any rate, this a core issue and not this module's.
Comment #14
vsemykin commentednodeteaser.module / nodeteaser_nodeapi()
nodeteaser.module / _nodeteaser_load
Comment #15
carpClash commentedI remember having the "n/d" issue on nodes and also that I could fix it in a minute by rebuilding permissions. Hope this help someone since I came up here looking for the fix described.