Drupal issue accessing custom content type -

-

I have a problem where a standard content type is not unique by standard user accounts and users. The content type is the page (not one but the one I created). There is no special, just static text in it.

When I try and see a page, my title is displayed, but below it, html is not included from tpl. So the problem is not that I get an access denied page. (The text is displayed in the box along the top and bottom of the round corners. The top ones are but the ones below, so I know that the HTML is not showing at all)

This account can access everyone In other content permissions, the access content is definitely checked and I did not get any entry that would determine the simple viewing of a specific content type.

What can be done with it?

If you use the CCK field with your new content type, you will need to re-enter your permissions : CCTV areas should have their own view and editing permissions and by default the most restrictive permissions are missed.

(note: comment has been answered)


Comments

Post a Comment

Popular posts from this blog

MySql variables and php -

-
I am getting an error with php in order to format mysql_query () in php to format this string What is the right way? SELECT SELECT SELECT (*) Agents @AgentCount; User_Agent_English, User_Angent_Oursal, US.___Gent_Aginal, COUNT (User_Agent_Percade) ACC, COUNT (*) / (AgentCount) Percentage by agents user_agent_preser order DEC limit limit 50; In PHP, how am i setting $ query $ query = "SELECT count (*) agents @ agentcount; SELECT user_agent_parsed, User_agent_original , COUNT (user_agent_parsed) ascount, COUNT (*) / (@AgentCount) as a percentage by user_agent_parced by URI date DESC limit 50 "; This exact query will work properly if I put it in MySQL directly through a command line session. Do I need to release two separate php calls from mysql_query () and store the results first? I get the following error: There is an error in your SQL syntax; Instead of using a sub-selection and instead of using the 'SELECT user_agent_parsed, user_agent_original, ne...
Read more

php - Laravel - Overriding a resource route into a different route filter group -

-
Does Laravel's routing work as expected? What I think, if I want to override a route, then I just have to give the expected route before each other. I have something like this: root :: group (array ('first' = & gt; 'defaultLoads' =); function () {root :: post 'Newsletter', 'newsletter controller @ store'); root: group (array ('(newsletter', 'newsletter controller');}}); That if I post this route, only http://domain.com/newsletter should run only the default loads route filter. However, when I call php Runs artisan routes , I get this: | | POST newsletter | newsletter.store | newslettercontroller@ store | default loads | login | | though it reads the route correctly (PHP artisan loads which The correct path is to the right place) but the file of the resource path even if it is not in the filter group, the path is affected. Then my question: How does it work Laravel? If so, do I post this -> Newsle...
Read more

url rewriting - How to implement the returnurl like SO in PHP? -

-
This URL should work even after the rewrite. Is this possible? Otherwise, I can only hardcoded everything If you are trying to create a login system with redirection You need to use the HTTP_REFERER header to find out where the user came from so that you can send it back there. The best way to do this is to use something like this in your login form: // - Login php & Lt; Input type = "password" name = "password" /> & Lt; Input type = "hidden" name = "returnrelale" value = "& lt ;? php echo $ redirectURL ;? & gt;" / & Gt; & Lt; / Form & gt; Please note that some ISP, browser or proxy will delete the referrer header, so you can not rely on each user to work fully. If you use a statement, to check whether the header exists or not, you can send those users back to the homepage or whatever. Edit If you are looking to use $ _SERVER ['REQUEST_URI'], if you are running Apache It sho...
Read more