Posted by kirkcaraway on September 23, 2010 at 1:10pm
For a variety of reasons (mobile posting via blogapi, simplified workflow) I would like to remove the teaser field from my article nodes, and use the standard node teaser instead.
But when I remove this via Views, I get this instead of a teaser:
< class="views-field-"> < class="field-content">
I first ran into this problem on OP 2.0, and was told it was a bug. I just installed the new 2.2 version, and the bug is still there.
I have gone through every theme file, and can't find where this is coming from or how to change it. Any help in finding this would be greatly appreciated. Thanks.
Comments
I also have this glitch, but
I also have this glitch, but it only appears for certain classes of users/roles. Non-auth and Auth are okay; Admin Account (#1 account) is fine. Other roles seem to be stuck with this on the main front page and other pages with lists. Blogs, Multimedia, and articles, it doesn't matter - but only for certain roles, even if those roles don't have added permissions. In other words, I created a new role, added it to an auth-user with no other roles and for whom this glitch did not appear. Now it appears even though the role had no added permissions.
I really love OP, but it seems as if it is over my head. It was working fine earlier this summer and now I'm stuck having to go into offline mode. Is there an easier alternative? I wish I had a lot of money to pay someone to do this for me, but I don't. I'm just a teacher trying to make a school newspaper online - I'm also doing the print version, so getting stuck in these things is just killing my project.
Please help! I love lost the node title for blogs and now I've got this for any roles that are not auth or non-auth.
For me, it shows up for user
For me, it shows up for user 1 and all other roles.
In my case, it is only
In my case, it is only happening on the Front page and say the "articles" or "blogs" pages. The individual nodes don't have it.
@kirkcaraway, who said it was
@kirkcaraway,
who said it was a bug? I would be surprised if it was somebody from OP dev team.
If you change a view you should change a views template that renders it, as well.
This is not a bug. It's a theming issue. You need to make appropriate change in your theme.
Thank you.
.............................................
http://twitter.com/inadarei
Thanks. Here is the previous
Thanks.
Here is the previous thread discussing this problem:
http://groups.drupal.org/node/66118
I don't know if the person who said it was a bug is a member of your team, but he was the only one who answered.
I know the problem rests in the theme, but I have been over every theme file and cannot figure out where this is coming from or how to fix it. Any clues on where I should look?
Thanks.
@irakli, When you say, "It's
@irakli,
When you say, "It's a theming issue. You need to make appropriate change in your theme," I appreciate that this is structurally the case. My problem is that I wasn't looking to mess with the view: this problem emerged when I did an update, but because only some roles are affected I did not notice it right away.
I appreciate that this is something that I should be able to fix, and may have caused, but given the exact shape of the problem I'm not sure what to do. I've tried creating new roles with no added permissions and the problem persists.
Perhaps there are issues with the theming template -- but I am unaware of how that might work with "roles" -- especially since I'm not asking for it to do that and as far as I know no other functions are affected (again, that I know of). That you point us to that is helpful, and I'll investigate it, but alas I'm not sure what I'm looking for... (that's never stopped or inhibited me with Drupal before, so I'm not afraid of trying to decode it on my own, as illiterate as I may be)
Right now, I've decided to just stay with two roles: auth and non-auth. This is a disappointment, since I was relying on different roles to preserve a kind of editorial hierarchy while still allowing authenticated users to have a slightly upgraded experience than the non-auth visitor to the site. In the absence of being able to use roles, I have to restrict account access as a way of simulating the hierarchy of writers and editors I had been working with.
Once I find a solution to this problem, I can resume building the social architecture of the project -- but like kirkcaraway I cannot figure out what is governing this, and assuming that I can, why is it not happening globally, but only to certain users.
If anyone can give me some clues for what to look for, or even a link to any documentation it would be much appreciated. I guess I need to return to Views and the templates.
Thanks to the team for all that you're doing. I've been working with Drupal for a 3 or 4 years now, and basically I teach myself what I need to know. The advent of OP really changed things for me -- pushing me into realms of Drupal and the like that are way over my head. It's worth it, even if a struggle for me. So, thanks again.