Tuesday 23 March 2010 12:13:49 pm
By : Nicolas Pastorino
Time to welcome a brand new feature on the community portal: the "Mark as solved" one !
Whenever someone asks a question on forums (ie: creates a new forum topic), she sometimes gets the answer she was looking for, after some time and collaboration with other fellow community members. By that time, it is convenient for the author to mark the initial post as "solved", clearly notifying anyone browsing the forums that a good answer was found, and that there is no need to help on this point anymore. As well, it helps others having similar questions quickly find the accepted answers.
Here are, at a glance, the new things you may stumble upon when browsing.
When landing on a forum topic, its status ( solved or unresolved ) is visible through the top-left corner icon :
If i am the original author of the topic, i have the possibility to change its status :
The status of topic is then reflected in the parent forum's landing page, listing all topics. All solved topics are pushed to the end of the list, can be deliberately found there for later reference, leaving more room for the unresolved topics.
EDIT: per community's feedback (see comments under this post), the solved topics are not pushed to the end of the list anymore.
Here is what it looks like :
Tell us (the share.ez.no team) if you like it, we love feedback. You can use the comments below to say a few words on how you are using it, or you can directly use the issue tracker (very handy i must confess) there : http://issues.ez.no/ProjectSelect.php?Id=6, to give enhancement ideas, or describe bugs you may have found using the feature (and in a more general way to help this portal evolve in the right direction).
Happy solving fellows !
Nicolas
Timing: | Jan 15 2025 03:24:52 |
Script start | |
Timing: | Jan 15 2025 03:24:52 |
Module start 'layout' | |
Timing: | Jan 15 2025 03:24:52 |
Module start 'content' | |
Timing: | Jan 15 2025 03:24:52 |
Module end 'content' | |
Timing: | Jan 15 2025 03:24:52 |
Script end |
Total runtime | 0.0135 sec |
Peak memory usage | 6,144.0000 KB |
Database Queries | 3 |
Checkpoint | Start (sec) | Duration (sec) | Memory at start (KB) | Memory used (KB) |
---|---|---|---|---|
Script start | 0.0000 | 0.0042 | 686.6484 | 183.7500 |
Module start 'layout' | 0.0042 | 0.0023 | 870.3984 | 52.6719 |
Module start 'content' | 0.0065 | 0.0037 | 923.0703 | 179.2188 |
Module end 'content' | 0.0102 | 0.0032 | 1,102.2891 | 747.7578 |
Script end | 0.0135 | 1,850.0469 |
Accumulator | Duration (sec) | Duration (%) | Count | Average (sec) |
---|---|---|---|---|
Ini load | ||||
Load cache | 0.0036 | 26.7491 | 14 | 0.0003 |
Check MTime | 0.0009 | 6.9824 | 14 | 0.0001 |
Mysql Total | ||||
Database connection | 0.0005 | 3.9145 | 1 | 0.0005 |
Mysqli_queries | 0.0023 | 17.2342 | 3 | 0.0008 |
Looping result | 0.0000 | 0.0672 | 1 | 0.0000 |
Template Total | 0.0029 | 21.1 | 1 | 0.0029 |
Template load | 0.0021 | 15.5589 | 1 | 0.0021 |
Template processing | 0.0007 | 5.5439 | 1 | 0.0007 |
Override | ||||
Cache load | 0.0019 | 14.0320 | 1 | 0.0019 |
General | ||||
dbfile | 0.0002 | 1.1646 | 8 | 0.0000 |
String conversion | 0.0000 | 0.0459 | 4 | 0.0000 |
Note: percentages do not add up to 100% because some accumulators overlap |
Usage | Requested template | Template | Template loaded | Edit | Override |
---|---|---|---|---|---|
1 | print_pagelayout.tpl | <No override> | extension/community/design/community/templates/print_pagelayout.tpl | ||
Number of times templates used: 1 Number of unique templates used: 1 |
Time used to render debug report: 0.0001 secs