5

Before starting on a new #eecms website, are there any other hotfixes i need to know of ?!

5

Most of the errors I run into have to do with Safecracker, since I usually build out my stuff in the front-end. I have a rolling fork for it.

There is another item I forgot to write down, but it's in the Safecracker API classes that extends the channel entries API.

| improve this answer | |
5

Yes EE has gone for months without a bug fix release. No this doesn't make any sense. But so long as you're being a Smart Developer and backing up as you go you're not likely to encounter any major issues. Just build the site and search the bug tracker if you run into an issue. In all probability most known bugs won't affect you. If something explodes, which is really unlikely, then roll back to your latest DB, revert your Git repo and be on your way.

| improve this answer | |
  • Some bugs are hard to hunt down and can take the better part of an afternoon to sort out. This question is to be prepared beforehand. – GDmac Dec 15 '12 at 12:09
  • I maintain that you don't need to spend time patching your install before starting development. The time could be better spent on features/polish and, frankly, it's EL's job to patch bugs, not ours. If you do run into an issue then there's already a searchable bug tracker which everyone has access to. – Dom Stubbs Dec 17 '12 at 18:44
4

There's also this nasty one that prevents you using {path=...} or {encode=...} tags inside your entries. Hotfix here:

https://support.ellislab.com/bugs/detail/18239/

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.