I am working on Hippo CMS, which has a plug-in for RSS feed
the RSS can grab documents from existed folders. But I would like to implement a feature to let it grab document from facet but not real folder.So I can do something like news/2012/published to get what I want. Anyone tried this before? Please share some idea about how I can do it.
Yes that should be possible. You could create a hippo:facetnavigation structure and show the tree like that. Next to that you probably need to modify the default RSSFeedBuilder component, so that it can handle this kind of structure.
The RSS feeds on my Hippo based site are based on facets. I'm using ROME to create the feed.
You can find the code that creates the feed on:
https://github.com/jashaj/HippoWeblog/blob/master/site/src/main/java/org/onehippo/forge/weblogdemo/components/FeedCreator.java
I only use these JSPs because the HST component needs a rendering template and the feed needs to have the correct header for the content type:
https://github.com/jashaj/HippoWeblog/tree/master/site/src/main/webapp/WEB-INF/jsp/feeds
Related
I have created one ADT for asset publisher and here im fetching all the documents from a specific folder ,here my problem is that we want to use existing pagination,we have configured the simple pagination, but still the result not coming properly.so is there any alternate way to use the existing pagination with our custom ADT.
Thanks & Regards,
P.v.B.Raju.
As far as I know, there is no way to paginate in Freemarker by default. For custom pagination, you have to override Liferay's core JSP here, which is very unfortunate. If you've found another solution, please share it here.
i'm currently working on a TYPO3 6.2 site using tx_news.
My goal is that a user can use the listView directly to download a related file, like it was possible in TT_news with type download.
The problem is in TX_news is only type news, internal page, external page available.
I dont really want to extend news that much to generate a new news type.
I got two possible solutions:
Use external page as link to file
Problem:
I dont really want the user to type the external file link
into these fields, since its a bigger project with many files.
Use sys_category and link the "more" field to related file
Problem:
I need a hardcoded check in the template files for the "File
Download Category" UID. What if this changes, or in a year some new
people need to maintain this.
This is possible with some template like this, but as is said before, this is an ugly hardcoded check in a template file:
<f:for each="{newsItem.categories}" as="category" iteration="catIterator">
</f:for>
Any help is very appreciated, if someone knows a better, cleaner solution.
To clarify: With 'listView' you mean a list of news items?
If so,
You could add a TemplateLayout to display only the URLs of the related files.
tx_news provides the news type "Internal Link", too.
With this type, it is possible to create a direct link to a file (on your webspace), page, folder or email.
HTH.
I'm using Typo3 for the first time and have been asked to update a site built on it.
Making changes to existing templates so far has been OK since they were mainly CSS changes or replacing images. Now though I need to create a couple of new page templates.
What's the easiest way to go about this? The existing site has a home.html and layout.hmlt in the fileadmin directory. Do I need to create a new html file there, if so how do I use this as a new template for some of my pages?
I'm coming from a mainly WordPress background in terms of CMS (I've nearly given in a recoded the site as a WordPress site since I think it would be quicker at this stage) but I'd really prefer to figure this out.
Any suggestions would be greatly appreciated as I'm pulling my hair out trying to read through the documentation and getting nowhere. The site is using Typo3 version 4.4.6
Thanks!
How you add a new template to your page depends on how templating is handled. Sadly TYPO3 has a poor templating out of the box, so there is most likely an extension that does the job on your site.
Probably one of these:
automaketemplate
templa_voila
flux & fluidpages
Check if one of these extension is installed and add a new page template according to the extensions manual or specify your question afterwards.
Edit:
If plain TYPO3 was used, you'll find something like
page = PAGE
page.10 = TEMPLATE
page.10 {
file = fileadmin/myTemplate.html
}
in your Typoscript. You can add tmplate files like the ones that are already there. To use a different template on a page, you have to replace the page.10.file with the template you want to use. This can be done with a new template record (crated in backend via the template module). But this is a rather anoying procedure to change the template, because you have to create each time you want to change the page template for a page and its children. That is why mostly extensions are used for this.
The out of the box situation gets better with newer TYPO3 versions but in 4.4.6 there are no Backend Layouts that could be uses for a template switch ot something like that.
In Addition to change the mere file you have to adjust the subparts or marker that are filled with the content. You'll find that configured in your TypoScript as well
On a website, I have a section where I put a new page every week. I'd like to convert this to a system using tt_news. How do you suggest me to import the pages (more than 100 pages) to tt_news? Can I do it using a simple SQL query, or should I write a custom PHP script to perform the importation? Is there already an extension that exists that could help me performing this task?
It doesn't really matter to me if I simply build news liked to existing pages, or if I transfer the content of the page to the content of the news. It would be great if I can convert the page title to the news publish date, but I could use the page publishing date as well.
What do you suggest for performing this task?
I would do it via SQL as you mentioned already. Could get tricky if you have multiple content-elements per page that needs to be merged into one tt_news-dataset.
You could also install an extension, that links tt_content-elements with tt_news-records. This way you only have to insert the tt_news-records by traversing the pages and link the content per page to the new tt_news-record. Here are some extension, that link tt_news with content-elements:
ttnews_irre
aba_ttnews_content_con
Here is also an extension that could be worth a look: content2news.
Hope this is useful to you.
Best regards,
Peter
I was wondering if page templates can be built instead of individual components in Teamsite 7? I've seen other cMS systems where it is just a page template that has lots of functionality built I and you can "switch" on and off elements that you want to display instead of having to drag components onto a page? Is this possible?
Old question, but since I just came across it:
Yes, TeamSite supports templates (.template) files which can be partial or full page templates. The default location is iwadmin/main/livesite/template.
I recommend downloading the developer guides from Autonomy's web site for detailed information.
Templates in teamsite/livesite is like a bag that can contain components. But in order for a functionality to be developed in teamsite/livesite we need to create components. certainly we can avoid dragging and dropping components in each page by creating templates and dropping components within it for once. Keep in mind templates are bound to layouts. for each type of layout we need to create a template. Please have a look at TS_7.3_SiteDeveloper_rev1, Chapter 5.
Yes, you can create templates instead of dragging components.
Since, TeamSite supports templates (.template) files which can be partial or full page templates and resides at location : iwadmin/main/livesite/template.
So, whenever you try to create a new page everytime the HTML code required for that page gets automatically added with the template and layouts you selected.
But, again this is not good since you can have any number of templates you need but this could create confusions at times when you try to create a new page since you will need to remember every template name and contents that you will need for a particular page so it's better to have small lists of templates and layouts since then we can say that there is reusability in our application/website which we are going to develop using Teamsite and Livesite.
Please vote the solution if its helpful.
Thanks!