Niels Meersschaert's profile

- State changed from stale to open
by Niels Meersschaert at 8:27 PM
[state:open] I have been running into this issue as well. Any disable button immediately returns to it's prior state before the Ajax request has completed. Swit...

Niels Meersschaert commented at 12:14 AM

Here's the route snippet as an attached file due to formatting fun.

Additionally due to the id => new, our current code gets a RecordNotFound due to running Obj...
Niels Meersschaert commented at 12:10 AM
Here is a sample route we are attempting to use in Rails 3.0
resources :accounts do
collection do
```
get :outlook
post :invoice_all
```
end member do
```
post :invoice
...
```

- Importance changed from to Medium
by Niels Meersschaert at 9:19 PM
This commit doesn't appear to be in 3.0 final release. Is it slated to be released at some time? I am running into problems as a result of the broken new resour...

Niels Meersschaert commented at 6:58 PM
After further investigation, it looks like 2.3.5 actually is working correctly, possibly solving this issue. It actually exposed bugs in my tests, causing the f...
- Tag changed from activecord, fixtures, testunit to 2.3.5, activecord, fixtures, testunit
by Niels Meersschaert at 5:51 PM
This appears to have become even worse under 2.3.5. I have self.use_transactional_fixtures = true & fixtures :all in my test_helper.rb file. With no other chang...

Niels Meersschaert created the ticket at 8:26 PM

Loading a model thru eager loading or simple loading should return same results for associations. That is not the case with habtm with uniq option.

I have a mod...

Niels Meersschaert commented at 5:12 PM
Also using ActiveMerchant as a gem v1.4.1 eliminates the issue. It looks like the conflict is only between older versions of ActiveMerchant/Money & Rails 2.3.0....

Niels Meersschaert commented at 6:53 PM
I believe it was caused because my app uses ActiveMerchant as a plugin. As a result, I had a config.gem "money" requirement. When I removed that requirement, th...
Niels Meersschaert commented at 6:17 PM
It appears that the Money gem may be overstepping some rails calls thus causing this issue.