I'm at the point where I am running "/dev/build?flush=all" and I get the following error...

"PHP Fatal error: Class 'SortableDataObject' not found in ../web/silvercart/_config.php"

I've searched all over the web but can't seem to find any help. Any suggestions would be appreciated.

-- John

Hi jbundy,

the class "SortableDataObject" comes from the external module DataObjectManager. Can you please verify that you have a working SilverStripe installation with the modules "DataObject Manager" and "Uploadify" installed before you try to setup SilverCart?

Please take care, the directory has to be named "dataobject_manager".

You can find additional information on the DataObjectManager here:
http://silverstripe.org/dataobjectmanager-module/

Hope this solves your problem.

Cheers
Ramon

I have downloaded the module DataObjectManager many times and ran a 'dev/build' after changing the directory name to dataobject_manager. There seems to be no confirmation that the module was actually loaded, but the directory is there. I have also verified that the permissions are set correctly on all directories.

-- John

Hi jbundy,

I am afraid, but it seems we can't help here. It is obviously a problem with the DataObjectManager module. SilverCart tries to use a class that comes from DataObjectManager. If it is not present, there is not much I can do from here.

It is very important that there is a fully functional SilverStripe installation and that the DataObjectManager + Uploadify are properly set up + /dev/build/?flush=all.

By trying to setup multiple modules at the same time, one module might try to call a function or a class from another module, which might not be installed at that time.

Cheers
Ramon

Ramon,

Thank you for the help in trying to resolve the problem.

At this point I am forced to give up on SilverCart. I deleted the SilverCart directories and database tables and have gone with the standard Ecommerce module from silverstripe.org. It loaded very easily on the exact same installation of SilverStripe with no issues.

-- John

Had temp an clean install with ss2.4.2 and got the same error. With 2.3.3/4/5 it had no errors