Open question for Boonex staff
sammie
posted 3rd of July 2008
in
Community Voice.
16 comments.
Can someone at Boonex explain to me why you do not apply the bug fixed to the present download versions of dolphin?
i.e the blog date bug that was mentioned and the fix for it, posted, but this was not applied to the current version, so a month later we have 40 forum threads or blog posts moaning about the same bug
this bug:
'_day_of_1' => '{0} January, {1}',
'_day_of_2' => '{0} February, {1}',.......
if the fix was applied to the current download, it would save 40 useless posts, it would save 40 members frustration. and most of all
it would save people posting other threads like "Dolphin is crap" or other follow on negative posts that we have seen plenty of.
if a bug is reported and fixed, i see no reason to keep allowing people to download and install a version that still has the same bug in it, when the fix has been done and tested and works.
if it is to keep the versions in order, then you can keep a master copy of the version, as i am sure you do anyway. but applying the fix to the current download in my eyes would limit a lot of frustration of members, limit a lot more of the negative comments about dolphin and the Boonex team. and if really needed, then you could add a letter to the version number to keep track of the added bug fixes like:
6.1.2.a
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
The new Dolphin solution is powered by UNA Community Management System.
_day_of_1' => '{0} January, {1}', '_day_of_2' => '{0} February, {1}',....
it was included since publishing 6.1.2
<p>
NOTE: After running upgrade script please check your site homepage. If you have errors on the page like missing language strings, e.g. '_day_of_1' on events or blogs block, follow the following steps:
a) Open the file file upgrade.php see more
Change English to en then what? run the upgrade.php again?
Every upgrade I have done and read they all say run upgrade.php only once or it will break your database. I know I could delete it restore it make the en change and try again, but how many people would actually understand that.
Unless this one wont break your database by running it twice.
Just a thought.
I see more
b) Remove following line: .......
execSqlFile( './upgrade.sql' );
you are only running the upgrade on the system files not the database again, so it does not bread the database.
its the database that breaks if you run it twice.
mrpowless has a tutorial on how to get the new pages built through dbase injection, but this should have been fixed on this 6.1.2 release.
also, i still see a lot of people complaining about 1942 on the registration. i personally have not seen that, but also understand see more
And you are absolutely right about finding out if the thumbs down have ALL been coming from the same ip which I think a lot of us would be surprised that they see more