Hello,

we were finally able to reproduce and track down the bug; a fix will be pushed within a short time. Have some patience please, we'll inform you in this thread when the fix is publicly available in the repositories.

We apologise for the inconvenience ;)
Sascha

You might want to tie this into the thread i mentioned earlier...since it's a much closer match to the error talked about in this thread...this seems like a more general topic...as to the other one is more specific to the actual error during the install.

then they can both be closed (as long as the bug fix works here too ;D )

Hi Terry,

we'll post that in the other thread, too. After all this solution was long overdue and the least we can do is to make it public everywhere where the problem was mentioned by our brave testers :)

Greetings,
Sascha

Good job :-) I am curious to learn what caused the problem.

Cheers
Ramon

same here...I spent almost a whole afternoon looking inside the code to see what could possibly be being called too early or too late...or something!

thanks for fixing it though (crossing fingers)!

Hello,

we just released SilverCart version 1.0 RC2 which fixes this bug.

You can download it at "http://code.silvercart.org/silvercart/downloads".

Here's a brief explanation of what caused the error:

The problem was a call to the method "Member::currentUser()" in the constructor of the class "SilvercartShoppingCart". The method "currentUser()" fires a SQL query to gather all data of the current user from the database.
Since we decorate Silverstripes' "Member" object with the class "SilvercartCustomerRole" the query tries to read all the additional fields defined in "SilvercartCustomerRole".
On the first installation of the SilverCart module those additional fields are not yet written to the database, still the manifest builder already has knowledge of the fields via the decorator. That results in "Member::currentUser()" trying to read fields that are not present in the "Member" table, what caused the error message you both got.

The error didn't occur on our installations on Linux and MacOS X operating systems. We could reproduce them reliably on Windows XP and 7 systems though. We assume that this behaviour originates from the way the different operating systems handle the order in which files are executed.

Our solution to this problem is a new static method "isInstallationCompleted" in the "SilvercartConfig" class. We call this method in the "SilvercartShoppingCart" constructor so that the call to "Member::currentUser()" gets executed only when the SilverCart installation is complete.

Greetings,
Sascha

I hate to be picky!!! but I am pretty sure that the DataObjectManager needs to be named dataobject_manager.

you have it in your new documentation that it doesn't have the underscore (_), but I have talked to UncleCheese:

http://twitter.com/#!/_UncleCheese_/status/63830371908853760

might want to take a look at that and verify.

Thanks team.. much appreciated.. will try the new version today and feedback the results. Mark.