Ticket #1207 (closed enhancement: fixed)

Opened 14 years ago

Last modified 9 years ago

Action to modify the portal front page

Reported by: lregebro Owned by: fguillaume
Priority: P3 Milestone: CPS 3.5.1
Component: CPS (global) Version: 3.3.8
Severity: normal Keywords:


Several of my friends has complained that it's hard to change the front page in CPS. There is a link in the default frontpage text, but after you delete this it's hard to get it back.

I suggest a "Modify frontpage" Action, that is displayed for managers along with the other management actions.

Change History

comment:1 Changed 14 years ago by ogrisel

As of the full portlets merge (> 3.3.8), this is now just a regular text porlet with a guard. The regular portlet configuration page might thus be enough.

comment:2 Changed 14 years ago by lregebro

Yes, if you know it is a portlet and which portlet it is. That took me ten minutes to figure out. New users that are not used to CPS has no chance to figure that out by themselves.

An alternative is to have a link on the "Reconfigure portal" page as well. But I think that would be more tricky. Maybe there are other better ways. But requireing that users figure out that you need to change a particular portlet is not goo enough.

comment:3 Changed 14 years ago by jmorliaguet

if there's a pedagocial function in the introduction text then it is better to write:

To modify the text on the front page, click on the "Manage portlets" action, ... 

than to have a direct link.

comment:4 Changed 14 years ago by ogrisel

The default portlet view is plain WYSIWYG: it is quite intuitive to click on the portlet you want to modify and then you get the drop down menu with the 'modify' option. What more do you want ?

The default text is the 'welcome_body' msgid which is translated in the CPSDefault's .po files. Maybe this is the very point that confuses your user. We could have i18n aware portlets with a link to the localizer UI to be able to customize the translation of a text portlet. Or even a translate action for portlets that stores the translations inside the portlet instead of using the translation_service.

Anyway, +1 for the pedagogical text but you need be manager at the portal level to see the "manage portlets" action. Thus the text should be something like :

"As a Manager, click on the "Manage portlets" action, to modify the text on the front page."

comment:5 Changed 14 years ago by fguillaume

Having the portlet content be just a msgid is really not good for users. We want to discourage people from changing .po and using Localizer.

Why not have the install process create the portlet in whatever languages are needed at the install and insert the translation at that stage?

comment:6 Changed 14 years ago by ogrisel

+1 for copying the ouput of .po's files into the text portlet object at install time.

However we loose the i18n of text portlets unless we extend them to host multiple translations and display only the one of the current user's language setting. But since the number of languages may vary, this might be tricky to implement (flexible text fields for portlets anyone ?).

Or we could use several text portlets: one for each translation and use portlets guards to display the one that is relevant to request.

comment:7 Changed 14 years ago by fguillaume

Isn't a portlet a cpsdocument? Ah maybe they don't use proxies, true...

comment:8 Changed 14 years ago by fguillaume

  • Milestone changed from CPS 3.4.0 to CPS 3.4.1

comment:9 Changed 14 years ago by lregebro

From a discussion on dev: "We should use a document portlet that points to a webdocument to build the homepage."

I also still think there needs to be a "Edit frontpage" action. It is NOT obvious that you should click on "Manage Portlets". Even less so in 3.4, when you now have to go to the workspaces, click on Manage Portlets and then click on the site root in CPSSkins.

comment:10 Changed 13 years ago by sfermigier

  • Milestone changed from CPS 3.4.1 to CPS 3.4.2

comment:11 Changed 13 years ago by sfermigier

  • Milestone changed from CPS 3.4.2 to CPS 3.4.3

comment:12 Changed 10 years ago by gracinet

  • Milestone changed from CPS 3.5.0 to CPS 3.5.1
  • Summary changed from "Modify frontpage"-action. to Action to modify the portal front page

Never understood why the "manage portlets" actions wasn't present on the root. Should maybe add it. Even with CPSDesignerThemes, this is still meaningful

comment:13 Changed 9 years ago by gracinet

  • Status changed from new to closed
  • Resolution set to fixed

Now the portlets action is present on the root, in the "global" actions category.

Note: See TracTickets for help on using tickets.