Tracker log

Issue state: In progress → Resolved.
Target release: → 0.2.
Added 1027 day(s) ago.

Issue state: Confirmed → Resolved.
Target release: None → 0.2.
Added 1027 day(s) ago.

This can be achieved without content type customization by adding Action Edition to portal_properties/site_properties > default_page_types. That's a global setting so it makes an edition usable as default page for any folderish ATFolder-derived content.

Unless a different solution is required, I will add this to the install script.

Issue state: unconfirmed → open.
Severity: Important → Medium.
Target release: 0.2 → None.
Responsible manager: (UNASSIGNED) → saffe.
Added 1696 day(s) ago.

For a simple action, I think I want to make my Action Edition selectable as the default page for a Campaign Action. Right, the Action Edition content type is not available to be selected as a default page. I think this is a trivial change to the Archetype.

This would allow me to construct a single-edition action that dumps users directly onto the petition page.

Added 1697 day(s) ago.

This is now fixed in trunk & 0.2 branch (bundle as well). Thanks to Sisi, Debra and Pete from Friends of the Earth International (http://www.foei.org) who dig into the issue and came up with a fix.

Issue state: unconfirmed → resolved.
Added 1697 day(s) ago.

Here's a description of the issue and a solution:

1. when the install code checks for whether a particular (countrycode) value exists in a property sheet ("country_lists"), it extends the check to site root (by acquisition) if a country code property does not yet exist. Thus if it finds a match (such as a folder with an id of "en" or "fr"), some properties do not get added at install time.

2. At runtime, as those properties are used, some of them are not found, resulting in an error.

This only happens if, at the time of ectool install, there is two-letter content at root whose id(s) match(es) a country code. As a workaround, the missing necessary properties can be added manually.

Added 1697 day(s) ago.

Issue state: open → resolved.
Added 1778 day(s) ago.

The point of this issue was hiding types from Anonymous view. That being implemented, closing this issue. For follow-up on workflow-based control of type visibility, please see #12.

Issue state: postponed → open.
Added 1778 day(s) ago.

A specific workflow to accomplish:

- ability to hide particular content types from Anonymous (Action Steps, Layout Elements, HTML/Field Blocks, Targets, Action Message, Thank You Page, Thank You Email)

- others?

Added 1778 day(s) ago.

Now usable

Issue state: in-progress → resolved.
Added 1792 day(s) ago.

Issue state: in-progress → resolved.
Added 1794 day(s) ago.

Issue state: in-progress → postponed.
Added 1794 day(s) ago.

Issue state: in-progress → resolved.
Added 1794 day(s) ago.

Issue state: in-progress → resolved.
Added 1794 day(s) ago.

Issue state: postponed → in-progress.
Added 1800 day(s) ago.

Grouping or association of editions with a larger context can be done in different ways. Using a "bottom-up" reference from edition to parent action was the initial way this was implemented, but it might be a good idea to explore for example keyword-based grouping as well.

Issue state: open → postponed.
Added 1800 day(s) ago.

Implemented in 0.2 branch for all but HTML block (no help configured for that type)

Issue state: in-progress → resolved.
Added 1800 day(s) ago.

Issue state: open → in-progress.
Added 1800 day(s) ago.

Issue state: in-progress → resolved.
Added 1800 day(s) ago.

Issue state: in-progress → resolved.
Added 1800 day(s) ago.