Re: Portlet titles gone in J2-M2?
Hi Frank, If you run J2 on locales other than en_US, it might occur.. After M2 release, I have fixed the portlet title handling issue. So, I think you can see the fix on CVS HEAD right now. Thanks, shinsuke > To all: > > Is it just me, or did the portlet title functionality get bugged out between > release M1 and M2? > I upgraded my installation of J2 and now all my portlet titles have vanished > ... they display > empty strings ?!? Of course perhaps I screwed something up during my upgrade > process. Just > curious if anyone else out there is experiencing the same issue. > > - Frank > __ Do You Yahoo!? Upgrade Your Life http://bb.yahoo.co.jp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Portlet titles gone in J2-M2?
Frank, I have heard there were some issues that cropped up right around the M2 release regarding titles. How are you defining them? In portlet.xml? Randy Frank Villarreal wrote: To all: Is it just me, or did the portlet title functionality get bugged out between release M1 and M2? I upgraded my installation of J2 and now all my portlet titles have vanished ... they display empty strings ?!? Of course perhaps I screwed something up during my upgrade process. Just curious if anyone else out there is experiencing the same issue. - Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Portlet titles gone in J2-M2?
To all: Is it just me, or did the portlet title functionality get bugged out between release M1 and M2? I upgraded my installation of J2 and now all my portlet titles have vanished ... they display empty strings ?!? Of course perhaps I screwed something up during my upgrade process. Just curious if anyone else out there is experiencing the same issue. - Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: Adding new user with the admin portlet
Hi, on thursday I asked the question below about adding a new user using the admin-portlet. But unfortunatly so far I got no reply. Also I asked, how I can tell torque (using 'maven torque:om') to use a different package name (instead the default package name 'org.apache.torque') when I create the OM-classes for my database-schema (after I ran 'maven torque:sql')? Maybe somebody can help me with either one or both of my problems? Thank you very much, Sven. --- Weitergeleitete Nachricht --- Von: "Sven Richter" <[EMAIL PROTECTED]> An: "jetspeed-user@jakarta.apache.org" Betreff: Adding new user with the admin portlet Datum: Thu, 07 Apr 2005 16:42:18 +0200 Hello, I'm using Jetspeed 1.5 with the Maven-plugin. I used the admin portlet to add a new user. Now I don't know where the information for the new user is stored (I thought in the psml-directory; so I copied it into the src/webapp/WEB-INF - directory of my application). After I did a 'maven clean', followed by a 'maven jetspeed:deploy' the new user is gone again (I can't login as the new user and the new user isn't shown in the admin-portlet anymore). So which files do I have to save before 'maven clean'? Thanks a lot, Sven. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
custom skins advice - background color
I'm using 1.6-dev, and creating some custom skins. All works fine so far. I do have a question about this. First some data: My local-skins.xreg contains something like: The 'background-color' property causes both the background color of a portlet, and the background color of the entire page to change, in the final HTML I find: The main cell which contains the portlets: And the portlet content cell: However, I want to change the background color of the portlet to white.. The logical step would be to alter the PContent class, but this is overridden by the inserted style-attribute in the HTML above. Now I'm stuck with editing the jetspeed.vm templates which render the portlets. Advice: I would advise that this entire mechanism to be changed, to use the full capabilities of CSS. For example, I'd like to see something like this: Here, the 'PContent' class overrides the 'general' class (space separated classes). This will eliminate all the inserted style-attributes in the tags, and make much cleaner HTML and VM-templates. However, in that case you can't define these properties in the skins xreg file, but you'd have to define these in the CSS file. Also, it would make styles less customizable from the portal website.. Any ideas? Roel PS I guess I have to post this to the other mailing list.. oh well. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
