Juergen Posted August 21, 2016 Share Posted August 21, 2016 Hello @ all, I have very strange error messages if I want to render my body field in a template. First of all: This happens only if I am not logged in as administrator and only for the body field. If I am logged in with superuser rights everything seems ok. Here are the error messages from Tracy debugger: Has anyone an idea what the cause could be? Best regards Jürgen Link to comment Share on other sites More sharing options...
Webrocker Posted August 21, 2016 Share Posted August 21, 2016 Hi, Does the page/template in question has the view permissions set for the guest user? Seems like the check for the right permission goes wrong. According to the debug code, if you are logged in as a super user, this check won't happen -- this would explain why it works if you're logged in. cheers Tom 1 Link to comment Share on other sites More sharing options...
Juergen Posted August 21, 2016 Author Share Posted August 21, 2016 Hello Webrocker, I think it has nothing to do with the page/template because if I remove the body field from the template the page can be viewed without problems. It is only depending on the field. Link to comment Share on other sites More sharing options...
horst Posted August 21, 2016 Share Posted August 21, 2016 Have you checked the access settings for the field too? 2 Link to comment Share on other sites More sharing options...
Juergen Posted August 21, 2016 Author Share Posted August 21, 2016 Of course. This was the first that I have done. Link to comment Share on other sites More sharing options...
Robin S Posted August 22, 2016 Share Posted August 22, 2016 Best thing would be to strip it back to basics to try and narrow down the problem: Remove any textformatters applied to the field. Try removing all the content from the field. Try the simplest template file possible, that just echos the field with no prepended or appended files. Try adding the field to a new template that doesn't contain any other fields (besides title) and see if you still get the problem there. 2 Link to comment Share on other sites More sharing options...
Juergen Posted August 22, 2016 Author Share Posted August 22, 2016 I have created the exact same field and added it instead of the body field. Now everything works fine. Unfortunately I was not able to trace down the problem according to the tipps of Robin S. Thanks all for your help. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now