Open question for Boonex staff


	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

-1

95 days ago


	This comment is below viewing threshold. Show comment and when are you going to fix the issue with the blogs here that do not put in a new line or two new lines when you hit return/enter once or twice?

-8

95 days ago


	One (first) note - 6.1.2 not need in fixes about _day_of_1' => '{0} January, {1}', '_day_of_2' => '{0} February, {1}',.... it was included since publishing 6.1.2

View 1 replies to this comment

95 days ago


	This comment is below viewing threshold. Show comment i am taking that as an example bug, it was in 6.1 and i also beg to differ on this bug, but only last week i downloaded and installed upgrades of 6.1.2 and patches and i had to run the upgrade again as posted in the Upgrade Instructions from 6.1.1 to 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 in editor. b) Remove following line: ....... execSqlFile( './upgrade.sql' ); c) Find the line: $iLangID = (int)db_value( "SELECT `ID` FROM `LocalizationLanguages` WHERE `Name`='English'" ); Replace 'English' with 'en' in this line. </p> <p> that is direct off the 6.1 to 6.1.2 patch would it not be better to just changes it in the file from the outset?

-5

95 days ago


	After running the upgrade and you have these errors...check your site homepage. If you have missing language strings _day_of_ etc 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 used a couple of files from 6.1.1 to do away with the date_of_1 because I didn't want to run this a second time to see what would happen.

-4

View 2 replies to this comment

DosDawg(positive)

94 days ago


	This comment is below viewing threshold. Show comment i have some of the same thoughts regarding fixing known bugs. mine is with the page builder. you cannot create a new page in 6.1.1 and now after installing 6.1.2 and thinking it would be fixed, well guess what, its not fixed. 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 its present on the events calendar, and in some posts on the blogs. dont know if this has been addressed as getting fixed, but those are some of the bugs i thought would be worked out on this last release. exactly what was or is different about the 6.1.2? did the boonex brands get taken off from the video upload and music upload page? i am going to check that, and see, as i have only one install of 6.1.2 currently. just tell all my clients to wait and see what shakes out for the 6.1.2 before they upgrade. later, DosDawg ps will be back to follow up on this as soon as i check a few things on the 6.1.2 install.

-7

93 days ago


	i see someone has lots of accounts and used them to hit everyone with neg reps. even the people that really do help you. cool. i think we need to see if they all came from the same ip.

93 days ago


	That was me ...i was bored lol...no just kidding

View 1 replies to this comment

Bramin(positive)

92 days ago


	So that's why you have been getting all this negative press, Sammie? Christ almighty I thought it was just a bunch of a holes who didn't or worse yet refused to understand what you were talking about. But you know what they say about getting negative reactions from negative people...that is about the best positive feedback anyone can get! 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 weren't at this point. And if that is the case hell bounce em we don't need that shit! But as for your original question(s) I have no idea either why the patch isn't being applied to the new version so that everyone does not have to go through the hassle of installing both the new version and then adding the patch on top of it thereby adding to the chance that between upgrading and then patching there are more chances for things to go wrong.

86 days ago


	Go figure still someone likes - minuses vs. +postives?

TxBoxer(positive)

34 days ago


	Sammy, what is the fix for this? I just downloaded and installed the latest version (6.1.4) and have the _day_of_ error. I looked thru the forums and did not find a fix. Please help.