How can I change the homepage for a plone site?
The closest thing I can find, is default_page under /portal_properties/site_properties in the ZMI. But it lists index.html and index.htm, which I find very confusing since there aren't any html files in a plone install.
On siteroot add a contenttype 'Link', enter a title of your choice and set the destination to '/yourSiteId/yourSubfolder', make sure it is published, set the Link as default-view of your site.
In the subfolder set the content-item as defaultview.
The "display" dropdown menu includes "select default item" which can be used to choose the object you wish to display as the default view of any folder in a Plone site, including the home folder.
You might want to check out Collage. You can define a layout and then pick content items from any sub-folder and have it rendered within your collage layout. You can then select your collage as the default view of your plone site (by selecting it as the default view).
The user interface for collage is a bit daunting but you should be able to get it after some trial and error.
Related
I'm trying to theme a Drupal site.
From what I was reading, if I have page--front.tpl.php, it should work for the homepage.
However, it doesn't seem to work for me.
From themer info, it is suggesting the file name to be page--node--6.tpl.php, which works, but I don't want to hardcode the id number.
Also $is_front is always coming back false.
For this node, I created a "Page" content type and select "bring it to front" and also set in site information for this node, which I alias to "Home" to be the default page.
Still not working. What am I missing?
Thank you,
Tee
If you have in page info
Default front page: node/6
then you could use page--front.tpl.php to theme the node as the front page, it must work.
Check you have the page--front.tpl.php in the correct place, in the
theme folder of the active theme.
Flush caches.
I have nested folder structure.
I'd like to have the splash page of a folder (site section) come from another folder (blog).
However, by default Plone does not seem to offer this functionality. Is it possible to enable default content view behavior for folders in the settings or does it require monkey-patching?
What pitfalls enabled this might include (regarding breadcrumbs, paths, etc.)
Just go to:
ZMI -> portal_properties -> site_properties
edit the property default_page_types and add a new line with "Folder".
This will allow you to select a subfolder as default view for your folder. I made a small test and I can't see any pitfall, it behaves just like any other default view.
I created a Page Template in the Custom folder using the ZMI.
I copied it using the ZMI into an existing Plone Folder.
I would like for this Page Template object to be visible in the Plone Contents tab. What must I do?
If the template is not a view for other content (i.e., it stands on its own), then:
1) Create a folder (in Plone) to contain the template. This folder will show in navigation.
2) Put your template into the folder (using the ZMI) and change its short name (ID) to index_html. That forces it to be the default view.
3) Don't put anything else in the folder. At least not anything for which you need Plone's editing, navigation or view machinery.
OR, if you're allowing the link type to show in navigation, just put in a link type and point it to the template. Much safer than the index_html recipe.
Create a folder in Plone.
Add /manage_propertiesForm to the url and add a new property layout with as value the id of your template (which can remain in the custom folder).
Your template is now the default view of this folder.
we have created new content type for this issue.
i tried to configure my imagecache..installed n enabled the module..now i created a cck for images..and set its test mode display as thumbnail preset linked to the node..
now when i am trying to add content to it, its not displaying the content on the node page.
I solved problem,;) when I activated the "ImageAPI GD2" package under the ImageCache module activation form (admin site building).
There are a few things you can check:
Go to /admin/content/node-type/YOURNODETYPE/display and make sure the image field is visible both in teaser and full view.
Make sure proper permissions are set for the files/imagecache folder (the files folder is usually located in site_root/sites/default/)
Check if the image shows up when you are on the node edit page
To use image cache you need to check three things.
check right php extension(GD) is installed
check your folder permission(generally sites/all/files)
ckeck permission for the field is given for drupal
I've assigned a page from Pages module as home page. And now the main menu shows the menu item called 'Main' which leads to '/main' page. How can I change that to make the 'Main' menu item link to really '/' of the site ?
Updated:
Sorry if it is not clear, the 'page' i mean is really a page - ( Site building -> Pages ).
If you go to the Site Information section of your admin panel, you can set a specific node to show up as the front page. I would use the node/XX way of referencing your node, since the alias you gave the node ("main") may change. Once you've done that, you can change your menu link to go to <front>, which will automatically send it to whatever node is designated as the front page.
Got it.
If I mark a 'page' as to be the front page of the site, and it has a menu item, this menu item leads to something like '/main', but not the '/'. To fix it I removed any menu reference on the page properties and then in the menu editor add the required link with the path ''.
Thanks for the response!
On top of what everyone else has said, can I just let you know of a mistake that I made.
I had pathauto switched on, but it was set to delete old path and create a new path if the title of a page changed.
And you know what, this happened to my home page, so where the page I'd over ridden and called homepage, was now called welcometothisthatortheother (if you know what I mean).
My advise if your using pathauto is to use the nid value ( node/11 ) or make sure unlike me, that you only create new paths on page inserts rather than updates.