Increasing the Activity History
Submitted by Legend on Fri, 07/11/2008 - 14:09.
Hi,
I was wondering if there was a way to increase the size of the acitivity history that is displayed on the dashboard and the project page. When I make many modifications, things are getting lost so I would really love to hear how to either display more on the same page, or paginate them so that one can view the entire activity from the beginning.
Thanks a lot!
There is a hidden configuration option, "dashboard_logs_count", which defaults to 15. I'm not sure if you can edit it from the front-end, but you should be able to find the option in the database tables.
If you want to see more logs (out of the box), i would suggest using the RSS feed. The configuration option that uses is, "feed_logs_count" which defaults to 50.
I don't think logs are ever destroyed, so you should be able to see all of them provided you modify the correct option.
The logs are never destroyed and you can technically display as much as you want.
Tim
Hmm... Something seems amiss.. Do you mean I should add that option or find that option in the database? I can't see it anywhere :(
Edit:
So its like I found this option here:
./application/controllers/DashboardController.class.php: $activity_log = ApplicationLogs::getOverallLogs($include_private, $include_si lent, $project_ids, config_option('dashboard_logs_count', 20));Now it works... But something strange is this:
./public/upgrade/templates/db_migration/onion.php:INSERT INTO `<?php echo $table_prefix ?>config_options` (`id`, `category_name`, `name`, `va lue`, `config_handler_class`, `is_system`, `option_order`, `dev_comment`) VALUES (5, 'system', 'dashboard_logs_count', '15', 'IntegerConfigHa ndler', 1, 0, NULL);I can see that it is inserting in the config table, but I don't see this anywhere... Any reasons for this?
My only concern is, hardcoding things isn't such a great idea in the long-term maybe...
In the database, open the pp_config_options table.
Find the project_logs_per_page row, and set the value field to whatever you want.
Bear in mind that increasing this number dramatically might have slow the page load.
It seems that the option is not actually added to the database. That's why changing the argument of config_option() works. This function checks if the first argument exists in the database and if not uses the second.
The second bit you're quoting is from the upgrade script. It looks like the upgrade script has what the installation script should have: addition of the option in the database.
So, at the moment, I suppose you can either change the code the way you did it, or add manually the option in the database following either the values used in the upgrade script or copying what's already in the database. The table for that would be pp_config_options.
Eventually, I guess it should be added to the database during the installation...
Tim
Thank you for the suggestion...
This sounds like a bug that could use a patch...
Sure. I will learn how to develop patches and will get back...
In the meantime (to have a patch), you can run the following SQL request to add the option to the table:
INSERT INTO `your_database`.`pp_config_options` (`id` ,
`category_name` ,
`name` ,
`value` ,
`config_handler_class` ,
`is_system` ,
`option_order` ,
`dev_comment`
)
VALUES (
NULL , 'system', 'dashboard_logs_count', '10', 'IntegerConfigHandler', '1', '0', NULL
);
I set it to 10 here but you can change to whatever you want.
Tim
Apparently, there is another option used for the project pages: project_logs_per_page
In the table pp_config_options of your database, it should be the first option and is set to 10. You can modify it to change the number of items you want to see on the project page.
Tim