How can I embed a theme within a Vaadin portlet ?
I created a theme as described here but at runtime, when I check the HTML source with Firebug, the theme's style returns a 404 error.
How can I include a theme in my portlet correctly ?
Regards.
In Liferay, Vaadin themes must locate a folder under the portal context. For example, Liferay bundled with Tomcat, the default location is:
LIFERAY_HOME/tomcat-6.0.29/webapps/ROOT/html/VAADIN/themes
For more information take a loot at Book of Vaadin, Section 12.5.
Henri Kerola's answer is correct but leaves out a very irritating pitfall. Your next question on stack overflow will likely be: Why isn't my CSS updating even though I put my new theme in
<LIFERAY_HOME>/<TOMCAT_HOME>/webapps/ROOT/html/VAADIN/themes
It's important to know that Liferay 6.1 Caches css from themes in
<TOMCAT_FOLDER>/temp/liferay/css/portal/html/VAADIN/themes/<THEME_NAME>/styles.css_E_DATA
So if you want to change the theme in a deployed instance you need to delete the cached version, otherwise you will spend hours and hours playing with firebug and fiddler and other tools trying to figure out why you are getting the old theme.
Edit: You can also put liferay in developer mode which prevents the caching, which is even better... just pass this in to the java process running your liferay
-Dexternal-properties=portal-developer.properties
Related
We have a Domino 9.0.1 server and we would like to demo the document Library that uses XPages but we would like to use OneUI v2.1's red theme, as it is an almost perfect fit with the company's color.
I can't get it to work. I must be missing something... What needs to be done in order to achieve that, if at all possible? I do have the themes copied in the doc Library, but it just uses OneUIv3's default theme regardless of what I choose in the app properties.
Set oneuiv2.1_red to Application Configuration / Xsp Properties / Application theme in Designer in your database.
This theme is already available on server so you don't need to put it into your database.
Hello
I have a live Magento 1.8.1 site where pagination was working on product list pages (such as category pages) but I’ve been adding and removing a number of extensions / plugins and I’ve lost all pagination. Unfortunately, I can’t remember the last time it was working so I can’t think precisely what extension might have caused the problem.
I’ve checked all the usual fixes such as here but my catalog.xml is fine (and all problems seem to only relate to 1.4 - 1.6). I am reluctant to upload new files which I actually think might fix it but I also know how temperamental Magento is! Everything else is working perfectly for the first time after a month of serious hard work including a couple of reinstalls!
The website is next2new.net and although you can see a custom theme, there is also no pagination on the default magento theme which indicates to me it’s a core problem somewhere.
Any thoughts on any files I could check / change before I do a big overwrite?
Many thanks
Following things you can try in order to Cope-up with this situation :
1) Disable those modules which is overriding Catalog module and check once again.
2) Check whether Toolbar block is calling or not using Template and Block Path hints using Magento Admin.
3) If you are using any template, possibly there could be a setting in Admin section to Manage toolbar.
I have a joomla 1. 7 website and I have installed a widget kit for displaying a slider with buttons on it. It works fine in the backend, however it does not display on the site.
Is there a reason why widget kit is not compatible with Joomla 1. 7?
Without any details at all, I'd suggest a possible conflict with you chosen joomla template and javascript library(s) like jquery or mootools.
Try one of the simple templates that came with your joomla installation and see if the problem on the front end persists.
Widget Kit is compatible with Joomla 1.7, however as Grag P said, it might possibly be a conflict with another extension using Jquery.
Use Firebug and look at the scripts being loaded in the <head> tags and see if there are 2 Jquery libraries being loaded.
If so then the 2nd one is most likely coming from your template in which case go to your template manager and see if there is an option to turn off Jquery, else if its coming from another extension, try disabling it and seeing if this solves the problem.
Also make sure you have the most up-to-date version of widget kit as Yootheme have brought out a lot of updates in the last 2 months.
I have a fresh installation of Liferay on Tomcat and in IE7 it doesn't show the buttons for visual editing in the editor when I try to edit content.
It works on in Firefox or Chrome.
Does anyone have an idea why would that happen? I am not sure where to dig, I don't see javascript exceptions and it doesn't look like the buttons are even populated in IE. It is hard to debug IE problems since I don't have a tool like Firebug there.
I downloaded the 6.1 and still have the same problem, adding the URLs of what I see. Looks like IE only has the text box and in the DOM I don't see the same things that I see in FF.
http://i44.tinypic.com/35jf5td.jpg
http://i43.tinypic.com/11qqvt0.jpg
Update on this:
I checked with some people in our organization and they have the buttons on their browser.
I checked the version of the IE browser and it's the same down to the last digit. Properties are the same as well. The only difference is that I have some plugins installed that the other browser doesn't. I tried disabling all the plugins but it didn't help.
The suspect plugin is Google Chrome Frame (ChromeFrame BHO). Can someone please try to add this plugin and see if it messes things up? The disabling it doesn't help.
Liferay CE 6.0 contains few bugs within the WYSIWYG editor integration.
One issue with IE is LPS-16004 (solution included). This might be the same problem as you are experiencing.
I remember we had also problem with javascript race condition in editor initialization, which sometimes loads the editor incorrectly.
But I strongly suggest you to move to Liferay CE 6.1 as it is much more stable.
Ok, I finally figured it out, so if someone has the same problem, here is the reason - we have Google Chrome Frame plugin installed in our organization, but it only works on white-listed domain names. In this case the domain the site was on wasn't whitelisted, but the portal looked at the agent string and saw chromeframe there and assumed it can use it as chrome browser, which broke things.
Right now I will try to white-list the domain and see if it works. Another solution would be to try and find a place where we look for the agent string and fix it there, not sure where this place is.
I have installed community builder on my Joomla installation. I need to understand the Community Builder templating. I cannot understand where templates are and how can I override them. Can I override them by placing files in my site template's html folder, the way Joomla does or else it gets harder to maintain.
Another small problem: I wanna redirect to the profile page after logging in from the CB login page instead of the page that say Hi %username% with a Logout button.
Thanks for all the help in advance.
I appreciate it.
CB templates are found in the CB plugin manager located through components - CBuilder - Plugin Management, There are a few default templates but most decent ones are commercial, If you happen to find any free ones please let me know.