I want to get all categories in alfresco. What i want to do is a function that return a tree of all categories in the repository (may be recursively) and display it in category managment page.
I'd like to display the tree expanded by default (using Yahoo javascript library)
Thank you in advance.
I'm using alfresco 5.0.d
You ll want to change the category manager page.
The code for the category manager (front end javascript, Yahoo js library) is in
alfresco\tomcat\webapps\share\components\console\category-manager.js
Css styling is in same dir
The back end webscript that provides the data is in
alfresco\tomcat\webapps\share\WEB-INF\classes\alfresco\site-webscripts\org\alfresco\components\console\category-manager.get.js
The freemarker template providing html can be found in the same directory.
Related
I am working Apache solr search its working fine. But I need to change the search result to my view like title, date, short description and image.
Can you please someone help me. How to override the search result to custom result.tpl page.
There are several options :
Altering/adding template variables for individual search result by implementing hook_preprocess_search_result().
Altering the template file itself search-result.tpl.php (first you need to copy the original in your theme's templates folder).
The same can be done on the entire set of results (rows per page) using search-results.tpl.php & hook_preprocess_search_results().
Add custom CSS or override some rules in your theme.
I am using one plugin known as Wp store Locator which is not based on custom post type.So that plugin gives one list of store as output and it has in built template for it.I have modified that plugin in a such way that on click of More Details it should take me to detail page of that particular clicked store.
I have built link like this localhost/wordpress/?wpsl-id=3.
So my question is that how can I show only on particular store? I have built one template in that plugin but I don't have any idea how can I use that.
Any help from Wp Store Locator user would be highly appericiated.
Hello I am trying to generate a Drupal node which would be similar to a feed page generated by views module. I need to generate an xml feed, so I would not want to show the regular drupal template that is showed up on every node. I am trying to understand how the views for feed works as I want to display my page in a similar fashion, without the drupal template. Any suggestions would be great.
In Drupal you can theme any individual page to be completely different than the default template. So, if you have a node, let's say the url is "node/14", you can create a new template file called "page-node-14.tpl.php" in your theme folder. In this template you can add any html/xml markup you need. Also, for that specific node you should also create a "node-14.tpl.php" to theme that node's content.
If you want to display more nodes on a page, something like "taxonomy/term/3" (here you can find all nodes tagged with the term with the ID 3), you have to create a "page-taxonomy-term-3.tpl.php" template in your theme folder. To theme every node from one particular content type, you should create a "node-news.tpl.php" (this is for news node types) in your theme folder.
Please keep in mind that these template suggestions are for Drupal 6. In Drupal 7, the template name changed from "node-news.tpl.php" to "node--news.tpl.php"
I'm attempting to build module that allows a user access to manage jobs/departments and post them to our website. It will also allow end users to apply for a given position.
The hierarchy is as follows:
About Us Page (standard drupal page)
-Careers (overview with list of all openings)
-Department Pages (if one or more jobs are available, they'll be displayed here)
-Individual Job posting with form to submit resume
I am currently using two custom tables for jobs and departments.
I have all the administration (CRUD) stuff working just fine -- my question lies in the 'drupal' way of integrating the department pages and individual career pages.
Should I create a custom content type that stores all the job/department data in the node? Or should I keep with my custom tables and integrate with the Path module to setup all the department pages and the application page? Also, what would be the best way to integrate the job application form into the module?
I appreciate any help!
You could create a custom node type for jobs and then create a taxonomy vocabulary for careers with terms for departments inside it so that you can then assign the taxonomy terms to a job. That would be very quick and easy to do.
This also means that you could output nice categorised breadcrumbs using the Custom Breadcrumbs module. Custom Breadcrumbs contains a submodule called Custom Breadcrumbs Taxonomy so you could output career/department information in the breadcrumbs.
You could also use Pathauto to output nicely structured SEO friendly URLS using this method.
Edited to say that with this method you could use Views to show taxonomy term specific lists simply by enabling the taxonomy term View, so you could show all openings at www.example.com/careers and all departmental openings at www.example.com/careers/department-name.
I'm just getting round to converting our static HTML website to Drupal. Our website is currently structured into sections, each section having a header, then a list of sub-sections below (for an example see http://www.eurosafeuk.co.uk/services/).
This ties in very nicely with Drupal's "book" module, but I need to customise the display of child pages; by default they're printed as an unordered list of page titles, whereas what I need is to output:
A teaser image for each page
The page title
The page summary
I've looked through the .tpl files, and found that the children are stored in a $tree variable (already HTML formatted). My question is: where do I start if I want to modify this? Does anyone know of a pre-existing module that would do it, or do I need to dig into the code?
Instead of using the Book module which is specifically for a book structure, you might want to look into modules that are made for your case. I haven't looked very well but the Node Hierarchy module might be useful for you. . Here is an excerpt from its project page:
... allows nodes to be children of other nodes creating a tree-like hierarchy of content. The module offers:
1-Click creation of hierarchical menus
Hierarchical breadcrumbs
Automatic hierarchical urls using Pathauto (and token module)
(eg: q=aboutus/history/beginning).
Automatic creation of hierarchical menus if desired.
Optional Views integration.
Optional Node Access integration.
If you want to theme nodes in specific sections in different ways, it's probably a good idea to make separate .tpl files for every section. The way you name those .tpl files makes them applicable to nodes in a certain section.
Get the devel module, and turn on theme developer. This will tell you the template or function which is used to build the HTML and what templates you can create to override it.