Recently Browsing 0 members
No registered users viewing this page.
Based on the structure below, "employee", "department" and "year" are simply place holder "pages". Each have been assigned a blank template and contain only a title field which is required. They serve no other purpose.
The issue I was seeing is that I could access these pages in the url directly. For example, root/location1/employee/ would simply display a blank page. This is undesirable for me as it made me fell empty and marking the page as hidden in the back-end did not resolve the issue. So I saw the option unpublished in the back-end and it works perfectly.
I then found Ryan's post here which explains a lot but this example I think deserves its own topic. Would my handling of this be considered advisable or would something else be a better solution, like a 301? I noted that marking a page hidden excludes it from the find() method, but I simply grabbed the children by their templates.
-- John Doe
-- Confused Department
--Even More Confused
Thought I'd point out a fantastic resource for placeholder images. Rather than the usual grey boxes or kittens...
The usual /300x400 urls apply.
Also if you want to avoid seeing the same images crop up again and again, you can use a tiny js file
You won't go back!
Can I specify default value for certain input field?
<h1>Title</h1><h2>subtitle</h2><p>article content</p>. in body InputField.
Maybe custom module?