22 Aug, 2010
1 commit
-
Added delayed_job plugin Added a daemon to start/stop delayed_job Added invitation on a queue to be processed later (ActionItem1640)
20 Aug, 2010
1 commit
-
(ActionItem1608)
15 Aug, 2010
2 commits
-
- Added a new jQuery UI theme - Added jQuery Cookie plugin (ActionItem1412)
-
* addThis * blog-feed-link * article-actions
14 Aug, 2010
12 commits
-
Added setting trusted_sites_for_iframes to environment WhiteListFilter lib to filter iframes from fields Removed "on hand" iframe filter from plugins (ActionItem1631)
-
Also removed the duplication of pagination links methods (ActionItem1588)
-
(ActionItem1588)
-
(ActionItem1608)
-
Implemented cache policy: * the homepage is cached for 5 minutes by default. This time can be configured with the =home_cache_in_minutes= attribute in the environment. * non-profile pages are cached for 15 minutes by default. This time can be configured with the =general_cache_in_minutes= attribute in the environment. * profile pages are cached for 15 minutes by default. This time can be configured in the =profile_cache_in_minutes= attribute in the environment. * The account controller (/account/*) is not cached at all. * The environment administration area (/admin/*) is not cached at all. * The profile administration area (/myprofile/*) is not cached at all. * Since Varnish will not cache any request that involves cookies: * Authenticated users will not benefit from the cache. * Cookies are not allowed for unauthenticated users. So, when a response is being prepared for an unauthenticated user, all cookies are wiped out. The contents of the login block and the login/logout part of the header is now loaded via an AJAX call to /account/user_data. This way we can cache almost all pages without caching user-specific data. We are also changing substantially how the flash[:notice] messages work. From now on, instead of setting flash[:notice], we must set session[:flash]. It will work more or less like before, except that session[:notice] will be consumed by the AJAX call to /account/user_data that is done during all page loads instead of being consumed automatically by Rails. The only exception to this is the media_panel, because it uses a different layout. (ActionItem1608) -
(ActionItem1630)
13 Aug, 2010
6 commits
-
(ActionItem1628)
-
(ActionItem1628)
-
Now the management is paginated.
-
(ActionItem1529)
-
(ActionItem1627)
-
site_title is added by theme favicon is added by theme or profile (ActionItem1529)
12 Aug, 2010
10 commits
-
(ActionItem1627)
-
(ActionItem1607))
-
(ActionItem1626)
-
(ActionItem1617)
-
(ActionItem1588)
-
(ActionItem1622)
11 Aug, 2010
5 commits
-
(ActionItem1620)
-
The access to the feed must be controlled by the content viewer access logic, not by the feed. P.S.: I'm not pretty sure if my solution have performance issues! (ActionItem1619)
-
(ActionItem1614)
10 Aug, 2010
3 commits