SMF Development > Fixed or Bogus Bugs

[4981] [1.x, 2.0] handling MS Smart Quotes

<< < (2/9) > >>

A doc file with such entities would help in at least do tests. ;)

meh...Devs always want more... :P

BTW: it's always MS's fault!!! >:( :P

Joshua Dickerson:

Wow. Maybe I should try complaining about the other things that irritate me to no end!

* Fix or remove the SMF database backup
* Really fix the Settings.php being emptied out problem
* Get rid of the spurious "your database may require an upgrade" warning
* Make mod install/uninstall either all or nothing -- refuse if ANY manual edits needed (most people ignore the manual edits) -- and validate that all changes were done properly (no more "undefined index" reports)
* Ensure that version updates do the database update too -- there are far too many systems out there with way back-level databases (even if it's just the smfVersion entry)
* Make conversion between encodings foolproof -- too many systems end up half-way changed, or a mix of encodings in the database or language files
* Fix the calendar so that the min/max limits are deltas to the current year (say, CY - 1 through CY + 5, with hard limits 1970 - 2037), or else automatically update the database, so we don't get reports that "I can't enter a 2012 event -- it's too far in the future!"
I consider all of these to be bugs, rather than enhancements, and they should be fixed in SMF 1 too! Properly dealing with this list will greatly reduce the support load, and greatly improve SMF's image.

The rest sound good, but honestly I'm not sure about this one:

"Make mod install/uninstall either all or nothing -- refuse if ANY manual edits needed (most people ignore the manual edits)........................."

Partially installed and partially uninstalled mods are the bane of SMF. Almost every "undefined index" error involves one. My impression is that people tend to accept partial actions and don't understand that they need to go back and manually edit the failed files. Therefore, I think that fully automatic installs/uninstalls should either do 100% of the job, or refuse to do any.

It would be nice to give some assistance on mod installs/uninstalls where SMF can handle some of the files itself, but we need to prevent people from walking off with the job half done. It might be enough to refuse to take the forum out of maintenance mode (or otherwise unlock it) until they have answered "yes" or "no" to each "Did you successfully manually edit file ________?" Maybe add, "do you swear upon your mother's grave..."?? There's probably no automated way to check that the work was done (else it could have been done fully automatically). If they answer "no" to any question, refuse to unlock the forum until they agree to uninstall/reinstall the mod, and can answer "yes" to all. Or, save a backup of each file affected by the mod, and restore all of them to completely roll back the action. If they say "yes" to a question, compare the current file to its backup, to see if something was done. There's all sorts of things that could be done.

If I had to do SMF over from scratch, I would not eval templates either. We always have to tell people to turn off eval and come back with the right error messages. Do you suppose it's possible to automatically turn off eval if an error is detected (and "eval" is in the message), and possibly purge the non-eval message?

Add: A related problem is that the package manager allows you to install a mod twice. As part of the pre-install check, it should see if the target code is already installed, and if so, refuse to proceed. This would eliminate all reports of "duplicate function defined".


[0] Message Index

[#] Next page

[*] Previous page

Go to full version