I assume that the manpower situation has not changed. But I have implemented it and can therefore provide some info.
In my mind it is no good idea to split this work up. It is better to have one person doing it all - and if in trouble - let another person do the quality check.
It kind of takes one persons concentration (lots of meetings in the middle of the process only breaks concentration).
The implementation:The implementation does take more than 45 minutes. I would say 2h is more realistic if you do the quality check.
It takes
a person that has access to the phpbb files on the server. You will have to find her/him
( I am sure there are problems with that; but that is what it takes)
It requires some PHP knowledge even if the "monkey see monkey do" method will work if you do it exactly as described. That will leave you with no option to check for errors though.
It can be done on a "live" board.
The mod works fine on phpbb 3.0.12.
It involves changes to the database. Easily done in phpmyadmin in 5 min.
It needs changes for
every language that you are using.
In my case it was only
en and
en_us but that might be a very different cup of tea here.
It does
not require access to the phpbb ACP (phpbb Admin).
Setting it up:Requires access to ACP (Admin)
You need to refresh the style themes and imagesets (prosilver)
you need to purge the cash
Then you can set the forums that should have the topic solved regime. You have various options:
You can let the topic solved marking lock the topic automatically and it will reopen if the topic starter clicks the "unsolve" button.
You can divide these functions between starter and moderators +++
You can search for unsolved topics on various levels - it is quite flexible and probably a moderators dream.
When finishedThis is where the bug-hunting begins:
Even if you have done everything right; you will not have it visible in the forums you have set up to use the topic solved mod.
There are various "I cannot see the solved button" threads out there.
Do not panic and start all over again - this might be fixed by clearing your browser cash.
Better yet; open another browser (I use
luakit) or have someone else testing it.
Do you really want and need this?You are welcome to check out the functionality
hereDescription of how it works
hereI agree with the Doctor that this would be a good thing to have here.